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

Updating helm chart #130

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Updating helm chart #130

wants to merge 2 commits into from

Conversation

CharlyF
Copy link
Contributor

@CharlyF CharlyF commented Jan 24, 2022

What does this PR do?

Upon merging releasing 0.4.0, we update the chart.

Motivation

seamless upgrade experience for users.

Additional Notes

Anything else we should know when reviewing?

Describe your test plan

Write there any instructions and details you may have to test your PR.

@CharlyF CharlyF requested a review from a team as a code owner January 24, 2022 23:45
@CharlyF
Copy link
Contributor Author

CharlyF commented Jan 28, 2022

Merge when 0.4.o is released.

@CharlyF CharlyF added this to the v0.4.0 milestone Jan 28, 2022
@@ -25,9 +31,12 @@ spec:
- JSONPath: .spec.maxReplicas
name: max replicas
type: integer
- JSONPath: .spec.dryRun
- JSONPath: .status.conditions[?(@.type=="DryRun")].status
Copy link
Collaborator

Choose a reason for hiding this comment

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

This is what I was talking about during the standup.

Comment on lines +10 to +15
- JSONPath: .status.conditions[0].type
name: condition
type: string
- JSONPath: .status.conditions[0].status
name: condition status
type: string
Copy link
Collaborator

Choose a reason for hiding this comment

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

how can we be sure it is always the first item in the conditions slice?

ddProfiling:
enabled: false

workers: 1
Copy link
Collaborator

Choose a reason for hiding this comment

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

IMO to be backward compatible the workers value should be empty. because here you will always add the new args that doesn't exist on previous version.

OR, you add an if in the template file. Something like

            {{- if no eq (int .Values.workers) 1 }}
             - -workers={{ .Values.workers }}
            {{- end }}     

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

Successfully merging this pull request may close these issues.

None yet

2 participants