We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 PodDisruptionBudget in k8s past version 1.25
Operator code explicitly references v1beta1.PodDisruptionBudget which is deprecated. This should be updated to v1.PodDistributionBudget https://pkg.go.dev/k8s.io/[email protected]/policy/v1#PodDisruptionBudget
Install operator on k8s 1.21+ and create a Redis cluster through the Operator, view the Operator logs
How are the pieces configured?
{ "jsonPayload": { "message": "policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget", "pid": "8" }, "sourceLocation": { "file": "warnings.go", "line": "70" } }
The text was updated successfully, but these errors were encountered:
working on a PR this week
Sorry, something went wrong.
@szelenka how about this? #405
my mistake, what's the expected release date for v1.2.0?
We will release this week
No branches or pull requests
Expected behaviour
Add PodDisruptionBudget in k8s past version 1.25
Actual behaviour
Operator code explicitly references v1beta1.PodDisruptionBudget which is deprecated. This should be updated to v1.PodDistributionBudget
https://pkg.go.dev/k8s.io/[email protected]/policy/v1#PodDisruptionBudget
Steps to reproduce the behaviour
Install operator on k8s 1.21+ and create a Redis cluster through the Operator, view the Operator logs
Environment
How are the pieces configured?
Logs
The text was updated successfully, but these errors were encountered: