-
Notifications
You must be signed in to change notification settings - Fork 63
fix: move tcp-router healthcheck port to avoid clash #1526
fix: move tcp-router healthcheck port to avoid clash #1526
Conversation
[gh#kubecf-1199]
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.
Approving so that we get a build for SUSE QA to test on AWS because that was the only platform needing the healthcheck to enable the load balancer.
Please do not merge until tests have been successful.
EKS testing: Smoke:
Brians
|
The important part of the brains - The two tests using tcp-routing passed! |
Does that mean we can press the big green "Merge pull request" button and be done with it? |
IMHO yes. Let us wait until standup to check with @prabalsharma |
yes, I consider this as Passed |
The clash is in tcp-router and router both exporting port 80/http. Depending on racing in kubecf the wrong endpoint is exposed through the main service.
Description
Motivation and Context
See #1199
How Has This Been Tested?
Minikube deployment, diego/SA. Roles are green, passed smoke and brain tests.
Use with ingress not tested.
This still needs testing on AWS, to be sure that the changed port is ok with AWS loadbalancers.
Types of changes
Checklist: