-
Notifications
You must be signed in to change notification settings - Fork 86
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
[BUG REPORT] When creating a Load Balancer the backends of the backend set (TCP 80) are not created automatically. #423
Comments
GBT55
changed the title
[BUG REPORT] When creating a Load Balancer backend sets are not created automatically.
[BUG REPORT] When creating a Load Balancer the backends of the backend set (TCP 80) are not created automatically.
Apr 14, 2023
Please attach the logs from the cloud-controller-manager pod running in your cluster |
There you go @AkarshES |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT
Versions
CCM Version: v1.25.0
Environment:
kubectl version
): v1.25.9uname -a
): Linux kow-m02 5.15.0-1032-oracle Update to latest SHA of bmcs-go-sdk #38-Ubuntu SMP Thu Mar 23 19:30:10 UTC 2023 aarch64 aarch64 aarch64 GNU/LinuxWhat happened?
When creating a Load Balancer with the Nginx example from https://github.com/oracle/oci-cloud-controller-manager/blob/master/docs/tutorial.md the backends of the backend set (TCP 80) aren't automatically created.
What you expected to happen?
That the the backends of the backend set (TCP 80) would be created automatically.
How to reproduce it (as minimally and precisely as possible)?
Use the example from https://github.com/oracle/oci-cloud-controller-manager/blob/master/docs/tutorial.md and append the following annotations to the LB service:
Then this LB will be created, with a backend configured TCP 80, but empty of backends inside it
Anything else we need to know?
If I try to curl the web, this happens:
But, If I create the backends myself (via the web console) then I'm able to connect to the webpage e.g.
The text was updated successfully, but these errors were encountered: