-
Bug
-
Resolution: Done
-
Critical
-
Primaza 0.1
-
None
Description of problem:
Given the ServiceBinding
apiVersion: primaza.io/v1alpha1 kind: ServiceBinding metadata: name: demo-app-catalog-rds namespace: applications spec: application: apiVersion: apps/v1 kind: Deployment selector: matchLabels: app: demo-app-catalog
it is mounted to any deployment with a label with matching key (app), like the following
apiVersion: apps/v1 kind: Deployment metadata: labels: app.kubernetes.io/instance: demo-app-inner-loop name: demo-app-frontend namespace: applications spec: selector: matchLabels: app: demo-app-frontend strategy: template: metadata: labels: app: demo-app-frontend spec: containers: - env: - name: NGINX_PORT value: "8080" - name: SERVICE_BINDING_ROOT value: /bindings image: demo-app/frontend:latest name: demo-app-frontend ports: - containerPort: 8080 protocol: TCP volumeMounts: - mountPath: /bindings/demo-app-catalog-rds name: demo-app-catalog-rds readOnly: true volumes: - name: demo-app-catalog-rds projected: defaultMode: 420 sources: - secret: name: demo-app-catalog-rds
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
1. Create a deployment with label app=aaa
2. Create a ServiceBinding for deployment with label app=bbb
Actual results:
Service Binding data is mounted to all the deployments with label app=bbb
Expected results:
Service Binding data should NOT be mounted into deployment with label app=bbb
Reproducibility (Always/Intermittent/Only Once):
Always
Build Details:
Additional info:
Documentation Requirement: No