-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Use a different healthcheck port for AWS CSI controller #16909
Conversation
…monset This avoids port conflicts when both run as hostNetwork
/test pull-kops-e2e-aws-upgrade-k130-ko130-to-klatest-kolatest-many-addons |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman 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 |
…09-origin-release-1.30 Automated cherry pick of #16909: Use a different healthcheck port for AWS CSI controller
@rifelpet fyi this conflicts with default port set by aws-efs-csi helm chart https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/9b81560bc204cf52c9f44e7f31d6876893f57e06/charts/aws-efs-csi-driver/values.yaml#L203 |
This avoids port conflicts when both the deployment (controller) and daemonset (agent) run as hostNetwork
Example:
https://storage.googleapis.com/kubernetes-ci-logs/logs/e2e-kops-aws-upgrade-k127-ko130-to-k128-kolatest-many-addons/1846558413924864000/artifacts/cluster-info/kube-system/events.yaml