Skip to content
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 PSP to the deprecation guide #26629

Merged
merged 1 commit into from
Apr 8, 2021
Merged

Conversation

tallclair
Copy link
Member

See also #26581

/cc @deads2k

@k8s-ci-robot k8s-ci-robot requested a review from deads2k February 19, 2021 20:20
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. language/en Issues or PRs related to English language sig/docs Categorizes an issue or PR as relevant to SIG Docs. labels Feb 19, 2021
@tallclair
Copy link
Member Author

@reylejano missed your comment before pushing this - how do you want to handle it? This information seems relevant prior to v1.21 being released, so I'd vote to keep it on the main branch.

@netlify
Copy link

netlify bot commented Feb 19, 2021

Deploy preview for kubernetes-io-master-staging ready!

Built with commit ce2e5f8

https://deploy-preview-26629--kubernetes-io-master-staging.netlify.app

@reylejano
Copy link
Member

/assign
@cc @sftim @kbhawkey @jimangel @irvifa

@tallclair I've cc'd sig-docs leads to get their input

@@ -49,6 +49,13 @@ RuntimeClass in the **node.k8s.io/v1beta1** API version will no longer be served
* All existing persisted objects are accessible via the new API
* No notable changes

#### PodSecurityPolicy {#psp-v125}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my initial version kept this page limited to things with clear replacements. I was going to see what shook out for PSP this release, and if cronjob graduates to v1 as expected in 1.21, update this section for both of them after that.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also, PSP deprecation is getting released with 1.21, so I'd hold this at least until then

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm OK with merging this into the live website before v1.21 released, provided that:

  • the deprecation in v1.21 is planned out, including how we communicate it
  • we are confident beyond any reasonable doubt of the deprecation timeline, we are committing ourselves to make exactly the changes we're documenting here
  • we make this update in tandem with the broader piece about communiction

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See PR #27369, Add blog post describing PSP deprecation and next steps.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(now merged)


The **extensions/v1beta1** API version of PodSecurityPolicy is no longer served as of v1.16.

* Migrate manifests and API client to use the **policy/v1beta1** API version, available since v1.10.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Migrate manifests and API client to use the **policy/v1beta1** API version, available since v1.10.
* Migrate manifests and API clients to use the **policy/v1beta1** API version, available since v1.10.

The **extensions/v1beta1** API version of PodSecurityPolicy is no longer served as of v1.16.

* Migrate manifests and API client to use the **policy/v1beta1** API version, available since v1.10.
* Note that the **policy/v1beta1** API version of PodSecurityPolicy will be removed in v1.25.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Note that the **policy/v1beta1** API version of PodSecurityPolicy will be removed in v1.25.
* Note that the **policy/v1beta1** API version of PodSecurityPolicy is also deprecated and will be removed in v1.25.

@@ -49,6 +49,13 @@ RuntimeClass in the **node.k8s.io/v1beta1** API version will no longer be served
* All existing persisted objects are accessible via the new API
* No notable changes

#### PodSecurityPolicy {#psp-v125}

PodSecurityPolicy in the **policy/v1beta1** API version will no longer be served in v1.25, and the PodSecurityPolicy admission controller will be removed.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
PodSecurityPolicy in the **policy/v1beta1** API version will no longer be served in v1.25, and the PodSecurityPolicy admission controller will be removed.
The **policy/v1beta1** API version of PodSecurityPolicy will no longer be served in v1.25, and the PodSecurityPolicy admission plugin will be removed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be good to add this, but I don't see it blocking a merge.


PodSecurityPolicy in the **policy/v1beta1** API version will no longer be served in v1.25, and the PodSecurityPolicy admission controller will be removed.

PodSecurityPolicy replacements are still under discussion, but current use can be migrated to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would avoid putting uncertain future-looking statements in this doc

