-
Notifications
You must be signed in to change notification settings - Fork 39.6k
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
Add kms-plugin-container.manifest to release manifest tarball. #65035
Add kms-plugin-container.manifest to release manifest tarball. #65035
Conversation
/assign @mikedanese |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: immutableT, mikedanese 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 |
/ok-to-test |
Holding until we verify the fix. /hold |
/kind cleanup |
[MILESTONENOTIFIER] Milestone Pull Request: Up-to-date for process Pull Request Labels
|
/hold cancel |
I build a release of this PR using release/push-build.sh and my test cluster (with KMS integration) came-up fine. |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions here. |
…5035-upstream-release-1.10 Automatic merge from submit-queue. Automated cherry pick of #65035 upstream release 1.10 Add kms-plugin-container.sh to release.sh. ```release-note Due to the mismatch between quick release and bazel release need to manually update release.sh to include kms-plugin-container.manifest in release.sh. Otherwise, when KMS integration is requested kube-apiserver fails to come-up. ``` REF #65035
What this PR does / why we need it:
cluster/gce/manifests/kms-plugin-container.manifest needs to be included into the manifests' release tarball.
Which 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:
Release note: