-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Chart: Deploy PodDisruptionBudget
with KEDA.
#11032
Chart: Deploy PodDisruptionBudget
with KEDA.
#11032
Conversation
Welcome @StuxxNet! |
Hi @StuxxNet. 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 Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
✅ Deploy Preview for kubernetes-ingress-nginx canceled.
|
/ok-to-test |
…s is greater than 1
e12c9d3
to
5f194a7
Compare
/assign |
/hold |
/retitle Chart: Deploy |
PodDisruptionBudget
with KEDA.
value: RELEASE-NAME-ingress-nginx-controller | ||
- equal: | ||
path: spec.minAvailable | ||
value: 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
value: 1 | |
value: 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This suggestions adds the requite line feed at the end of the file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also this was addressed in the last commit where the file was renamed :)
value: RELEASE-NAME-ingress-nginx-controller | ||
- equal: | ||
path: spec.minAvailable | ||
value: 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This suggestions adds the requite line feed at the end of the file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please rename the file to charts/ingress-nginx/tests/controller-poddisruptionbudget_test.yaml
. We used to have them named like the resources they are testing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey! May you please check if the naming is correct now? :D
charts/ingress-nginx/templates/controller-poddisruptionbudget.yaml
Outdated
Show resolved
Hide resolved
@@ -0,0 +1,22 @@ | |||
suite: Controller > Keda > PDB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suite: Controller > Keda > PDB | |
suite: Controller > PodDisruptionBudget |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also addressed!
charts/ingress-nginx/templates/controller-poddisruptionbudget.yaml
Outdated
Show resolved
Hide resolved
charts/ingress-nginx/tests/controller-poddisruptionbudget_test.yaml
Outdated
Show resolved
Hide resolved
…yaml Co-authored-by: Marco Ebert <[email protected]>
….yaml Co-authored-by: Marco Ebert <[email protected]>
@Gacko Hey! Thanks for the review. Indeed it looks way much simple now than it was before. Thanks for it! I just accepted the proposed changes :D |
/unhold Thanks a lot for your contribution and the nice collaboration! :) |
@Gacko: once the present PR merges, I will cherry-pick it on top of release-1.10 in a new PR and assign it to you. In response to this:
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. |
/kind bug |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment for clarification
{{- if .Values.controller.autoscaling.enabled }} | ||
{{- $replicas = .Values.controller.autoscaling.minReplicas }} | ||
{{- else if .Values.controller.keda.enabled }} | ||
{{- $replicas = .Values.controller.keda.minReplicas }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we need to add some docs for this?
What if the user enable both by mistake?
Can we try to use the OR instead or that does not work?
/hold for clarification
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, yeah, I get your point. HPA and KEDA being mutually exclusive always was a problem and looking at the particular resource templates, we are not even preventing that in there.
So right now what you see above is pretty close the best we can get without making the conditions too complex and unreadable.
I created an issue for improving and aligning that everywhere. But for now, I'd just go on and merge this PR. Aligning all these conditions is out of scope here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's the issue I created: #10814
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, Gacko, StuxxNet 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 |
@Gacko: new pull request created: #11105 In response to this:
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. |
What this PR does / why we need it:
Currently we deploy the PDB only if Keda is enabled. This PR tries to address this adding a new entry to the "if" statement to make it consider Keda also.
Types of changes
Which issue/s this PR fixes
fixes #10083
How Has This Been Tested?
The testing was done by creating a fresh deployment of the Ingress Nginx in a brand new Kind cluster running Kubernetes 1.29. Below you can see that the corresponding PDB object was created when the values for Keda were passed to the chart:
Checklist: