ci: smoke test against k8s as well as microk8s #1600
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hmm, oddly, this is failing, but the concierge tests themselves do a prepare in a GitHub runner with this preset, so I'm not sure why it isn't working for us. Moving to draft until I figure that out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Concierge
devpreset uses K8s rather than Microk8s, and in general we're moving towards K8s over Microk8s, so it's probably best to test against it.It seems extraordinarily unlikely that anything in ops would work on K8s and not on Microk8s or vice-versa, so we could instead swap from
microk8stok8s. Given that we're in a transition period at the moment, and these tests only run monthly, it seems reasonable to have both for now.