Upgrade Dex¶
This guide will walk you through upgrading Dex.
Fast Forward
If you are upgrading from EKF 2.0 or later, expand this box to fast-forward.
- Proceed to the Verify section.
Overview
What You’ll Need¶
- An upgraded management environment.
- An existing Kubernetes cluster.
- Your local clone of the Arrikto GitOps repository.
- Arrikto manifests for EKF version 2.0.2.
Procedure¶
Go to your GitOps repository, inside your
rok-tools
management environment:root@rok-tools:~# cd ~/ops/deploymentsDelete the Dex
Deployment
in theauth
namespace:root@rok-tools:~/ops/deployments# kubectl delete deploy -n auth dex \ > --ignore-not-found deployment.apps "dex" deletedNote
EKF 2.0.X deploys Dex as a
StatefulSet
with persistent storage provided by Rok.Upgrade Dex:
root@rok-tools:~/ops/deployments# rok-deploy --apply \ > kubeflow/manifests/common/dex/overlays/deployRemove any stale custom resources that Dex might have left behind while operating with Kubernetes CRDs as its storage backend:
root@rok-tools:~/ops/deployments# kubectl delete -n auth --all \ > --ignore-not-found \ > authcodes.dex.coreos.com,\ > authrequests.dex.coreos.com,\ > connectors.dex.coreos.com,\ > devicerequests.dex.coreos.com,\ > devicetokens.dex.coreos.com,\ > oauth2clients.dex.coreos.com,\ > offlinesessionses.dex.coreos.com,\ > passwords.dex.coreos.com,\ > refreshtokens.dex.coreos.com,\ > signingkeies.dex.coreos.com offlinesessions.dex.coreos.com "3opdnr6v5xfwg" deleted signingkey.dex.coreos.com "openid-connect-keys" deletedNote
EKF 2.0.X changes Dex’s storage backend from Kubernetes to SQLite3. As such, after applying the latest manifests, Dex will stop garbage collecting any existing CRs.