Skip to content
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

Define a separate etcd metrics URL when using separate etcd events cluster #8230

Closed
khatrig opened this issue Nov 25, 2021 · 1 comment · Fixed by #8232
Closed

Define a separate etcd metrics URL when using separate etcd events cluster #8230

khatrig opened this issue Nov 25, 2021 · 1 comment · Fixed by #8232
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@khatrig
Copy link
Contributor

khatrig commented Nov 25, 2021

Environment:

  • Cloud provider or hardware configuration:
    On-prem baremtal host
  • OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
    Ubuntu 18.04
  • Version of Ansible (ansible --version):
    Ansible 2.10
  • Version of Python (python --version):
    3.8

Kubespray version (commit) (git rev-parse --short HEAD):
release-2.17

Network plugin used:
calico

Full inventory with variables (ansible -i inventory/sample/inventory.ini all -m debug -a "var=hostvars[inventory_hostname]"):

Command used to invoke ansible:

Output of ansible run:

Anything else do we need to know:
There is a need to define a separate metrics url:port (ETCD_LISTEN_METRICS_URLS) for events etcd cluster(etcd_events_cluster_setup: true). Currently, etcd uses the same port for both k8s etcd, and events etcd container causing etcd container startup failure as both containers listen on the same port.

@khatrig khatrig added the kind/bug Categorizes issue or PR as related to a bug. label Nov 25, 2021
@zhengtianbao
Copy link
Member

It's a confilct between etcd-event listen client port and etcd metrics port.
/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants