Thanks for the heads up Humble. This would help many of the gluster
community users, who may not be following k8s threads actively to be
planning their migration plans actively.
For all the users who are currently running heketi + glusterfs, starting
from k8s v1.26, you CANNOT use heketi +
Hey Gluster Community,
As you might be aware, there is an effort in the kubernetes community to
remove in-tree storage plugins to reduce external dependencies and security
concerns in the core Kubernetes. Thus, we are in a process to gradually
deprecate all the in-tree external storage plugins
Yup.
Seems the /etc/sysconfig/glusterd setting got finally applied and I now
have a process like this:
root 4107315 0.0 0.0 529244 40124 ?Ssl ago08 2:44
/usr/sbin/glusterd -p /var/run/glusterd.pid --log-level ERROR
but bitd still spits out (some) 'I' lines
[2022-08-11
