aws / aws/eks-anywhere

ETCdadm cluster endpoints diverged from the actual ETCd machines

Open
#6,148 1 comment 0 reactions 0 assignees View on GitHub
external kind/bug
Dominant language
Go
Stars
2.1k
Forks
328
Avg merge
1d 4h
Merged PRs (30d)
9

Description

**What happened**:

ETCD Endpoints in `/etc/kubernetes/manifests/kube-apiserver.yaml` file do not match actual etcd cluster member ip.

**What you expected to happen**:

- Secret objects holding the etcd endpoint should have correct etcd member ips.
- As a workaround, manually changed the secrets holding the etcd endpoints secrets to reflect the right ones and the issues were resolved.

**How to reproduce it (as minimally and precisely as possible)**:
- n/a

**Anything else we need to know?**:

**Environment**:
- EKS Anywhere Release:
- EKS Distro Release:

Contributor guide

Open the contributing guide

Research direction

Start with /etc/kubernetes/manifests/kube-apiserver.yaml and the Secret objects holding the etcd endpoints. Compare those values with the actual etcd cluster member IPs and trace where the mismatched endpoints are produced. Done means the generated endpoint values match the member IPs and the reported workaround is no longer needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
distributed-systems, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.