Open KshitizLohia opened 2 years ago
@KshitizLohia when deploying the helm charts, we loop to check for availability of the pods to move to the next step, so at first it may not find the etcd-0 pod, but then find it and move on. So was it stuck there, or was it just the check that initially failed?
Also, what's your use case for the Service Broker? Service Broker is being superseded by the Oracle Service Operator for Kubernetes (OSOK), which you can find here: https://github.com/oracle/oci-service-operator
That new version (OSOK) doesn't cover a few use cases, namely with Object Storage, but Object Storage in OSB is also limited to creating Pre-Authentication requests (PAR) for posting data, but not read or list files, so it is only really useful to post things like logs with no intention to use the files in the container. For all other use cases (like database connectivity / creation / credentials) I'd recommend going with OSOK.
Hi @streamnsight, I stuck here for 15 mins, it still waiting for pod etcd-0. Do you know how to fix it? Thanks !
null_resource.deploy_service_catalog (local-exec): waiting for catalog-catalog-webhook pod null_resource.deploy_etcd (local-exec): Error from server (NotFound): pods "etcd-0" not found null_resource.deploy_etcd (local-exec): waiting for pod etcd-0 null_resource.deploy_service_catalog (local-exec): waiting for catalog-catalog-webhook pod null_resource.deploy_service_catalog (local-exec): waiting for catalog-catalog-webhook pod null_resource.deploy_etcd (local-exec): Error from server (NotFound): pods "etcd-0" not found null_resource.deploy_etcd (local-exec): waiting for pod etcd-0 null_resource.deploy_etcd: Still creating... [15m30s elapsed]
getting the following exception when running the script with kubernetes version "v1.24.1"