Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

9.3. Configuring Network Encryption for an existing Trusted Storage Pool

You can configure network encryption for an existing Red Hat Gluster Storage Trusted Storage Pool for both I/O encryption and management encryption.

9.3.1. Enabling I/O encryption for a Volume
Copy link

Enable the I/O encryption between the servers and clients:
  1. Unmount the volume on all the clients. 
    # umount mount-point# umount mount-point
    Copy to Clipboard Toggle word wrap
  2. Stop the volume. 
    # gluster volume stop VOLNAME# gluster volume stop VOLNAME
    Copy to Clipboard Toggle word wrap
  3. Set the list of common names for clients allowed to access the volume. Be sure to include the common names of all the servers. 
    # gluster volume set VOLNAME auth.ssl-allow 'server1,server2,server3,client1,client2,client3'# gluster volume set VOLNAME auth.ssl-allow 'server1,server2,server3,client1,client2,client3'# gluster volume set VOLNAME auth.ssl-allow 'server1,server2,server3,client1,client2,client3'# gluster volume set VOLNAME auth.ssl-allow 'server1,server2,server3,client1,client2,client3'
    Copy to Clipboard Toggle word wrap
  4. Enable client.ssl and server.ssl on the volume. 
    # gluster volume set VOLNAME client.ssl on
# gluster volume set VOLNAME server.ssl on
    Copy to Clipboard Toggle word wrap
  5. Start the volume. 
    # gluster volume start VOLNAME# gluster volume start VOLNAME
    Copy to Clipboard Toggle word wrap
  6. Mount the volume from the new clients. For example, to manually mount a volume and access data using Native client, use the following command: 
    # mount -t glusterfs server1:/test-volume /mnt/glusterfs
    Copy to Clipboard Toggle word wrap

9.3.2. Enabling Management Encryption
Copy link

Though, Red Hat Gluster Storage can be configured only for I/O encryption without using management encryption, management encryption is recommended. On an existing installation, with running servers and clients, schedule a downtime of volumes, applications, clients, and other end-users to enable management encryption.
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.
  1. Unmount the volume on all the clients. 
    # umount mount-point# umount mount-point
    Copy to Clipboard Toggle word wrap
  2. Stop all the volumes. 
    # gluster volume stop VOLNAME# gluster volume stop VOLNAME
    Copy to Clipboard Toggle word wrap
  3. Stop glusterd on all servers. 
    # service glusterd stop
    Copy to Clipboard Toggle word wrap
  4. Stop all gluster-related processes on all servers. 
    # pkill glusterfs
    Copy to Clipboard Toggle word wrap
  5. Create the /var/lib/glusterd/secure-access file on all servers and clients. 
    # touch /var/lib/glusterd/secure-access
    Copy to Clipboard Toggle word wrap
  6. Start glusterd on all the servers. 
    # service glusterd start
    Copy to Clipboard Toggle word wrap
  7. Start all the volumes 
    # gluster volume start VOLNAME# gluster volume start VOLNAME
    Copy to Clipboard Toggle word wrap
  8. Mount the volume on all the clients. For example, to manually mount a volume and access data using Native client, use the following command: 
    # mount -t glusterfs server1:/test-volume /mnt/glusterfs
    Copy to Clipboard Toggle word wrap
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat