-
Notifications
You must be signed in to change notification settings - Fork 16.8k
[stable/superset] Use the target port number instead of a name #7857
Conversation
Hi @legal90. 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 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. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
It's not stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
da1ff96
to
8207b6e
Compare
8207b6e
to
3b8bd47
Compare
3b8bd47
to
923a161
Compare
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
923a161
to
36d1170
Compare
/assign @prydonius |
Older (but still actual) versions of some Network Policy providers don't support named ports as a value of `targetPort` field in the Service spec. Changing it to the number shouldn't break the UX for existing installations. Signed-off-by: Mikhail Zholobov <[email protected]>
Signed-off-by: Mikhail Zholobov <[email protected]>
36d1170
to
98d74e2
Compare
@prydonius @cpanato Could you please review? |
/ok-to-test |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, legal90 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 |
Older (but still actual) versions of some Network Policy providers don't support named ports as
a value of
targetPort
field in the Service spec:Changing it to the number shouldn't break the UX for existing installations because the container port 8088 is still hard-coded here:
charts/stable/superset/templates/deployment.yaml
Line 57 in 6b518ce