-
Notifications
You must be signed in to change notification settings - Fork 16
Open
Labels
bugSomething isn't workingSomething isn't working
Description
We are trying to deploy an instance of activemq but we can not access to the web console with a port-forward because it is not listening on 0.0.0.0.
At startup of init container, we can see this :
Creating Broker with args --silent --role admin --name amq-broker --http-host activemq-artemis-ss-0.activemq-artemis-hdls-svc.staging.svc.cluster.local --java-options=-Djava.net.preferIPv4Stack=true --user XXXXX --password XXXXX --allow-anonymous --data /opt/activemq-artemis/data --no-amqp-acceptor --no-hornetq-acceptor --no-mqtt-acceptor --no-stomp-acceptor --no-autotune --clustered --cluster-user XXXXX --cluster-password XXXXX --host activemq-artemis-ss-0.activemq-artemis-hdls-svc.staging.svc.cluster.local --nio at /home/jboss/amq-broker
we can see that http-host is set to the pod's FQDN. We want to have it listening on 0.0.0.0 but we can not change it.
I can see in launch.sh script that the BROKER_IP is set with hostname -f which is not an IP address in our case.
Should it be possible to fix this, or at least to have a way to override it ?
We can not set --http-host with EXTRA_ARGS env variable because it results with a duplicate flag which is forbidden.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working