-
Notifications
You must be signed in to change notification settings - Fork 42.1k
Rename '--experimental-encryption-provider-config' to '--encryption-provider-config' #71206
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
Conversation
|
Hi @stlaz. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
/ok-to-test |
|
This is the alternative to #61592, 61592 was stuck behind other PRs and in rebase-hell. This does not alter the logic in any way or drop support for the older option. This just marks the older one as deprecated and adds a new option that exercises the same code as the old option /priority critical-urgent |
|
LGTM! |
|
there's a gofmt error: https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/71206/pull-kubernetes-verify/114526/ cc @smarterclayton @immutableT for evaluation (https://github.com/kubernetes/kubernetes/blob/master/OWNERS_ALIASES#L76-L78), since this is effectively graduating the encryption feature from experimental |
815ed49 to
21c1bb8
Compare
…'--encryption-provider-config'. This change renames the '--experimental-encryption-provider-config' flag to '--encryption-provider-config'. The old flag is accepted but generates a warning. In 1.14, we will drop support for '--experimental-encryption-provider-config' entirely. Co-authored-by: Stanislav Laznicka <[email protected]>
Weird, my IDE started doing that. Fixed with vim... |
probably a different go version (gofmt changed how indentation worked in 1.11, iirc) |
|
/retest |
|
Many thanks for LGTM and approval 🙂 Maybe we could get @mikedanese for the cluster/gce approval here? |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, smarterclayton, stlaz The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
maybe this is an actual gke error / using the flag in some of their scripts? |
|
/retest Review the full test history for this PR. Silence the bot with an |
both the old and new flag are still accepted. the same gke error appears in other PR jobs: https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/71124/pull-kubernetes-e2e-gke/3445/ |
|
/retest |
|
/test pull-kubernetes-e2e-gke |
|
/cc @loburm @mikedanese @loburm we have a couple of PRs failing on pull-kubernetes-e2e-gke consistently today. Can you please help take a look to see if there's a wider GKE issue. this is critical PR blocked on getting into 1.13 release. |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest |
1 similar comment
|
/retest |
|
cc @mayakacz |
As per [this PR](kubernetes/kubernetes#71206) the flag has changed, which is a change that I proposed, even though we still support 1.14. Other things may have changed since the last change to the document in 2017, so requires better review. In addition there is a specific area for AWS. Does Azure require the same?
As per [this PR](kubernetes/kubernetes#71206) the flag has changed, which is a change that I proposed, even though we still support 1.14. Other things may have changed since the last change to the document in 2017, so requires better review. In addition there is a specific area for AWS. Does Azure require the same?
This change renames the '--experimental-encryption-provider-config' flag to '--encryption-provider-config'. The old flag is accepted but generates a warning.
In 1.14, we will drop support for '--experimental-encryption-provider-config' entirely.
What type of PR is this?
/kind api-change
What this PR does / why we need it:
This PR follows up on the
EncryptionConfigurationalpha->stable move from #67383Which issue(s) this PR fixes:
Fixes #61420
Special notes for your reviewer:
This is a rebase of original PR #61592
Does this PR introduce a user-facing change?: