Skip to content

Makes juju and microk8s classic confinement optional - #57

Open
mz2 wants to merge 1 commit into
charmed-kubernetes:mainfrom
mz2:confinement-inputs
Open

Makes juju and microk8s classic confinement optional#57
mz2 wants to merge 1 commit into
charmed-kubernetes:mainfrom
mz2:confinement-inputs

Conversation

@mz2

@mz2 mz2 commented Jun 7, 2023

Copy link
Copy Markdown

Adds inputs juju-classic-confinement and microk8s-classic-confinement (on by default, i.e. not a breaking change) to allow optionally for using the strictly confined versions of juju and microk8s.

@addyess addyess left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is fine... my understanding was that you could install a strictly confined snap with the --classic flag -- and that it would just be ignored.

But sure this is fine.

IronCore864 added a commit to canonical/operator that referenced this pull request Mar 24, 2025
This PR adds a channel for microk8s for the test explanation doc in the
CI section.

More information: when using the [charmed-kubernetes/actions-operator
action](https://github.com/charmed-kubernetes/actions-operator) to setup
an environment for integration test, with Juju 3.3+, microk8s needs a
strict channel version. Without this setting, there will be an error
like `juju "3.x.x" can only work with strictly confined microk8s`. See
an [existing issue
here](charmed-kubernetes/actions-operator#70)
and [an unmerged PR
here](charmed-kubernetes/actions-operator#57).

Related: canonical/juju-sdk-tutorial-k8s#72.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants