-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OPSEXP-2291 Bump Search services chart to most recent conventions #179
Conversation
83fcaf8
to
9bc425d
Compare
charts/alfresco-search-service/templates/secret-repository.yaml
Outdated
Show resolved
Hide resolved
7a474da
to
eecce1c
Compare
spec: | ||
replicas: {{ .Values.replicaCount }} | ||
selector: | ||
matchLabels: | ||
app: {{ template "alfresco-insight-zeppelin.fullName" . }} | ||
release: {{ .Release.Name }} | ||
{{- include "alfresco-insight-zeppelin.selectorLabels" . | nindent 6 }} | ||
strategy: | ||
type: RollingUpdate | ||
rollingUpdate: {{- toYaml .Values.global.strategy.rollingUpdate | nindent 6 }} | ||
template: | ||
metadata: | ||
annotations: | ||
checksum/config: {{ include (print $.Template.BasePath "/config.yaml") . | sha256sum }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please remove
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why? we have a configmap and should help if changing it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because it would lead to different behavior in case the user uses cm or values to configure the repo. Also this technic is more a workaround to me (e.g. a change in the metadata would also trigger pod recreation while not needed) and not a true feature. People should prefer solution such as reloader.
charts/alfresco-search-service/charts/alfresco-insight-zeppelin/templates/config.yaml
Show resolved
Hide resolved
charts/alfresco-search-service/templates/secret-repository.yaml
Outdated
Show resolved
Hide resolved
Apply automatic changes
Apply automatic changes
Apply automatic changes
b7a3419
to
180715b
Compare
bf28b61
to
603adaa
Compare
e076048
to
f145210
Compare
fb04888
to
353bd29
Compare
353bd29
to
883e04d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will insist on getting rid of the config/checksum which I really don't like
spec: | ||
replicas: {{ .Values.replicaCount }} | ||
selector: | ||
matchLabels: | ||
app: {{ template "alfresco-insight-zeppelin.fullName" . }} | ||
release: {{ .Release.Name }} | ||
{{- include "alfresco-insight-zeppelin.selectorLabels" . | nindent 6 }} | ||
strategy: | ||
type: RollingUpdate | ||
rollingUpdate: {{- toYaml .Values.global.strategy.rollingUpdate | nindent 6 }} | ||
template: | ||
metadata: | ||
annotations: | ||
checksum/config: {{ include (print $.Template.BasePath "/config.yaml") . | sha256sum }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because it would lead to different behavior in case the user uses cm or values to configure the repo. Also this technic is more a workaround to me (e.g. a change in the metadata would also trigger pod recreation while not needed) and not a true feature. People should prefer solution such as reloader.
Ref: OPSEXP-2291