Details
-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
8
-
App Services Sprint 184, Sprint 185, Sprint 189
Description
Why
Today, we support binding a secret only to podSpec compliant types. However, many types including KafkaSource which are not podSpec compliant.
We would like to support an optional field to let the user specify where to inject the binding secret's reference name the way we do in `envFrom` today.
Acceptance Criteria
Support a new attribute called bindingSecretPath in the CRD. A User should be able to provide where the secret is being bound instead of the default podSpec path.
apiVersion: apps.openshift.io/v1alpha1 kind: ServiceBindingRequest metadata: name: eventsource-binding-foo-bar namespace: service-binding-demo spec: applicationSelector: bindingPath: customSecretPath: spec.eventSourceSecret # <--- In KafkaSource group: sources.eventing.knative.dev resource: kafkasources resourceRef: my-kafka-source version: v1alpha1 backingServiceSelectors: - group: kafka.strimzi.io version: v1beta1 kind: KafkaTopic resourceRef: my-kafka-topic - group: kafka.strimzi.io version: v1beta1 kind: Kafka resourceRef: my-kafka-cluster
apiVersion: sources.eventing.knative.dev/v1alpha1
kind: KafkaSource
metadata:
name: my-kafka-source
spec:
consumerGroup: knative-group
eventSourceSecret: eventsource-binding-foo-bar-binding-secret <--- Associated made by service binding operator
sink:
ref:
apiVersion: serving.knative.dev/v1alpha1
kind: Service
name: event-display