Skip to content

Disabling Kubernetes KMS v2

You can disable KMS encryption and migrate to local etcd encryption to simplify operations or resolve external KMS connectivity issues.

Warning

Kubernetes KMS v2 is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

Disable KMS encryption

You can disable external KMS encryption and migrate to local encryption to simplify operations or resolve KMS connectivity issues.

Prerequisites

  • You have access to the cluster as a user with the cluster-admin role.
  • You have created an etcd backup.

Warning

Re-encryption of all etcd data will occur.

Procedure

  1. Edit the APIServer custom resource by entering the following command:

    $ oc edit apiserver cluster

  2. Change the encryption configuration:

    apiVersion: config.openshift.io/v1
kind: APIServer
metadata:
  name: cluster
spec:
  encryption:
    type: <encryption>

    Replace <encryption> with aescbc, aesgcm, or identity.

  3. Save and exit.

    OpenShift Container Platform automatically migrates etcd data. Migration time depends on etcd size and secret count.

  4. Monitor the migration progress by entering the following command:

    $ oc get openshiftapiserver -o=jsonpath='{range .items[0].status.conditions[?(@.type=="Encrypted")]}{.reason}{"\n"}{.message}{"\n"}{end}'

    Wait until the output shows EncryptionCompleted.

  5. Verify kube-apiserver pods rolled out by entering the following command:

    $ oc get pods -n openshift-kube-apiserver -l app=openshift-kube-apiserver

  6. Remove the static pod manifest from each control plane node by running the following command:

    $ for node in $(oc get nodes --selector=node-role.kubernetes.io/master -o name | cut -d/ -f2); do
    echo "Removing static pod from $node..."
    oc debug node/$node -- chroot /host \
      rm -f /etc/kubernetes/manifests/vault-kms-plugin.yaml
  done

    The kubelet automatically stops static pods when their manifest is removed from /etc/kubernetes/manifests/.

  7. Clean up the socket directory by running the following command:

    $ for node in $(oc get nodes --selector=node-role.kubernetes.io/master -o name | cut -d/ -f2); do
    oc debug node/$node -- chroot /host rm -rf /var/run/kmsplugin
  done

  8. After backup retention period passes, decommission the KMS key.

Verification

  1. Verify the encryption type by entering the following command:

    $ oc get apiserver cluster -o jsonpath='{.spec.encryption.type}'

  2. Verify that a test secret uses the new encryption type:

    1. Create a test secret by entering the following command:

      $ oc create secret generic encryption-test --from-literal=key=value -n default

    2. Get an etcd pod name by entering the following command:

      $ oc get pods -n openshift-etcd -l app=etcd -o name | head -1

    3. Check the encryption prefix by entering the following command:

      $ oc exec -n openshift-etcd <etcd_pod_name> -- etcdctl get /kubernetes.io/secrets/default/encryption-test --print-value-only | hexdump -C | head -1

      Output should begin with k8s:enc:aescbc:v1:, k8s:enc:aesgcm:v1:, or show readable JSON for identity.

    4. Delete the test secret by entering the following command:

      $ oc delete secret encryption-test -n default

    Note

    Do not delete the KMS key until migration completes successfully.

Additional resources