Skip to content

test: Scrub GKE cluster more thoroughly when releasing cluster.#12192

Merged
nebril merged 1 commit intomasterfrom
pr/jrajahalme/ci-scrub-gke
Jun 19, 2020
Merged

test: Scrub GKE cluster more thoroughly when releasing cluster.#12192
nebril merged 1 commit intomasterfrom
pr/jrajahalme/ci-scrub-gke

Conversation

@jrajahalme
Copy link
Copy Markdown
Member

@jrajahalme jrajahalme commented Jun 18, 2020

Noticed in local testing that an Istio sidecar-injector label can
prevent PODs being deployed in the default namespace if left behind by
a failed Istio test, so deleted this label in the clean-up.

Delete also all other resources left into the default namespace.

Delete cilium-monitoring and cilium namespaces to leave the cluster in
a more predictable condition and remove all CRDs from the cluster.

Move the cleaning to the renamed gke/clean-cluster.sh so that it can be reused from the command line in local testing.

These changes allowed the cilium-ci-12 cluster to successfully pass all the K8s tests, while before it would not pass anything.

Fixes: #11928
Signed-off-by: Jarno Rajahalme jarno@covalent.io

@jrajahalme jrajahalme added kind/bug/CI This is a bug in the testing code. area/CI-improvement Topic or proposal to improve the Continuous Integration workflow release-note/misc This PR makes changes that have no direct user impact. needs-backport/1.8 labels Jun 18, 2020
@jrajahalme jrajahalme requested review from a team as code owners June 18, 2020 22:51
@jrajahalme jrajahalme marked this pull request as draft June 18, 2020 22:51
@coveralls
Copy link
Copy Markdown

coveralls commented Jun 18, 2020

Coverage Status

Coverage increased (+0.004%) to 37.11% when pulling 00d964d on pr/jrajahalme/ci-scrub-gke into 33da7a8 on master.

@jrajahalme
Copy link
Copy Markdown
Member Author

test-gke

@jrajahalme jrajahalme force-pushed the pr/jrajahalme/ci-scrub-gke branch from ba0d813 to 8fbda12 Compare June 19, 2020 00:00
@jrajahalme
Copy link
Copy Markdown
Member Author

test-gke

Noticed in local testing that an Istio sidecar-injector label can
prevent PODs being deployed in the default namespace if left behind by
a failed Istio test.

Delete also all other resources left into the default namespace.

Delete cilium-monitoring and cilium namespaces to leave the cluster in
a more predictable condition.

Finally, delete all CRDs.

Move the cleaning to the renamed `gke/clean-cluster.sh` so that it can
be reused from the command line in local testing.

Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
@jrajahalme jrajahalme force-pushed the pr/jrajahalme/ci-scrub-gke branch from 8fbda12 to 00d964d Compare June 19, 2020 03:09
@jrajahalme
Copy link
Copy Markdown
Member Author

test-gke

@jrajahalme jrajahalme marked this pull request as ready for review June 19, 2020 06:18
@jrajahalme
Copy link
Copy Markdown
Member Author

Note to reviewers and committers: This PR only touches scripts used by CI on GKE, so there is no need to run any other than the GKE CI pipeline.

@nebril nebril merged commit 62e4558 into master Jun 19, 2020
@nebril nebril deleted the pr/jrajahalme/ci-scrub-gke branch June 19, 2020 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/CI-improvement Topic or proposal to improve the Continuous Integration workflow kind/bug/CI This is a bug in the testing code. release-note/misc This PR makes changes that have no direct user impact.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI: test-gke pipeline broken

5 participants