-
Notifications
You must be signed in to change notification settings - Fork 295
v0.12.x: feat: add CF stackNameOverride in cluster.yaml #1487
Conversation
Add option in cluster.yaml to override the name of CF controlPlane, network and etcd stacks. This is useful for migration of CF stacks from kube-aws <0.11.x without creating a new VPC.
Because it is part of the cloudformation config in cluster.yaml.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: If they are not already assigned, you can assign the PR to them by writing 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 |
Codecov Report
@@ Coverage Diff @@
## v0.12.x #1487 +/- ##
===========================================
- Coverage 37.91% 37.85% -0.06%
===========================================
Files 75 75
Lines 4595 4607 +12
===========================================
+ Hits 1742 1744 +2
- Misses 2611 2620 +9
- Partials 242 243 +1
Continue to review full report at Codecov.
|
kubernetes-retired#1487 introduced a bug when doing a partial stack upgrade with a stack name override. This is fixed by using the actual stack name in operation targets instead of the hard coded constants.
kubernetes-retired#1487 introduced a bug when doing a partial stack upgrade with a stack name override. This is fixed by using the actual stack name in operation targets instead of the hard coded constants.
kubernetes-retired#1487 introduced a bug when doing a partial stack upgrade with a stack name override. This is fixed by using the actual stack name in operation targets instead of the hard coded constants.
kubernetes-retired#1487 introduced a bug when doing a partial stack upgrade with a stack name override. This is fixed by using the actual stack name in operation targets instead of the hard coded constants.
#1487 introduced a bug when doing a partial stack upgrade with a stack name override. This is fixed by using the actual stack name in operation targets instead of the hard coded constants.
kubernetes-retired#1487 introduced a bug when doing a partial stack upgrade with a stack name override. This is fixed by using the actual stack name in operation targets instead of the hard coded constants.
#1487 introduced a bug when doing a partial stack upgrade with a stack name override. This is fixed by using the actual stack name in operation targets instead of the hard coded constants.
See #1484 for details/comments.