You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a relic of the past, and makes adding an additional sidecar containers harder than it should be, as everything now requires templating if it needs to reference to existing volumes (e.g. VSM):
As doing {{ .Release.Name }} here and elsewhere in a Pod (e.g. container name) doesn't have any real gains, we should consider dropping it.
Since we want to avoid breaking existing deploy, a possible migration strategy might be to add server.nameFromReleaseName with the default set to true for the time being, which retains current behavior with a deprecation message, then switch to false sometimes in the future, and eventually drop the server.nameFromReleaseName/{{ .Release.Name }} usage altogether.
The text was updated successfully, but these errors were encountered:
This is a relic of the past, and makes adding an additional sidecar containers harder than it should be, as everything now requires templating if it needs to reference to existing volumes (e.g. VSM):
As doing
{{ .Release.Name }}
here and elsewhere in a Pod (e.g. container name) doesn't have any real gains, we should consider dropping it.Since we want to avoid breaking existing deploy, a possible migration strategy might be to add
server.nameFromReleaseName
with the default set totrue
for the time being, which retains current behavior with a deprecation message, then switch tofalse
sometimes in the future, and eventually drop theserver.nameFromReleaseName
/{{ .Release.Name }}
usage altogether.The text was updated successfully, but these errors were encountered: