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

Helm Chart initial commit #118

Merged
merged 7 commits into from
Aug 7, 2019
Merged

Helm Chart initial commit #118

merged 7 commits into from
Aug 7, 2019

Conversation

maimaisie
Copy link
Contributor

@maimaisie maimaisie commented Aug 2, 2019

Create the Helm chart. Dependencies and automation of yaml generation will be in separate PRs.

Output of helm install:

$ helm install helm/sumologic
NAME:   giggly-pike
LAST DEPLOYED: Fri Aug  2 11:24:49 2019
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1/ConfigMap
NAME                                 DATA  AGE
giggly-pike-sumologic-config         9     1s
giggly-pike-sumologic-events-config  2     1s

==> v1/Deployment
NAME                          READY  UP-TO-DATE  AVAILABLE  AGE
giggly-pike-sumologic         0/3    3           0          0s
giggly-pike-sumologic-events  0/1    1           0          0s

==> v1/Pod(related)
NAME                                           READY  STATUS             RESTARTS  AGE
giggly-pike-sumologic-d5dc9d85d-9ptld          0/1    Pending            0         0s
giggly-pike-sumologic-d5dc9d85d-b6sxd          0/1    Pending            0         0s
giggly-pike-sumologic-d5dc9d85d-kfhc2          0/1    Pending            0         0s
giggly-pike-sumologic-events-5db58c487d-9f722  0/1    ContainerCreating  0         0s

==> v1/Service
NAME                          TYPE       CLUSTER-IP     EXTERNAL-IP  PORT(S)                       AGE
giggly-pike-sumologic         ClusterIP  10.101.92.220  <none>       9888/TCP,24321/TCP,24231/TCP  0s
giggly-pike-sumologic-events  ClusterIP  10.99.214.103  <none>       24231/TCP                     0s

==> v1/ServiceAccount
NAME                   SECRETS  AGE
giggly-pike-sumologic  1        1s

==> v1beta1/ClusterRole
NAME                   AGE
giggly-pike-sumologic  1s

==> v1beta1/ClusterRoleBinding
NAME                   AGE
giggly-pike-sumologic  0s

@rvmiller89
Copy link
Contributor

$ helm install helm/sumologic
NAME:   giggly-pike

what is giggly-pike ?

@maimaisie
Copy link
Contributor Author

That is a randomly generated release name. You can override release name by passing in the --name flag to helm install

@rvmiller89
Copy link
Contributor

Can we provide a default release name to avoid this without having the customer specify --name flag?

rvmiller89
rvmiller89 previously approved these changes Aug 2, 2019
Copy link
Contributor

@rvmiller89 rvmiller89 left a comment

Choose a reason for hiding this comment

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

LGTM

deploy/helm/sumologic/values.yaml Outdated Show resolved Hide resolved
yuting-liu
yuting-liu previously approved these changes Aug 2, 2019
Copy link
Contributor

@yuting-liu yuting-liu left a comment

Choose a reason for hiding this comment

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

LGTM overall

deploy/helm/sumologic/Chart.yaml Outdated Show resolved Hide resolved
{{/*
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".
Copy link
Contributor Author

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

Copy link
Contributor

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?

Copy link
Contributor Author

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

@rvmiller89
Copy link
Contributor

What does the helm install command look like to also pass prometheus-overrides.yaml and fluentbit-overrides.yaml ?

frankreno
frankreno previously approved these changes Aug 5, 2019
Copy link
Contributor

@frankreno frankreno left a 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

deploy/helm/sumologic/Chart.yaml Outdated Show resolved Hide resolved
deploy/helm/sumologic/conf/events/events.conf Outdated Show resolved Hide resolved
deploy/helm/sumologic/conf/events/events.conf Outdated Show resolved Hide resolved
{{/*
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".
Copy link
Contributor

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?

deploy/helm/sumologic/templates/_helpers.tpl Outdated Show resolved Hide resolved
image:
repository: sumologic/kubernetes-fluentd
tag: 0.0.0
pullPolicy: Always
Copy link
Contributor

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.

@maimaisie
Copy link
Contributor Author

What does the helm install command look like to also pass prometheus-overrides.yaml and fluentbit-overrides.yaml ?

@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

samjsong
samjsong previously approved these changes Aug 6, 2019
@maimaisie maimaisie merged commit 4de4b66 into master Aug 7, 2019
@maimaisie maimaisie deleted the maisie-helm-chart branch August 7, 2019 18:26
flushInterval: 5

## Increase number of http threads to Sumo. May be required in heavy logging clusters
numThreads: 1
Copy link
Contributor

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?

psaia pushed a commit to psaia/sumologic-kubernetes-collection that referenced this pull request May 25, 2021
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.

6 participants