Suggested change
PodSecurityPolicy replacements are still under discussion, but current use can be migrated to
Current use can be migrated to

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can link to the blog article from #27369, which I believe is due to merge and publish before the v1.21 release. Usually we don't link to blog articles for information about features but in this case I (confidently) think that's a good idea.

@annajung
Copy link
Contributor

/hold until consensus on adding this to main vs dev-1.21 branch
feel free to remove hold when a decision has been reached

cc @palnabarun

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 19, 2021

PodSecurityPolicy in the **policy/v1beta1** API version will no longer be served in v1.25, and the PodSecurityPolicy admission controller will be removed.

PodSecurityPolicy replacements are still under discussion, but current use can be migrated to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👋 @tallclair .
I'm a bit surprised that this page includes information about future feature deprecations (about 1 yr away?).

nit: PodSecurityPolicy replacements are still under discussion; however, you can migrate current PodSecurityPolicy resources to ...

Copy link
Member

@liggitt liggitt Feb 19, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the ones already included in the page in master are current deprecations (if you kubectl get those resources on a 1.20 API server, you get a message that they are deprecated, when they'll be removed, and what you should switch to using)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

current deprecations

makes sense to me

We could merge this change at the same time as the deprecation announcement.

@tengqm
Copy link
Contributor

tengqm commented Feb 20, 2021

SInce PSP deprecation is targeted 1.21, please consider submit this to the dev-1.21 branch.

@reylejano
Copy link
Member

/milestone 1.21
/assign @tengqm
/sig auth

@k8s-ci-robot k8s-ci-robot added the sig/auth Categorizes an issue or PR as relevant to SIG Auth. label Feb 20, 2021
@k8s-ci-robot k8s-ci-robot added this to the 1.21 milestone Feb 20, 2021
@tengqm
Copy link
Contributor

tengqm commented Mar 18, 2021

@annajung I was suggesting this going into dev-1.21 branch because PSP is not deprecated in 1.20 yet. Considering that the target page already contains some future predicting contents, maybe we can lift the hold on this?

@liggitt
Copy link
Member

liggitt commented Mar 18, 2021

Considering that the target page already contains some future predicting contents, maybe we can lift the hold on this?

I intentionally limited this page to items already announced as deprecated in a released version, which had an unequivocal "switch to use ____" call to action. Neither of those is yet true for PSP, so I wouldn't merge this to master yet.

@reylejano
Copy link
Member

I intentionally limited this page to items already announced as deprecated in a released version, which had an unequivocal "switch to use ____" call to action. Neither of those is yet true for PSP, so I wouldn't merge this to master yet.

@liggitt @tallclair How about submitting this PR to the dev-1.21 branch so that it merges with master on the 1.21 release date (April 8). March 31 is the "ready to merge" deadline for the dev-1.21 and the PR can be modified until then.

@sftim
Copy link
Contributor

sftim commented Apr 6, 2021

We published https://blog.k8s.io/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/

@sftim
Copy link
Contributor

sftim commented Apr 6, 2021

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 6, 2021
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: c6ccb356f9965f6eaf628f55cdd7b7d52af3b580

@sftim
Copy link
Contributor

sftim commented Apr 6, 2021

Not unholding, but I recommend that whoever approves this does also unhold it.

@reylejano
Copy link
Member

reylejano commented Apr 7, 2021

Hi @tallclair , what do you think of the suggestion of replacing controller with plugin in L54. The PSP blog post is live now, what do you think of linking to the blog post. This PR can stay targeted to the master branch

@sftim
Copy link
Contributor

sftim commented Apr 7, 2021

I'm definitely happy to see this merge in even if there are nits. The commit in the PR right now could be polished, but is factually accurate enough to merge.

@reylejano
Copy link
Member

/hold cancel
/approve

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 8, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: reylejano

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 /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 Apr 8, 2021
@k8s-ci-robot k8s-ci-robot merged commit 5fe92f2 into kubernetes:master Apr 8, 2021
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/docs Categorizes an issue or PR as relevant to SIG Docs. 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.

8 participants