-
Bug
-
Resolution: Done
-
Major
-
None
We do not have eap operator on the stage OperatorHub WFWIP-232, so I could not try myself. But this questions arise.
deploy/configmap-eap-operator.gen.yaml
...
deployments: - name: eap-operator
spec: replicas: 1
selector: matchLabels: name: eap-operator
strategy: {}
template: metadata: labels: name: eap-operator
spec: containers: - command: - wildfly-operator
env: - name: WATCH_NAMESPACE
valueFrom: fieldRef: fieldPath: metadata.annotations['olm.targetNamespaces']
...
deploy/operator-group.yaml
apiVersion: operators.coreos.com/v1 kind: OperatorGroup metadata: name: example namespace: eap-operator spec: targetNamespaces: - eap-operator
1. Does it mean operator by default watch only eap-operator namespace? Will that be parametrized in Web Console?
2. If user want to install operator to watch multiple/all namespaces how should he do? Will that be exposed in Web Console?
If I try to edit WATCH_NAMESPACE on eap-operator Deployment it is owerwriten back to
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: 'metadata.annotations[''olm.targetNamespaces'']'
- is blocked by
-
-
- Resolved
-
