[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: etcd v2 data after upgrade from 3.6 to 3.7



Dale,

I'm not finding the documentation right now, maybe it's a KCS article.
But no, we don't remove v2 keys after the migration process. They can
safely be removed after verifying that
kubernetesMasterConfig.apiServerArguments.storage-backend is set to
etcd3. ex :

kubernetesMasterConfig:
  apiServerArguments:
    storage-backend:
    - etcd3

One thing we do recommend is after removal that you create a new v2
key /kubernetes.io with a value of "migrated", this will prevent typos
in master-config.yaml from potentially reverting storage configuration
back to v2 and re-initializing the cluster. If your v2 data store is
sizable then each time you hit the snapshot count it's going to
re-snapshot both v2 and v3 data stores which may lead to extra IOps.

Of course be very careful to only remove v2 data and make sure to
create backups first.

--
Scott



On Fri, Feb 8, 2019 at 11:31 AM Dale Bewley <dale bewley net> wrote:
>
> 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


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]