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

feat: option for app-controller Deployment instead of StatefulSet #77

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

34fathombelow
Copy link
Member

closes: #54

Comment on lines +1 to +3
{{- if .Values.controller.deployment }}
apiVersion: apps/v1
kind: Deployment
Copy link
Member

@jessesuen jessesuen Oct 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of having a whole new file, would it not be easier to change the kind based on the {{- if .Values.controller.deployment }} ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree it would be much easier. However I wanted to have a clear separation between the Deployment & StatefulSet, specifically if the number of replicas was increased beyond 1 and dynamicClusterDistribution was not enabled.

I'm happy to make the suggested changes if that makes more sense.

@34fathombelow 34fathombelow merged commit ff6c77e into master Oct 17, 2024
1 check passed
@34fathombelow 34fathombelow deleted the feat/app-controller-deployment branch October 17, 2024 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Option for app-controller Deployment instead of StatefulSet
2 participants