Support Secrets Manager

[haf-tech]

Provisioning IBM Secrets Manager works if creating a new or using existing one. But the binding does not work, means no secret will be created.

Definition

apiVersion: ibmcloud.ibm.com/v1
kind: Service
metadata:
  name: secret-manager-demo
  namespace: ico-test
spec:
  plan: lite
  serviceClass: secrets-manager
---
apiVersion: ibmcloud.ibm.com/v1
kind: Binding
metadata:
    name: secret-manager-demo
    namespace: ico-test
spec:
    serviceName: secret-manager-demo

Error message

2020-12-21T17:54:43.744Z        INFO    controllers.Binding     controllers/binding_controller.go:451   Creating        {"credentials": "secret-manager-demo"}
2020-12-21T17:54:46.295Z        INFO    controllers.Binding     controllers/binding_controller.go:380   Request failed with status code: 400, ServerErrorResponse: {"message":"Service Broker returned error status code 404","status_code":400,"transaction_id":"bss-5dd8afa0e37bae82"}

Env:

• OpenShift 4.5
• IBM Cloud Operator 1.0.0

[otrebor]

I have the same problem.

• Openshift 4.7
• Ibm Cloud Operator 1.1.0

[JohnStarich]

Service Broker returned error status code 404

Looks like Resource Controller sent a request to Secret Manager and it failed. ICO works well with other services and bindings, so I’d recommend reaching out to support (or that team if you’re an IBMer). Be sure to mention you’re using Resource Controller’s API via IBM Cloud Operator.