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

Generate setup job yaml from helm template #280

Merged
merged 4 commits into from
Nov 7, 2019

Conversation

rvmiller89
Copy link
Contributor

@rvmiller89 rvmiller89 commented Nov 6, 2019

Description

Updates the CI build.sh script to generate a new template yaml file setup-sumologic.yaml.tmpl that contains all of the setup Helm templates needed to run a job on Kubernetes to setup the Sumo Logic collector and HTTP sources, namespace and secret.

In order to use the job yaml, you must first create the sumologic namespace:

kubectl create namespace sumologic

And then update these parameters in the yaml template:

  1. $NAMESPACE
  2. $SUMOLOGIC_ACCESSID
  3. $SUMOLOGIC_ACCESSKEY
  4. $COLLECTOR_NAME
  5. $CLUSTER_NAME

This can be added to our README in a future PR. One thing I did notice is it leaves the setup pod as 0/1 Completed but I think that's okay to leave:

k8s $ k get pods
NAME                               READY   STATUS      RESTARTS   AGE
collection-sumologic-setup-bj65t   0/1     Completed   0          40m
Testing performed
  • ci/build.sh
  • Redeploy fluentd and fluentd-events pods
  • Confirm events, logs, and metrics are coming in

Copy link
Contributor

@maimaisie maimaisie left a comment

Choose a reason for hiding this comment

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

LGTM

@rvmiller89 rvmiller89 merged commit b0aaea2 into master Nov 7, 2019
@rvmiller89 rvmiller89 deleted the rmiller-generate-non-helm-terraform branch November 7, 2019 22:32
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.

4 participants