Remove unsupported PodSecurityPolicy #918
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Praveenrajmani
force-pushed
the
upgrade-deps
branch
2 times, most recently
from
2cb5783
to
89b8a4e
Compare
Praveenrajmani
force-pushed
the
upgrade-deps
branch
from
89b8a4e
to
3f06b48
Compare
Praveenrajmani
force-pushed
the
upgrade-deps
branch
from
3f06b48
to
df81a8d
Compare
balamurugana
approved these changes
Aug 1, 2024
balamurugana
changed the title
prakashsvmx
approved these changes
Aug 1, 2024
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PSP is deprecated from v1.21 and removed from k8s v1.24. The dependent pkgs have already removed the PSP support. It is time to remove PSP and stop supporting it.
To be added in release notes
No support for PSP from v4.1.x
As PodSecurityPolicy was deprecated in kubernetes v1.21 and removed from kubernetes in v1.25. Its support will be removed from DirectPV v4.1.x.
If you wish to retain the support during the upgrade from versions < v4.1.x to v4.1.x, please follow the steps below
STEP 1: Take a backup before upgrade
STEP 2: Apply the backup after upgrade
NOTE: The release will be a minor version bump -
v4.1.0