Updated GlusterFS to 4.0 in Hypercube image #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated Dockerfile to install the latest stable release of GlusterFS, 4.0. This fixes a problem when mounting Gluster volumes created on a GlusterFS 4.0 server. See kubernetes#65093
What this PR does / why we need it:
The current image uses Cluster 3.7.6, 5 minor versions behind, and 1 one major release behind (and countless patch versions). If someone tries to mount a Gluster volume from a server that is using GlusterFS 3.9+, the volume will fail to mount with the following error:
Server is operating at an op-version which is not supported
Sysadmins are using Gluster 4.0 because of the many performance improvements over 3.7.6, and added integrity features such as bitrot scrubbing. Not to mention, Gluster 4.0 includes a REST API that is meant to assist with dynamic provisioning for platforms like Kubernetes.
Which issue(s) this PR fixes :
Fixes kubernetes#65093
Special notes for your reviewer:
We've tested these changes and are running it in production currently.
Release note: