At the 2019 sig-storage F2F a person asked if the library could combine the configMap endpoint data into the secret in order to reduce the number of k8s resources used by the lib. At scale this is probably a good suggestion.
We should decide if completely remove the configMap all together, or keep configMaps and secrets separate but define a setting/flag allowing them to be combined.
At the 2019 sig-storage F2F a person asked if the library could combine the configMap endpoint data into the secret in order to reduce the number of k8s resources used by the lib. At scale this is probably a good suggestion.
We should decide if completely remove the configMap all together, or keep configMaps and secrets separate but define a setting/flag allowing them to be combined.