-
Notifications
You must be signed in to change notification settings - Fork 84
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
NotAuthorizedOrNotFound in NLB Kuberentes Ingress Controller #408
Comments
It depends on how you have configured the IAM permissions for CCM. CCM should be having permission to use the reserved IP.
|
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.24.0
What happened?
When using "loadBalancerIP" in the Nginx Ingress Controller manifest. LoadBalancer returns failure
What you expected to happen?
When specifying reserved IP in "loadBalancerIP" manifest, load balancer must be created with specified IP
How to reproduce it (as minimally and precisely as possible)?
Create an Oracle Cloud Reserved IP
Insert LoadBalancerIP into the manifest:
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.5.1/deploy/static/provider/cloud/deploy.yaml
(404, NotAuthorizedOrNotFound, false) Authorization failed or requested resource not found.
Anything else we need to know?
I'm creating according documents:
https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengcreatingloadbalancer.htm#contengcreatingloadbalancer_topic_Specifying_Load_Balancer_Reservado_IP
I have full permission on my tenancy.
The Reserved IP is on the same IP as the Cluster...
If I don't specify LoadBalancerIP, the LB is successfully created!
The text was updated successfully, but these errors were encountered: