Page History

...

1. Create a service account. a role binding, and a service account token secret. See BuildSystem/artifact_storage/api/artifact_service_account.yaml at main · ad-build-test/BuildSystem (github.com)
2. Apply this manifest with

   1. kubectl apply -f artifact_service_account.yaml 

3. Then look at the secret

   1. kubectl describe -n artifact secret/myexample-sa-token

4. Add that to environment variable passed in to artifact_api_deployment.yaml BuildSystem/artifact_storage/api/artifact_api_deployment.yaml at main · ad-build-test/BuildSystem (github.com)
5. Apply this manifest with

   1. kubectl apply -f artifact_api_deployment.yaml

   2. What this does is starts the api deployment, it'll start the script to add in the kube config at $HOME/.kube/config, then start the api process
6. done TODO: Create the script that initializes the kube configuration, then start the api process (probably bash)

How to test service is accessible to other build containers

1. TODO: Apparently the artifact needs to be in the same namespace as the build containers if they want to access it, so in that case, may just put the build containers in the artifact namespace?