Chapter 6. Known issues
This section lists the known issues for AMQ Streams 1.7.
6.1. Issue with deploying the Cluster Operator to an IPv6 cluster Copy linkLink copied to clipboard!
Description and workaround
The AMQ Streams Cluster Operator does not start on Internet Protocol version 6 (IPv6) clusters.
There are two workarounds for this issue.
Workaround one: Set the KUBERNETES_MASTER environment variable
Display the address of the Kubernetes master node of your OpenShift Container Platform cluster:
oc cluster-info Kubernetes master is running at MASTER-ADDRESS # ...
oc cluster-info Kubernetes master is running at MASTER-ADDRESS # ...Copy to Clipboard Copied! Toggle word wrap Toggle overflow Copy the address of the master node.
List all Operator subscriptions:
oc get subs -n OPERATOR-NAMESPACE
oc get subs -n OPERATOR-NAMESPACECopy to Clipboard Copied! Toggle word wrap Toggle overflow Edit the
Subscriptionresource for AMQ Streams:oc edit sub amq-streams -n OPERATOR_NAMESPACE
oc edit sub amq-streams -n OPERATOR_NAMESPACECopy to Clipboard Copied! Toggle word wrap Toggle overflow In
spec.config.env, add theKUBERNETES_MASTERenvironment variable, set to the address of the Kubernetes master node. For example:Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Save and exit the editor.
Check that the
Subscriptionwas updated:oc get sub amq-streams -n OPERATOR-NAMESPACE
oc get sub amq-streams -n OPERATOR-NAMESPACECopy to Clipboard Copied! Toggle word wrap Toggle overflow Check that the Cluster Operator
Deploymentwas updated to use the new environment variable:oc get deployment CLUSTER-OPERATOR-DEPLOYMENT-NAME
oc get deployment CLUSTER-OPERATOR-DEPLOYMENT-NAMECopy to Clipboard Copied! Toggle word wrap Toggle overflow
Workaround two: Disable hostname verification
List all Operator subscriptions:
oc get subs -n OPERATOR-NAMESPACE
oc get subs -n OPERATOR-NAMESPACECopy to Clipboard Copied! Toggle word wrap Toggle overflow Edit the
Subscriptionresource for AMQ Streams:oc edit sub amq-streams -n OPERATOR_NAMESPACE
oc edit sub amq-streams -n OPERATOR_NAMESPACECopy to Clipboard Copied! Toggle word wrap Toggle overflow In
spec.config.env, add theKUBERNETES_DISABLE_HOSTNAME_VERIFICATIONenvironment variable, set totrue. For example:Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Save and exit the editor.
Check that the
Subscriptionwas updated:oc get sub amq-streams -n OPERATOR-NAMESPACE
oc get sub amq-streams -n OPERATOR-NAMESPACECopy to Clipboard Copied! Toggle word wrap Toggle overflow Check that the Cluster Operator
Deploymentwas updated to use the new environment variable:oc get deployment CLUSTER-OPERATOR-DEPLOYMENT-NAME
oc get deployment CLUSTER-OPERATOR-DEPLOYMENT-NAMECopy to Clipboard Copied! Toggle word wrap Toggle overflow
6.2. Issue with 3scale discovery of the Kafka Bridge service Copy linkLink copied to clipboard!
Description and workaround
Red Hat 3scale cannot discover the Kafka Bridge service as documented in Deploying 3scale for the Kafka Bridge.
Workaround
Perform the following steps in your AMQ Streams cluster to enable service discovery:
Edit the
specproperties for theKafkaBridgecustom resource.Add the
discovery.3scale.net: truetemplate property to your existing configuration:Example template configuration for Kafka Bridge
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - 1
- Enables 3scale to discover the Kafka Bridge service.
Create or update the custom resource:
kubectl apply -f KAFKA-BRIDGE-CONFIG-FILE
kubectl apply -f KAFKA-BRIDGE-CONFIG-FILECopy to Clipboard Copied! Toggle word wrap Toggle overflow - Continue with 3scale service discovery as described in step six of Deploying 3scale for the Kafka Bridge.