Skip to content
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

Inconsistent behavior across charts #424

Closed
Almenon opened this issue Oct 16, 2023 · 2 comments · Fixed by #508
Closed

Inconsistent behavior across charts #424

Almenon opened this issue Oct 16, 2023 · 2 comments · Fixed by #508

Comments

@Almenon
Copy link

Almenon commented Oct 16, 2023

The posit connect chart specifies the following:

    {{- if eq .Values.strategy.type "RollingUpdate" }}
    rollingUpdate:
      maxUnavailable: {{ .Values.strategy.rollingUpdate.maxUnavailable }}
      maxSurge: {{ .Values.strategy.rollingUpdate.maxSurge }}
    {{- end }}

The PM chart just has:

  {{- with .Values.strategy }}
  strategy:
    {{- toYaml . | nindent 4 }}
  {{- end }}

It would be nice if the templating was consistent, as this tripped me up when working with the charts. I thought just specifying strategy.type: RollingUpdate was enough because it worked for the connect chart, but in the PM chart you also need to specify rollingUpdate: null under strategy.

@colearendt
Copy link
Member

Thanks for reporting @Almenon ! To be clear: do you think that the Connect chart's approach is preferable?

@Almenon
Copy link
Author

Almenon commented Oct 30, 2023

I don't have much of a preference, but if you want me to pick one as the 'best' I'll pick the PM chart as it is more flexible. But up to you :)

Actually, yes, connect is preferable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants