I'm on RHEL, OCP 3.9.60. In anticipation of upgrading to 3.10 I am trying to determine if the v2 data I can see remaining in etcd is still relevant or if I can abandon it.
Given this step https://docs.openshift.com/container-platform/3.7/upgrading/migrating_etcd.html was executed successfully during the 3.7 upgrade I expect only v3 is in use. I would like to be sure since I still see v2 data. Can I confirm v2 is not in use? Support has been unclear so far. #!/bin/bash # etcd-ls2 . /etc/etcd/etcd.conf etcdctl \ --cert-file ${ETCD_PEER_CERT_FILE} \ --key-file ${ETCD_PEER_KEY_FILE} \ --ca-file ${ETCD_PEER_CA_FILE} \ --endpoints "${ETCD_ADVERTISE_CLIENT_URLS}" \ ls ${1:-/} [root@ose-test-etcd-01 bin]# ./etcd-ls2 /kubernetes.io /openshift.io #!/bin/bash # etcd-ls3 . /etc/etcd/etcd.conf ETCDCTL_API=3 etcdctl \ --cert ${ETCD_PEER_CERT_FILE} \ --key ${ETCD_PEER_KEY_FILE} \ --cacert ${ETCD_PEER_CA_FILE} \ --endpoints "${ETCD_ADVERTISE_CLIENT_URLS}" \ get / --prefix --keys-only | sed '/^\s*$/d' [root@ose-test-etcd-01 bin]# ./etcd-ls3 | head /kubernetes.io/apiservices/v1. /kubernetes.io/apiservices/v1.apps /kubernetes.io/apiservices/v1.apps.openshift.io /kubernetes.io/apiservices/v1.authentication.k8s.io /kubernetes.io/apiservices/v1.authorization.k8s.io /kubernetes.io/apiservices/v1.authorization.openshift.io /kubernetes.io/apiservices/v1.autoscaling /kubernetes.io/apiservices/v1.batch /kubernetes.io/apiservices/v1.build.openshift.io /kubernetes.io/apiservices/v1.image.openshift.io _______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
