Cannot create a binding to existing Cloudant service about cloud-operators HOT 5 CLOSED

@paolo yes this is more an issue about exposing the error at the CR level (inside status). Originally I had only the Binding object stuck in Pending state, and I had not idea why.

Now it is all working like a charm :-)

from cloud-operators.

logs:

{"level":"info","ts":1571344992.572309,"logger":"binding","msg":"Binding could not read service","cloudant":"Service.ibmcloud.ibm.com \"cloudant\" not found"}

from cloud-operators.

The plan Alias should be applied to a Service CR, not to a Binding (see https://github.com/IBM/cloud-operators/blob/master/docs/user-guide.md#referencing-an-existing-service ). Is this issue more about not getting some message about the error in the status then about binding ?

from cloud-operators.

This should be written as:

apiVersion: ibmcloud.ibm.com/v1alpha1
kind: Service
metadata:
    name: cloudant
spec:
    plan: Alias
    serviceName: cloudant
    serviceClass: cloudantnosqldb
---
apiVersion: ibmcloud.ibm.com/v1alpha1
kind: Binding
metadata:
  name: binding-cloudant
spec:
  serviceName: cloudant

The binding is failing because we are getting a 500 error from Bluemix. Investigating...

from cloud-operators.

In the original yaml, the plan:alias is ignored, the Binding object is just waiting for its service to be online and that is what the log message is indicating.

from cloud-operators.