You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of k8s 1.26 the kubectl flag --prune-whitelist has been deprecated and --prune-allowlist has been created to replace it. We reference this flag in examples and instructions which are output from the CLI.
How should the problem be solved?
We should update these references of --prune-whitelist to --prune-allowlist once our minimum support k8s version is 1.26 or later.
We also use the flag in integration tests should update the usage of this flag once the version of kubectl in the dev image is 1.26 or later.
Any alternatives you've considered?
N/A
How would users interact with this feature?
No response
Would you like to work on this feature?
None
The text was updated successfully, but these errors were encountered:
Hi @nikzayn! Unfortunately, we cannot make this change until our minimum supported Kubernetes version is 1.26 or greater. It is currently 1.21. So any work on this issue will need to wait, for now.
What problem are you trying to solve?
As of k8s 1.26 the kubectl flag
--prune-whitelist
has been deprecated and--prune-allowlist
has been created to replace it. We reference this flag in examples and instructions which are output from the CLI.How should the problem be solved?
We should update these references of
--prune-whitelist
to--prune-allowlist
once our minimum support k8s version is 1.26 or later.We also use the flag in integration tests should update the usage of this flag once the version of kubectl in the dev image is 1.26 or later.
Any alternatives you've considered?
N/A
How would users interact with this feature?
No response
Would you like to work on this feature?
None
The text was updated successfully, but these errors were encountered: