-
Notifications
You must be signed in to change notification settings - Fork 629
fix: resolve secrets when generating eks userdata #4285
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
fix: resolve secrets when generating eks userdata #4285
Conversation
/test ? |
@faiq: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
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. |
/test pull-cluster-api-provider-aws-e2e-eks |
8c9dff4
to
1ec1610
Compare
/test pull-cluster-api-provider-aws-e2e-eks |
It would be be good to get this covered by e2e at some point. From my side: /approve |
/cherrypick release-2.0 |
@richardcase: once the present PR merges, I will cherry-pick it on top of release-2.0 in a new PR and assign it to you. In response to this:
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. |
/cherrypick release-1.5 |
@richardcase: once the present PR merges, I will cherry-pick it on top of release-1.5 in a new PR and assign it to you. In response to this:
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. |
/lgtm |
/hold |
/lgtm |
/unhold |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: richardcase, Skarlso 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 |
@richardcase: #4285 failed to apply on top of branch "release-2.0":
In response to this:
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. |
@richardcase: #4285 failed to apply on top of branch "release-1.5":
In response to this:
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. |
/cherrypick release-2.0 |
@faiq: #4285 failed to apply on top of branch "release-2.0":
In response to this:
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. |
fix: resolve secrets when generating eks userdata (backport #4285)
…2.1) (#4289) * fix: resolve secrets when generating eks userdata * fix: log line and resolve files error
What type of PR is this?
/kind bug
What this PR does / why we need it:
Previously the userdata for the eks config did not resolve the data from the
ContentFrom
field. This PR borrows the implementation in the kubeadm bootstrap provider in CAPI and ports it over here. We also add a test to see if we resolve the secret properlyWhich issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Checklist:
Release note: