Uploaded image for project: 'Service Binding'
  1. Service Binding
  2. APPSVC-1040

Cloud Native Postgres operator exposed host binding is wrong

XMLWordPrintable

    • False
    • False
    • +
    • Hide
      Before this update, binding the data values from a `Cluster` custom resource (CR) of the `postgresql.k8s.enterpriesedb.io/v1` API collected the `host` binding value from the `.metadata.name` field of the CR. The collected binding value is an incorrect hostname and the correct hostname is available at the `.status.writeService` field. With this update, the annotations that the Service Binding Operator uses to expose the binding data values from the backing service CR are now modified to collect the `host` binding value from the `.status.writeService` field. The Service Binding Operator uses these modified annotations to project the correct hostname in the `host` and `provider` bindings.
      Show
      Before this update, binding the data values from a `Cluster` custom resource (CR) of the `postgresql.k8s.enterpriesedb.io/v1` API collected the `host` binding value from the `.metadata.name` field of the CR. The collected binding value is an incorrect hostname and the correct hostname is available at the `.status.writeService` field. With this update, the annotations that the Service Binding Operator uses to expose the binding data values from the backing service CR are now modified to collect the `host` binding value from the `.status.writeService` field. The Service Binding Operator uses these modified annotations to project the correct hostname in the `host` and `provider` bindings.
    • AppSvc Sprint 211

            pedjak@gmail.com Predrag Knezevic (Inactive)
            pedjak@gmail.com Predrag Knezevic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: