-
Notifications
You must be signed in to change notification settings - Fork 819
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
Remove redundant "helm test" pod from "install.yaml" #1591
Conversation
helm test
pod in install.yaml
helm test
pod in install.yaml
Build Succeeded 👏 Build Id: ec631017-80b1-40e8-831c-b5a573b44d16 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
gameservers: | ||
namespaces: | ||
- default | ||
minPort: 7000 | ||
maxPort: 8000 | ||
|
||
helm: |
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.
Question - should this be on by default? Or should it be off?
I would have thought "off" would be better? Or no?
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.
Generally this PR lacks of changes to helm.md
. There is a statement about use helm test agones --cleanup
as a simple test of your installation.
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.
Right, but should we be installing this test pod by default on production deployments by default?
This seems to me like this is something people should opt into, rather than opt out. I didn't realise that the helm test would be installing a test pod on each cluster -- or maybe I'm missing something?
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.
+1 for making it false by default, to match what this is changing in install.yaml.
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.
Agree, I have updated this PR and subj.
eab1756
to
9043a13
Compare
Build Failed 😱 Build Id: ade1dad6-dbab-4c1b-8de0-f22af9a85764 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Helm test template would create an additional pod in an error state. Add new Helm variable to avoid creating new pod.
Build Succeeded 👏 Build Id: 4dc68644-028f-44e1-85be-527784decbe0 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
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.
👍
New changes are detected. LGTM label has been removed. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aLekSer, markmandel The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Helm test template would create an additional pod in an error state. Add new Helm variable to avoid creating new pod. Co-authored-by: Mark Mandel <markmandel@google.com>
What type of PR is this?
/kind cleanup
What this PR does / Why we need it:
Helm test template would create an additional pod in an error state.
Add new Helm variable to avoid creating new pod.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Thanks to Davit Mkrtchyan for pointing on this issue.