Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

8.4. Disabling Encryption

You can disable encryption for on Red Hat Openshift Container Storage setup in the following two scenarios:
  • Disabling I/O Encryption for a Volume
  • Disabling Management Encryption

8.4.1. Disabling I/O Encryption for all the Volumes
Copiar enlace

Execute the following commands to disable the I/O encryption between the servers and clients for a volume:

Note

The servers are the OpenShift nodes on which Red Hat Gluster Storage pods are running.
The clients are the remaining OpenShift nodes on which Red Hat Gluster Storage is not running.
  1. Stop all the application pods that have the Red Hat Gluster Storage volumes.
  2. Stop all the volumes. 
    # oc rsh <gluster_pod_name> gluster volume stop VOLNAME
    Copy to Clipboard Toggle word wrap
  3. Reset all the encryption options for a volume: 
    # oc rsh <gluster_pod_name> gluster volume reset VOLNAME auth.ssl-allow
# oc rsh <gluster_pod_name> gluster volume reset VOLNAME client.ssl
# oc rsh <gluster_pod_name> gluster volume reset VOLNAME server.ssl
    Copy to Clipboard Toggle word wrap
  4. Delete the files that were used for network encryption using the following command on all the OpenShift nodes: 
    # rm /etc/ssl/glusterfs.pem /etc/ssl/glusterfs.key /etc/ssl/glusterfs.ca
    Copy to Clipboard Toggle word wrap

    Note

    Deleting these files in a setup where management encryption is enabled will result in glusterd failing on all gluster pods and hence should be avoided.
  5. Stop the Red Hat Gluster Storage pods. 
    # oc delete daemonset glusterfs
    Copy to Clipboard Toggle word wrap
  6. On deletion of daemon set the pods go down. To verify if the pods are down, execute the following command: 
    # oc get pods
    Copy to Clipboard Toggle word wrap
  7. Create the Red Hat Gluster Storage daemonset by executing the following command:

    Note

    For Ansible deployments, the image name and the version has to be specified in the template, before executing the command. 
    # oc process glusterfs | oc create -f -
    Copy to Clipboard Toggle word wrap
  8. On creation of daemon set the pods are started. To verify if the pods are started, execute the following command: 
    # oc get pods
    Copy to Clipboard Toggle word wrap
  9. Start the volume. 
    # oc rsh <gluster_pod_name> gluster volume start VOLNAME
    Copy to Clipboard Toggle word wrap
  10. Start the application pods to use the I/O encrypted Red Hat Gluster Storage volumes.

8.4.2. Disabling Management Encryption
Copiar enlace

You cannot currently change between unencrypted and encrypted connections dynamically. Bricks and other local services on the servers and clients do not receive notifications from glusterd if they are running when the switch to management encryption is made.
Execute the following commands to disable the management encryption
  1. Stop all the application pods that have the Red Hat Gluster Storage volumes.
  2. Stop all the volumes. 
    # oc rsh <gluster_pod_name> gluster volume stop VOLNAME
    Copy to Clipboard Toggle word wrap
  3. Stop the Red Hat Gluster Storage pods. 
    # oc delete daemonset glusterfs
    Copy to Clipboard Toggle word wrap
  4. On deletion of daemon set the pods go down. To verify if the pods are down, execute the following command: 
    # oc get pods
    Copy to Clipboard Toggle word wrap
  5. Delete the /var/lib/glusterd/secure-access file on all OpenShift nodes to disable management encryption. 
    # rm /var/lib/glusterd/secure-access
    Copy to Clipboard Toggle word wrap
  6. Delete the files that were used for network encryption using the following command on all the OpenShift nodes: 
    # rm /etc/ssl/glusterfs.pem /etc/ssl/glusterfs.key /etc/ssl/glusterfs.ca
    Copy to Clipboard Toggle word wrap
  7. Create the Red Hat Gluster Storage daemonset by executing the following command:

    Note

    For Ansible deployments, the image name and the version has to be specified in the template, before executing the command. 
    # oc process glusterfs | oc create -f -
    Copy to Clipboard Toggle word wrap
  8. On creation of daemon set the pods are started. To verify if the pods are started, execute the following command: 
    # oc get pods
    Copy to Clipboard Toggle word wrap
  9. Start all the volumes. 
    # oc rsh <gluster_pod_name> gluster volume start VOLNAME
    Copy to Clipboard Toggle word wrap
  10. Start the application pods to use the management encrypted Red Hat Gluster Storage.
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat