Kubernetes configuration

Running boutique

Boutique is run using helm, in the root repository simply run helm install btq ./helm-chart However don't do that because first of all it's already running and second it needs some values for building the dockefiles. Helm uses values added to helm-chart/values.yaml file.

Variables in values.yaml

However the default values are empty and the dockerfiles need them. to give them values just simply add --set flag. For example to add a buildname you write helm upgrade btq ./helm-chart/ --set SealightsEnvVars.build_name="some_build_name"

Also because the boutique is already running you should run helm upgrade btq ./helm-chart --install

Here's the full command (replace environment variables with real values):

helm upgrade btq $HELM_PATH/helm-chart/ --set SealightsEnvVars.token=$TOKEN --set SealightsEnvVars.lab_id=$LABID --set SealightsEnvVars.build_name=$BUILDNAME --set SealightsEnvVars.sl_branch=$SL_BRANCH --set SealightsEnvVars.java_agent_url=https://storage.googleapis.com/cloud-profiler/java/latest/profiler_java_agent_alpine.tar.gz --set SealightsEnvVars.dotnet_agent_url=https://agents.sealights.co/dotnetcore/latest/sealights-dotnet-agent-alpine-self-contained.tar.gz --set images.tag=$TAG --install
  • $TOKEN: Sealights token from website.

  • $LABID: Is a sealights lab id.

  • $BUILDNAME: Is a buildname for Sealights (You can write any string but it should be a different one each time).

  • $SL_BRANCH: Is the branch of the build (Doesn't really have to be a real branch).

  • $TAG: Is the tag that the Kubernetes will use to pull specific image/s from ecr, for example setting it to sealights-1.0.5 in email service {{ .Values.images.repository }}/btq-{{ .Values.emailService.name }}:{{ .Values.images.tag | default .Chart.AppVersion }} it will pull 534369319675.dkr.ecr.us-west-2.amazonaws.com/btq-emailservice:sealights-1.0.5.

To access the boutique cluster you have to ssh to the ec2 (DNS and key are provided), then write export KUBECONFIG=$(k3d kubeconfig write btq). then any kubectl operation like kubectl get pods will be on the boutique.

Last updated