-
Notifications
You must be signed in to change notification settings - Fork 183
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
Helm Chart initial commit #118
Conversation
what is |
That is a randomly generated release name. You can override release name by passing in the |
Can we provide a default release name to avoid this without having the customer specify |
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.
LGTM
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.
LGTM overall
{{/* | ||
Create a default fully qualified app name. | ||
We truncate at 63 chars because some Kubernetes name fields are limited to this (by the DNS naming spec). | ||
If dryRun=true, we use fixed value "fluentd". |
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.
when we need to generate yaml files, we would set dryRun
(for the lack of a better name) to true to use fixed values for release name and the app label
eg.
helm template ./sumologic --set dryRun=true --namespace sumologic
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 do we need this?
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.
this is such that the generated yaml for non-helm users will be consistent with the yaml we currently provide in the repo. for example our current yaml uses fluentd
as the name for a lot of resources but in helm we would prefix with the release name followed by the chart name
What does the |
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.
Overall, LGTM but some comments
{{/* | ||
Create a default fully qualified app name. | ||
We truncate at 63 chars because some Kubernetes name fields are limited to this (by the DNS naming spec). | ||
If dryRun=true, we use fixed value "fluentd". |
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 do we need this?
image: | ||
repository: sumologic/kubernetes-fluentd | ||
tag: 0.0.0 | ||
pullPolicy: Always |
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.
When we do make this officially released, this should default to IfNotPresent, not always.
969eb7b
@yuting-liu is looking into adding the dependencies into the chart and it will be done in a separate PR. The chart in the current PR will not install prometheus or fluent-bit |
flushInterval: 5 | ||
|
||
## Increase number of http threads to Sumo. May be required in heavy logging clusters | ||
numThreads: 1 |
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 think we changed default to 4?
Create the Helm chart. Dependencies and automation of yaml generation will be in separate PRs.
Output of
helm install
: