-
Bug
-
Resolution: Done
-
Major
-
2.9.2.GA
-
None
-
None
- The drain cleaner cannot be installed because the ports key is not in the deployment file.
- When installing the drain cleaner in v2.9.2 LTS, the following error occurs.
$ oc apply -f install/drain-cleaner/openshift namespace/strimzi-drain-cleaner created serviceaccount/strimzi-drain-cleaner created clusterrole.rbac.authorization.k8s.io/strimzi-drain-cleaner created role.rbac.authorization.k8s.io/strimzi-drain-cleaner created clusterrolebinding.rbac.authorization.k8s.io/strimzi-drain-cleaner created rolebinding.rbac.authorization.k8s.io/strimzi-drain-cleaner created service/strimzi-drain-cleaner created validatingwebhookconfiguration.admissionregistration.k8s.io/strimzi-drain-cleaner created error: error parsing install/drain-cleaner/openshift/060-Deployment.yaml: error converting YAML to JSON: yaml: line 29: mapping values are not allowed in this context
- "ports" key is not in install/drain-cleaner/openshift/060-Deployment.yaml
-
apiVersion: apps/v1 kind: Deployment metadata: ... spec: ... template: ... spec: ... containers: - name: strimzi-drain-cleaner image: registry.redhat.io/amq-streams/drain-cleaner-rhel9:2.9.0 ports: <<-- !!! HERE !!! - containerPort: 8080 name: http - containerPort: 8443 name: https env: - name: STRIMZI_DRAIN_KAFKA value: "true" - name: STRIMZI_DRAIN_ZOOKEEPER value: "true"
- As far as I can see, there is no problem with ports key in v3.0 or v2.8.