Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

optionally skip post Setup operator environment #20

Open
ca-scribner opened this issue Sep 3, 2021 · 1 comment
Open

optionally skip post Setup operator environment #20

ca-scribner opened this issue Sep 3, 2021 · 1 comment

Comments

@ca-scribner
Copy link
Contributor

ca-scribner commented Sep 3, 2021 •
edited
Loading

The post Setup operator environment cleanup happens after all meaningful work is complete and immediately before stopping the workflow. Is cleanup necessary? At least in some cases, like when creating a ephemeral microk8s cluster for testing, couldn't we skip this step and leave microk8s running on the runner (for github to trash themselves)?

There might be cases where cleanup is important (if we bootstrap on an existing cloud?), but for microk8s I think it is unnecessary. It also takes maybe 2 minutes per run, which is a good portion of many integration tests.
@carlcsaposs-canonical
Copy link
Contributor

+1 for LXD

Fixed by a32a699 for microk8s

Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ca-scribner @carlcsaposs-canonical