Skip to content

Incorrect Environment Property in kafka-ui.yaml Example #4535

Open
@eddycaballeroibm

Description

@eddycaballeroibm

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running master-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

The services.kafka1.environment.KAFKA_JMX_OPTS property is incorrect in the kafka-ui.yaml config file.

The property -Djava.rmi.server.hostname=kafka0 conflicts with the configuration of kafka0, which uses the same hostname.

services.kafka1.environment.KAFKA_JMX_OPTS

KAFKA_JMX_OPTS: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=kafka0 -Dcom.sun.management.jmxremote.rmi.port=9998

services.kafka0.environment.KAFKA_JMX_OPTS

KAFKA_JMX_OPTS: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=kafka0 -Dcom.sun.management.jmxremote.rmi.port=9997

This makes it impossible to connect to kafka0

Expected behavior

The property services.kafka1.environment.KAFKA_JMX_OPTS should be changed -Djava.rmi.server.hostname=kafka1.

KAFKA_JMX_OPTS: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=kafka1 -Dcom.sun.management.jmxremote.rmi.port=9998

This will allow you to connect.

Your installation details

  1. 83b5a60
  2. n/a
  3. https://github.com/provectus/kafka-ui/blob/master/documentation/compose/kafka-ui.yaml
  4. n/a

Steps to reproduce

  1. Start kafka-ui.yaml with the podman compose command
  2. Go to http://localhost:8080/ui/clusters/local/config
  3. Validate the config
  4. Connection will fail

Screenshots

No response

Logs

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    status/triageIssues pending maintainers triagetype/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions