-
Notifications
You must be signed in to change notification settings - Fork 47
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
sidb with loadBalancer=true Unhealth and unavalable #149
Comments
Hello Robert, please do send some oraoperator pod logs along anyway, it seems as if it's waiting for something (an IP address from the loadbalancer?) and will not update the database status but also wont error out then. Can You also see a service of type LoadBalancer which maybe is PENDING , waiting for an IP address ? |
you are right, svc extrnal-ip is pending. But I don't want external IP...
Operator log when "loadBalancer=true"
|
@rbaumgar I don' think the problem is from the operator code. So if the cloud provider requires some service annotation for the load balancer then you have to give that in the singleinstancedatabase config yaml file. Can I know which provider are you using ? And please try just to deploy a load balancer on the provider to check what annotation are required |
@IshaanDesai45 it's on OpenShift and I don't want an external IP. I only want an IP from the pod network. |
So you would need to create a private/internal load balancer if you don't want an external IP. OpenShift might have some service annotations for creating the same like OKE have it here |
What do you think is needed to create a service in OpenShift? No annotation is required.
|
When I create a sidb (enterprise, free, xe, ..) it works fine until I set loadBalancer = true.
db orperator is namespace based.
No error in operator log!
siddb.yaml
status:
status after loadBalancer=true
The text was updated successfully, but these errors were encountered: