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

Generate revisions of NLB objects, and introduce cleanup phase #16356

Merged
merged 1 commit into from
Feb 17, 2024

Conversation

justinsb
Copy link
Member

This lets us safely make changes to otherwise immutable fields, in
particular for adding security groups to NLBs created without them.

We detect the older versions, and create deletion tasks to remove
them. These tasks can be deferred, and we expect them to be
deferred to a "prune" phase that runs after cluster apply.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Feb 15, 2024
@k8s-ci-robot k8s-ci-robot added area/documentation area/provider/aws Issues or PRs related to aws provider area/provider/openstack Issues or PRs related to openstack provider area/rolling-update labels Feb 15, 2024
@justinsb
Copy link
Member Author

This is the remaining work from #16291; I think it makes sense to consider as a single PR. (I sent a new PR to keep the PR history understandable, even though they should now be the same!)

cc @hakman @rifelpet

@justinsb
Copy link
Member Author

One possible thing I've realized I could do ... I could split out the deletion tasks/printing/processing into a separate PR, and then only really use them in this PR. That would make this one smaller... let me know!

@justinsb justinsb force-pushed the revisions_and_pruning branch from 182dd96 to da2c2f6 Compare February 17, 2024 05:17
@hakman
Copy link
Member

hakman commented Feb 17, 2024

/test pull-kops-e2e-k8s-aws-calico

cmd/kops/update_cluster.go Outdated Show resolved Hide resolved
This lets us safely make changes to otherwise immutable fields, in
particular for adding security groups to NLBs created without them.

We detect the older versions, and create deletion tasks to remove
them.  These tasks can be deferred, and we expect them to be
deferred to a "prune" phase that runs after cluster apply.

Co-authored-by: Ciprian Hacman <ciprian@hakman.dev>
@justinsb justinsb force-pushed the revisions_and_pruning branch from 74b26d1 to 2a9343a Compare February 17, 2024 16:41
@justinsb
Copy link
Member Author

Changed to --prune, added a few more comments, and squashed the commits.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 17, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 17, 2024
@k8s-ci-robot k8s-ci-robot merged commit 24ab206 into kubernetes:master Feb 17, 2024
21 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.29 milestone Feb 17, 2024
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/documentation area/provider/aws Issues or PRs related to aws provider area/provider/openstack Issues or PRs related to openstack provider area/rolling-update cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants