Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

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
Link kopieren

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
Link kopieren

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.
Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat