Skip to content

Add annotations to task update request api#4647

Merged
mxpv merged 1 commit intocontainerd:masterfrom
katiewasnothere:task_update_annotations_upstream
Nov 18, 2020
Merged

Add annotations to task update request api#4647
mxpv merged 1 commit intocontainerd:masterfrom
katiewasnothere:task_update_annotations_upstream

Conversation

@katiewasnothere
Copy link
Copy Markdown

This PR is a companion to an update in cri-api that I made recently kubernetes/kubernetes#95741. This PR adds annotations to UpdateTaskRequest and UpdateTaskInfo so when the cri-api change is merged, containerd can use it and pass along to shims. While waiting for that PR, I'd like to get feedback here and hopefully merge this.

As mentioned in the above PR, the annotations field on task Update allows for experimentation with updating various resources or passing along update options.

Signed-off-by: Kathryn Baldauf [email protected]

@k8s-ci-robot
Copy link
Copy Markdown

Hi @katiewasnothere. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@katiewasnothere
Copy link
Copy Markdown
Author

@kevpar @dcantah @ambarve fyi

@theopenlab-ci
Copy link
Copy Markdown

theopenlab-ci Bot commented Oct 23, 2020

Build succeeded.

@AkihiroSuda
Copy link
Copy Markdown
Member

/ok-to-test

Copy link
Copy Markdown
Member

@mxpv mxpv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@katiewasnothere katiewasnothere force-pushed the task_update_annotations_upstream branch from b79c5a7 to 7c6543e Compare October 27, 2020 20:42
@katiewasnothere
Copy link
Copy Markdown
Author

Updated based on local testing to actually pass the annotations in a shim request :P

Will need to retest @mxpv

@theopenlab-ci
Copy link
Copy Markdown

theopenlab-ci Bot commented Oct 27, 2020

Build succeeded.

@katiewasnothere
Copy link
Copy Markdown
Author

@mxpv PTAL when you can and merge if it looks good :)

@mxpv
Copy link
Copy Markdown
Member

mxpv commented Nov 5, 2020

Changes LGTM. This needs one more LGTM in order to be merged :)

Comment thread task.go Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only for experimentation?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can update this. Really annotations are for arbitrary AND experimental resource constraint information. The goal is that we can pass in any resource information for use and for testing now, then if we determine there are specific resources or other fields that would be useful upstream or in some other way, we can make additional PRs to opencontainer's runtime spec to update WindowsResources.

@katiewasnothere katiewasnothere force-pushed the task_update_annotations_upstream branch from 7c6543e to 64e0e1b Compare November 9, 2020 21:44
@theopenlab-ci
Copy link
Copy Markdown

theopenlab-ci Bot commented Nov 9, 2020

Build succeeded.

@katiewasnothere katiewasnothere force-pushed the task_update_annotations_upstream branch from 64e0e1b to 95ba6e9 Compare November 9, 2020 22:13
@theopenlab-ci
Copy link
Copy Markdown

theopenlab-ci Bot commented Nov 9, 2020

Build succeeded.

@katiewasnothere
Copy link
Copy Markdown
Author

@AkihiroSuda PTAL when you can :)

@kevpar @dcantah @ambarve @anmaxvl fyi

@katiewasnothere
Copy link
Copy Markdown
Author

@mxpv and @AkihiroSuda is there any concern about compat issues with this?

@kevpar
Copy link
Copy Markdown
Member

kevpar commented Nov 11, 2020

This looks okay to me. Adding a field to the proto shouldn't be a breaking change, and using the functional options approach on the task API with WithAnnotations means that shouldn't break either.

@AkihiroSuda
Copy link
Copy Markdown
Member

@dmcgowan PTAL

Copy link
Copy Markdown
Member

@estesp estesp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@katiewasnothere
Copy link
Copy Markdown
Author

@AkihiroSuda @estesp @dmcgowan is this ready to be merged?

Copy link
Copy Markdown
Member

@mikebrow mikebrow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants