6ea0c838ec
|
||
|---|---|---|
| .vscode | ||
| agent-custom | ||
| agentpods | ||
| cmd/manager | ||
| helm | ||
| pkg | ||
| version | ||
| .gitignore | ||
| Dockerfile | ||
| README.md | ||
| Security.md | ||
| azure-pipelines-L2Testcase.yml | ||
| azure-pipelines-buildctl.yml | ||
| azure-pipelines.yml | ||
| consistent-hash.go | ||
| consistent_hash_test.go | ||
| constants.go | ||
| contracts.go | ||
| crd_controller_test.go | ||
| go.mod | ||
| go.sum | ||
| hmac.go | ||
| hmac_test.go | ||
| http_handler_test.go | ||
| kubernetes-auth.go | ||
| kubernetes.go | ||
| kubernetes_test.go | ||
| main.go | ||
README.md
k8s-poolprovider
helm install k8s-poolprovider --name=myhelmchart --set "vsts.VSTS_SECRET=shared secret"
For local testing
Use the kubernetes.yaml and buildkit.yaml under Manifests folder to set up the application on your cluster. This works if you want to test the containerised application on a kubernetes cluster.
When using VS Code, the launch.json has been appropriately modified for local debugging. If debugging locally,
- Make sure you can run kubectl commands from your machine, and a kubeconfig file is present on your machine.
- Create a new namespace 'azuredevops' on your cluster.
- Create an opaque secret in the azuredevops namespace with the required secrets set.
kubectl create secret generic vsts --from-literal=VSTS_SECRET=sharedSecret -n azuredevops - Voila! You can start debugging directly from VS code. When the deployment happens, hit localhost:8082 with the correct APIs and see the app in action.