-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Update AWS CCM tags #12104
Update AWS CCM tags #12104
Conversation
kubernetes/cloud-provider-aws#267 has the new location for images (including going back to 1.18) /test ? |
/test pull-kops-e2e-aws-cloud-controller-manager |
/test pull-kops-e2e-aws-cloud-controller-manager |
/retest |
@@ -28,7 +28,7 @@ spec: | |||
serviceAccountName: aws-cloud-controller-manager | |||
containers: | |||
- name: aws-cloud-controller-manager | |||
image: {{ if .ExternalCloudControllerManager.Image }}{{ .ExternalCloudControllerManager.Image }}{{ else }}gcr.io/k8s-staging-provider-aws/cloud-controller-manager:{{AWSCCMTag}}{{ end }} | |||
image: {{ if .ExternalCloudControllerManager.Image }}{{ .ExternalCloudControllerManager.Image }}{{ else }}us.gcr.io/k8s-artifacts-prod/provider-aws/cloud-controller-manager:{{AWSCCMTag}}{{ end }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should move this + the tag logic to pkg/model/components
. Then we can more easily fall back to latest for newer k8s versions.
Also, should the repository for prod be k8s.gcr.io/provider-aws/cloud-controller-manager
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm trying to move it to pkg/model/components but the cluster spec as seen by AWSCloudControllerManagerOptionsBuilder
:
eccm := clusterSpec.ExternalCloudControllerManager |
shows cloudControllerManager
as empty, even if the actual cluster spec includes the cloudProvider
subfield.
I think a related symptom is that the integration test input includes the CCM struct and fields:
cloudControllerManager: | |
provider: aws |
but the completed cluster spec as stored in the state store has an empty CCM struct:
Line 21 in 8dee92b
cloudControllerManager: {} |
I don't know why that is happening but I'm guessing it is related. Any help would be appreciated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I run kops get cluster -o yaml --full
I do see:
cloudControllerManager:
allocateNodeCIDRs: true
cloudProvider: aws
clusterCIDR: fd00:10:96::/64
clusterName: test.kops-dev.srsandbox.io
configureCloudRoutes: false
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With some rough testing, this only seems to be happening with the terraform tests, but why ... it doesn't make any sense to me.
/retest |
I just pushed what ./hack/update-expected.sh is setting for the integration test files. I don't understand why one manifest has |
The external cloud controller manager data seems to be lost during decoding: Line 123 in d69106e
The input yaml has the fields but the outputted object does not. |
/test pull-kops-e2e-aws-cloud-controller-manager |
/test pull-kops-e2e-aws-cloud-controller-manager |
/test pull-kops-e2e-aws-cloud-controller-manager |
/test pull-kops-e2e-cni-kuberouter |
@olemarkus it turns out the decoding issues were due to the manifests having |
/test pull-kops-e2e-ipv6-conformance |
/test pull-kops-e2e-cni-kuberouter |
/retest |
/test pull-kops-e2e-aws-cloud-controller-manager |
/test pull-kops-e2e-ipv6-conformance |
/test pull-kops-e2e-cni-kuberouter |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus 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 |
WIP pending any action from kubernetes/cloud-provider-aws#244