-
Notifications
You must be signed in to change notification settings - Fork 9
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.
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
Add support for canonical k8s #357
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Phan Trung Thanh <[email protected]>
Signed-off-by: Phan Trung Thanh <[email protected]>
Signed-off-by: Phan Trung Thanh <[email protected]>
Signed-off-by: Phan Trung Thanh <[email protected]>
Signed-off-by: Phan Trung Thanh <[email protected]>
Signed-off-by: Phan Trung Thanh <[email protected]>
Signed-off-by: Phan Trung Thanh <[email protected]>
Signed-off-by: Phan Trung Thanh <[email protected]>
Signed-off-by: Phan Trung Thanh <[email protected]>
Signed-off-by: Phan Trung Thanh <[email protected]>
Signed-off-by: Phan Trung Thanh <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like some tests are filing. Can you double check?
if: ${{ inputs.use-canonical-k8s }} == true | ||
id: canonical-k8s | ||
run: | | ||
sudo snap install k8s --channel=1.30-classic/beta --classic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can reuse the channel
input here currently used for microk8s to be able to customise the snap channel
This PR adds an input
use-canonical-k8s
to theintegration-test
workflow to allow deploying juju applications on canonical-k8s.For now, this parameter must be used in conjuction with
provider: k8s
so thataction-operator
bootstraps canonical-k8s as a generic cluster when creating the juju controller.action-operator
will add support for canonical-k8s in the future. Until then, this will be used as a workaround since it's needed to test workflows running on canonical-k8s.Checklist
urgent
,trivial
,complex
)