kubeapiserver: rename '--experimental-encryption-provider-config' to …#61592
kubeapiserver: rename '--experimental-encryption-provider-config' to …#61592marrrvin wants to merge 1 commit intokubernetes:masterfrom
Conversation
…'--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.12, we will drop support for '--experimental-encryption-provider-config' entirely.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: marrrvin 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 DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@php-coder FYI |
|
@marrrvin Thank you for your contribution! Could you update PR title to make it shorter? Also in the description, please, replace And this issue deserves to be mentioned in the changelog, hence release note is needed. I'd suggest to something like: @ericchiang @liggitt PTAL. Do we need release note with required action in this case? /sig auth |
|
@marrrvin Please, mention also that |
|
before this can be merged, we have to fix the way the encryption config is parsed. currently it uses a non-standard parsing method that pays no attention to the version of the config: the types must change to use standard methods for including kind/apiVersion (inlining metav1.TypeMeta like all other objects), define a versioned config (we can promote straight to v1beta1 if we don't require any structural changes), and parsing must require well-formed config files before this is promoted out of experimental mode. |
|
@liggitt Thanks. Could you please put me an example of standard parsing method? |
Looks like you may follow this example: kubernetes/cmd/kube-proxy/app/server.go Lines 292 to 314 in dce1b88 @liggitt Please, confirm. |
|
yes, roughly that.
|
|
@marrrvin: PR needs rebase. 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. |
Not yet, unfortunately (as now that PR requires another PR :) ) |
php-coder
left a comment
There was a problem hiding this comment.
Besides rebasing against the latest master, we need to also update another place that was introduced recently:
$ git grep 'experimental-encryption-provider-config'
...
cluster/gce/gci/apiserver_manifest_test.go: return fmt.Sprintf("--experimental-encryption-provider-config=%s", path)
cluster/gce/gci/apiserver_manifest_test.go:// EncryptionProviderConfig file of type KMS and inject experimental-encryption-provider-config startup flag.|
@php-coder ok. I'll try to do it on holidays. |
|
/milestone v1.12 Looks like this needs to be in 1.12 please drop the milestone if i am reading this wrong |
|
@marrrvin can you please rebase? |
|
/hold while this is definitely desired, we shouldn't drop the experimental prefix until the config driving this graduates from alpha (in progress in #67383) |
|
@marrrvin this needs rebase ... code freeze is tomorrow! ( https://github.com/kubernetes/sig-release/tree/master/releases/release-1.13 ) |
|
@dims should we just do the rebase ourselves? I've got it ready in https://github.com/stlaz/kubernetes/tree/enc_config_opt but won't be able to push it in this PR. |
|
@stlaz please open a fresh PR and we can discuss there. |
|
This PR can now be closed as the above one was merged. |
|
/close |
|
@php-coder: Closed this PR. DetailsIn 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. |
…'--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.12, we will drop support for '--experimental-encryption-provider-config' entirely.
What this PR does / why we need it:
Encryption at rest with static configs has been promoted to beta.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Updates #61420
Special notes for your reviewer:
Release note: