You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You'll also need to create an SSH secret in your cluster to run [this test pipeline](internal/integration/fixtures/secretref.yaml). This SSH key needs to be associated with your GitHub account to be able to clone this public repo, and must be in a form acceptable to OpenSSH (aka `BEGIN OPENSSH PRIVATE KEY`, not `BEGIN PRIVATE KEY`).
27
87
@@ -34,13 +94,16 @@ The integration tests on the [`kubernetes-agent-stack`](https://buildkite.com/bu
34
94
35
95
36
96
## Cleanup
37
-
These will be deleted automatically for successful tests, but for unsuccessful tests, then will remain after then end of the test job to allow you to debug them.
38
-
However, this means they should be cleaned up manually. To do this run
97
+
98
+
In general, pipelines and queues will be deleted automatically for successful tests, but for unsuccessful tests, then will remain after then end of the test job to allow you to debug them.
99
+
100
+
To do clean them up:
101
+
39
102
```bash
40
-
CLEANUP_PIPELINES=true just cleanup-orphans --org=buildkite-kubernetes-stack --buildkite-token=<buildkite-api-token>
103
+
just cleanup-orphans
41
104
```
42
105
43
-
The token will need to have graphql access as well as:
106
+
The token will need to have GraphQL access as well as:
44
107
-`read_artifacts`
45
108
-`write_pipelines`
46
109
@@ -50,19 +113,17 @@ To clean these out you should run the following in a kubernetes context in the n
50
113
kubectl get -o jsonpath='{.items[*].metadata.name}'jobs| xargs -L1 kubectl delete job
51
114
```
52
115
53
-
At the time of writing, the CI pipeline is run in an EKS cluster, `agent-stack-k8s-ci` in the `buildkite-agent` AWS account.
54
-
The controller is deployed to the `buildkite` namespace in that cluster.
55
-
See https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html for how to obtain a kubeconfig for an EKS cluster.
116
+
## CI ❤️ Integration Test
56
117
57
-
# Run from source
118
+
At the time of writing, the CI pipeline run in an EKS cluster, `agent-stack-k8s-ci` in the `buildkite-agent` AWS account.
119
+
CI deployes the controller onto `buildkite` namespace in that cluster.
58
120
59
-
First store the agent token in a Kubernetes secret:
0 commit comments