Skip to content

Conversation

@stlaz
Copy link
Member

@stlaz stlaz commented Nov 19, 2018

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 EncryptionConfiguration alpha->stable move from #67383

Which 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?:

API server flag `--experimental-encryption-provider-config` was renamed to `--encryption-provider-config`. The old flag is accepted with a warning but will be removed in 1.14.

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API size/S Denotes a PR that changes 10-29 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Nov 19, 2018
@k8s-ci-robot
Copy link
Contributor

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Nov 19, 2018
@k8s-ci-robot k8s-ci-robot added area/apiserver sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Nov 19, 2018
@liggitt
Copy link
Member

liggitt commented Nov 19, 2018

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 19, 2018
@dims
Copy link
Member

dims commented Nov 19, 2018

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
/milestone v1.13

@k8s-ci-robot k8s-ci-robot added this to the v1.13 milestone Nov 19, 2018
@k8s-ci-robot k8s-ci-robot added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Nov 19, 2018
@dims
Copy link
Member

dims commented Nov 19, 2018

LGTM!

@liggitt
Copy link
Member

liggitt commented Nov 19, 2018

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

…'--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]>
@stlaz
Copy link
Member Author

stlaz commented Nov 19, 2018

there's a gofmt error: https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/71206/pull-kubernetes-verify/114526/

Weird, my IDE started doing that. Fixed with vim...

@liggitt
Copy link
Member

liggitt commented Nov 19, 2018

Weird, my IDE started doing that

probably a different go version (gofmt changed how indentation worked in 1.11, iirc)

@stlaz
Copy link
Member Author

stlaz commented Nov 19, 2018

/retest

@stlaz
Copy link
Member Author

stlaz commented Nov 20, 2018

Many thanks for LGTM and approval 🙂 Maybe we could get @mikedanese for the cluster/gce approval here?

@smarterclayton
Copy link
Contributor

/approve

@k8s-ci-robot
Copy link
Contributor

[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

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 20, 2018
@dims
Copy link
Member

dims commented Nov 20, 2018

/retest

2 similar comments
@stlaz
Copy link
Member Author

stlaz commented Nov 20, 2018

/retest

@nikopen
Copy link
Contributor

nikopen commented Nov 20, 2018

/retest

@nikopen
Copy link
Contributor

nikopen commented Nov 20, 2018

maybe this is an actual gke error / using the flag in some of their scripts?

@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

@liggitt
Copy link
Member

liggitt commented Nov 20, 2018

maybe this is an actual gke error / using the flag in some of their scripts?

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/

@enj
Copy link
Member

enj commented Nov 21, 2018

/retest

@AishSundar
Copy link
Contributor

/test pull-kubernetes-e2e-gke

@AishSundar
Copy link
Contributor

AishSundar commented Nov 21, 2018

/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.

@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

@stlaz
Copy link
Member Author

stlaz commented Nov 21, 2018

/retest

@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

@stlaz
Copy link
Member Author

stlaz commented Nov 21, 2018

/retest

@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.

@nikopen
Copy link
Contributor

nikopen commented Nov 21, 2018

/retest

1 similar comment
@mikedanese
Copy link
Member

/retest

@k8s-ci-robot k8s-ci-robot merged commit 2b0212d into kubernetes:master Nov 21, 2018
@dims
Copy link
Member

dims commented Nov 27, 2018

cc @mayakacz

Oshratn added a commit to giantswarm/docs that referenced this pull request Jan 19, 2020
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?
Oshratn added a commit to giantswarm/docs that referenced this pull request Mar 1, 2020
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?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/apiserver cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Promote encryption at rest with static configs to beta