-
Notifications
You must be signed in to change notification settings - Fork 50
sidb with loadBalancer=true Unhealth and unavalable #149
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
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.
|
@rbaumgar please try to create the service and let me know if you still see the issue. |
@psaini79 see entry from Oct 25. |
@rbaumgar thanks for the reply and sorry I didn't realize you already tried. Since you need only internal service to connect to the DB pod and you also used the selectors, did the service you create helped? Also, you want to to connect to DB on port 8080? If you need this connection for DB connection then DB port is 1521. |
@psaini79 Yes, creating a service helped. Yes, you are right. Port 1521 has to be used. Not a perfect example. |
Thanks @rbaumgar . Closing this issue, please open new one if you have any question. |
@psaini79, I don't know why you closed this issue. It is not solved; I only presented a workaround. |
I closed as it seems the problem from openshift side. I think your main concern that it should happen automatically from Oracle DB operator and in this case you did it manually. Let me test this scenario on openshift. I have following questions before I replicate the problem:
|
At the time of testing, it was on a baremetal cluster and OpenShift Local version 4.17. |
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: