Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrade sigs.k8s.io/structured-merge-diff/v4 to v4.2.1 #107565

Merged

Conversation

jiahuif
Copy link
Member

@jiahuif jiahuif commented Jan 14, 2022

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR upgrade sigs.k8s.io/structured-merge-diff/v4 v4.2.1

Which issue(s) this PR fixes:

Fixes #104641
Replaces #105983

Special notes for your reviewer:

Does this PR introduce a user-facing change?

kube-apiserver: when merging lists, Server Side Apply now prefers the order of the submitted request instead of the existing persisted object

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


/sig api-machinery

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. labels Jan 14, 2022
@jiahuif
Copy link
Member Author

jiahuif commented Jan 14, 2022

/assign @apelisse @liggitt

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. area/apiserver area/cloudprovider area/code-generation area/dependency Issues or PRs related to dependency changes area/kubectl sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/storage Categorizes an issue or PR as relevant to SIG Storage. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Jan 14, 2022
@k8s-ci-robot k8s-ci-robot requested review from andrewsykim, apelisse and a team January 14, 2022 18:29
@liggitt
Copy link
Member

liggitt commented Jan 14, 2022

glad to see the test change in test/integration/client/client_test.go from #105983 wasn't needed with this PR

will defer review to @apelisse and can approve the dep update once this has lgtm

@jiahuif jiahuif force-pushed the deps/structured-merged-diff branch from 3a09679 to 31205dc Compare January 14, 2022 18:31
@apelisse
Copy link
Member

Awesome, thanks!
/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 14, 2022
@liggitt
Copy link
Member

liggitt commented Jan 14, 2022

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: apelisse, jiahuif, liggitt

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

to be appending instead of prepending.
@k8s-ci-robot k8s-ci-robot added area/test sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed lgtm "Looks good to me", indicates that a PR is ready to be merged. labels Jan 14, 2022
@jiahuif
Copy link
Member Author

jiahuif commented Jan 14, 2022

@liggitt Actually, I forgot to update the integration test. We still need to update the test because the order in it was wrong.
What the test expects:
{nginx} apply {sidecar} = {sidecar, nginx}
what we want
{nginx} apply {sidecar} = {nginx, sidecar}, because we are expecting the apply to append new items from RHS.

The test was written with no assumption about the order. Now that we fix the ordering issue, we should enforce it in the test as well.

@apelisse
Copy link
Member

Yeah, reading the test, it looks like side-car was applied first and then nginx. So we should have nginx last which is what we have now.
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 14, 2022
@k8s-ci-robot k8s-ci-robot merged commit cf18d80 into kubernetes:master Jan 14, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.24 milestone Jan 14, 2022
@cbandy
Copy link
Contributor

cbandy commented Jan 14, 2022

I see container env vars have the same merge strategy as init containers. Does this change address the ordering of both fields?

@jiahuif
Copy link
Member Author

jiahuif commented Jan 15, 2022

Yes it does! Under the hood they are both using the list merge algorithm.

I see container env vars have the same merge strategy as init containers. Does this change address the ordering of both fields?

k8s-ci-robot added a commit that referenced this pull request Jan 15, 2022
…f-#107565-upstream-release-1.23

Automated cherry pick of #107565: upgrade sigs.k8s.io/structured-merge-diff/v4 to v4.2.1
k8s-ci-robot added a commit that referenced this pull request Jan 15, 2022
…f-#107565-upstream-release-1.21

Automated cherry pick of #107565: upgrade sigs.k8s.io/structured-merge-diff/v4 to v4.2.1
k8s-ci-robot added a commit that referenced this pull request Jan 15, 2022
…f-#107565-upstream-release-1.22

Automated cherry pick of #107565: upgrade sigs.k8s.io/structured-merge-diff/v4 to v4.2.1
@jiahuif jiahuif deleted the deps/structured-merged-diff branch January 15, 2022 20:35
@fedebongio
Copy link
Contributor

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/apiserver area/cloudprovider area/code-generation area/dependency Issues or PRs related to dependency changes area/kubectl area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect initContainers order when using server-side apply
6 participants