-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] ...AMQ Streams Kafka Operator installation failed on Openshift 4.3.18 Version #3059
Comments
This is related to JDK8u252 and fabric8io/kubernetes-client#2212. This does not affect Strimzi 0.17.0 which is using older version of Java. Issues related to Red Hat AMQ Streams should be reaised within Red Hat. You should be able to workaround it by disabling HTTP2:
- name: HTTP2_DISABLE
value: "true"
apiVersion: kafka.strimzi.io/v1alpha1
kind: Kafka
metadata:
name: my-cluster
spec:
kafka:
# ...
template:
initContainer:
env:
- name: HTTP2_DISABLE
value: true
zookeeper:
# ...
entityOperator:
topicOperator:
# ...
userOperator:
# ...
template:
topicOperatorContainer:
env:
- name: HTTP2_DISABLE
value: true
userOperatorContainer:
env:
- name: HTTP2_DISABLE
value: true |
For Openshift 4.x, I could address this issue by adding the environment variable at subscription object, that would add this into all the containers that are managed by the Operator.
oc get csv -n openshift-operators
oc get pods -n openshift-operators
|
That is a neat trick ... I didn't knew about it. Thanks for sharing. |
Thanks for Subscription trick.. its working fine. |
Describe the bug
install failed: Timeout: deployment amq-streams-cluster-operator-v1.4.1 not ready before timeout: deployment "amq-streams-cluster-operator-v1.4.1" exceeded its progress deadline
To Reproduce
Steps to reproduce the behavior:
Installation Mode : All namespaces
Channel : stable
Approval Strategy : Automatic
Expected behavior
Kafka operator should installed without any issue.
Environment (please complete the following information):
YAML files and logs
The text was updated successfully, but these errors were encountered: