-
Notifications
You must be signed in to change notification settings - Fork 16.8k
Conversation
Hi @askhalil. Thanks for your PR. I'm waiting for a helm 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. |
7c14acb
to
3930377
Compare
Selector labels on deployments are immutable and cannot be updated. This would be a major breaking change. Currently, there is work in progress to move this chart into the ingress-nginx repo and we are taking this opportunity to make breaking changes like this. Feel free to add this change there if it is not already fixed. |
@ChiefAlexander what if we make it as optional so people who will be using the chart for the first time they have the ability to allow it. |
That would be fine by me |
3930377
to
f6e868a
Compare
@ChiefAlexander I have updated the PR accordingly, so please have a look and approve it if it is okay |
f6e868a
to
ef88bd3
Compare
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 looks good. Other than the comment that I left can you also update the readme for this change. Once those two are resolved i'm good with this change.
stable/nginx-ingress/Chart.yaml
Outdated
@@ -1,6 +1,6 @@ | |||
apiVersion: v1 | |||
name: nginx-ingress | |||
version: 1.33.5 | |||
version: 1.33.6 |
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.
As we have added a feature to the chart please bump the minor version.
version: 1.33.6 | |
version: 1.34.0 |
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.
@ChiefAlexander I have addressed both of you comments but please have a look at the readme file after the upadte
ef88bd3
to
86796c9
Compare
Signed-off-by: Abdulrahman Khalil <a.skhalil93@gmail.com>
86796c9
to
e7f38f8
Compare
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: askhalil, ChiefAlexander 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 |
Unfortunately this introduced a regression that broke the connection between the controller service and the pods (the selector no longer matches). Can you please revert this change or fix forward? Also, please add a regression test so that this does not recur. |
Signed-off-by: Abdulrahman Khalil <a.skhalil93@gmail.com>
This is a regression. Breaks service monitor for instance #21873. Only half of the component labels have been changed why? If to change then to change all labels... Moreover app.kubernetes.io/component breaks prometheus and prometheus operator servicemonitor. |
Signed-off-by: Abdulrahman Khalil <a.skhalil93@gmail.com>
Signed-off-by: Abdulrahman Khalil <a.skhalil93@gmail.com>
Signed-off-by: Abdulrahman Khalil <a.skhalil93@gmail.com> Signed-off-by: Adrien Loiseau <adrien.loiseau@logic-immo.com>
Signed-off-by: Abdulrahman Khalil <a.skhalil93@gmail.com> Signed-off-by: Miguel Mingorance <miguel.mingorance@deliveryhero.com>
This will fix the issue where the HPA isn't able to read the metrics even when the resources of the controllers are set because the resources of the default-backend aren't set and both are using the same selectors