Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-6152

Add a preconfigured etcdctl container to the etcd deployment

XMLWordPrintable

    • Proactive Architecture
    • False
    • None
    • False
    • Not Selected
    • OCPSTRAT-892Optimize & Enhance Etcd's Functionality, Performance, and Manageability w/ Hosted Control Planes

      In classic OCP every etcd pod has a container called etcdctl with env variables set so that running `etcdctl` without any flags connects to all 3 etcd endpoints with the right certificates and settings.

      It would be good to have that container also running in all HCP etcd pods to cut on time and not rely on etcd familiarity.

      AC:

      • Running
      oc rsh -c etcdctl -n ocm-production-${CLUSTER_ID}-lh-hypershift1 etcd-0 etcdctl endpoint status
      

      as an SRE-P shows the status of all 3 endpoints, the same command should also work with the "etcd-1" and "etcd-2" pod.

      • The etcdctl running inside the container doesn't rely on `--insecure-skip-tls-verify` (the currently deployed etcd server cert in HCP doesn't include pod IPs, but specifying --endpoints=10-128-10-1.etcd-client.ocm-production$CLUSTER_ID-lh-hypershift1.svc.cluster.local:2379,... instead of --endpoints=10.128.10.1:2379,... works fine and matches the cert SANs).

              azaalouk Adel Zaalouk
              ljakubow2.openshift Leszek Jakubowski
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: