Releases: balchua/microk8s-actions
Release v0.4.3
Increase the hostpath provisioner timeout to 15m
This is a minor release. It simply updates the hostpath-provisioner
rollout timeout to 15m
instead of the previous 120s
. Some runners maybe a little slow in responding, hence the increased timeout.
If the rollout finishes early, then it will return immediately.
Hopefully this addresses #20
Release v0.4.1
This release increases the timeout when enabling the hostpath storage and the persistent volume to about 120s
.
Fixes #20
Release v0.4.0
Support new MicroK8s launch configuration and image side loading.
v0.3.2
What's Changed
- Fix/push local registry by @balchua in #15
Full Changelog: v0.3.1...v0.3.2
Fixes the following:
- Wait for hostpath provisioner to be ready before proceeding
- Wait for the persistent volume
registry-claim
to beBound
before proceeding.
This allows CI builds to push their images to the local registry instead of remote registries.
Upgrade node v12 to v16
Thanks to @barrettj12 for upgrading node version to v16
What's Changed
- update to Node 16 by @barrettj12 in #12
New Contributors
- @barrettj12 made their first contribution in #12
Full Changelog: v0.3.0...v0.3.1
Release v0.3.0
This version now supports MicroK8s on strict confinement.
Options removed, since the addition of the addons
attribute, one can specify multiple addons to enable:
rbac
dns
storage
kubeflow
addon is also no longer supported by MicroK8s.
New option:
devMode
- to enable strict confinement ondevmode
. This is to facilitate allowing some workloads to run on strict confinement.
Release v0.2.2
Release v0.2.1
Improvements
You can now use all available addons in MicroK8s.
As an example, users can now define all addons to enable with one argument.
- uses: balchua/microk8s-actions@v0.2.0
with:
channel: '1.19/stable'
addons: '["rbac", "dns", "storage", "registry", "metrics-server"]'
This release also waits for the kube-apiserver to stabilize before handing the cluster to the user.
Release v0.1.3
fix shell check.