Enabling multiple addons on MicroK8s in one invocation may lead to unreachable API server

[worldofgeese]

Bug

Current Behavior

When running microk8s enable addons dns storage registry ingress, a WARNING is printed:

            "WARNING: Do not enable or disable multiple addons in one command.\n"
            "         This form of chained operations on addons will be DEPRECATED in the future.\n"
            f"         Please, {action} one addon at a time: 'microk8s {action} <addon>'"

The responsible line of code is linked here.

Expected behavior

Garden should enable addons single invocation by single invocation.

Impacted code in our CircleCI config.yml and our config.ts.

Reproducible example

Use https://github.com/garden-io/quickstart-example

Workaround

Manually enable addons as user before running first garden deploy.

Additional context

Following garden deploy auto-enabling all addons on Windows 21H2, the MicroK8s API server became unreachable, requiring a complete VM delete and re-creation. I manually enabled the required addons one-by-one before running garden deploy again, at which point MicroK8s was accessible.

garden-microk8s-error-log.log

Your environment

• OS: Windows Enterprise LTSC 21H2
• How I'm running Kubernetes: MicroK8s

garden version 0.13.8

[vvagaytsev]

@worldofgeese, thanks for reporting this! It should be an easy-to-fix issue. I'm taking a look now.

By the way, the link to the config.ts points to the minikube-specific piece of code, not to the microk8s. So I think we should fix the function configureMicrok8sAddons.

Should we use sequential addon installation for minikube as well?

[worldofgeese]

By the way, the link to the config.ts points to the minikube-specific piece of code, not to the microk8s. So I think we should fix the function configureMicrok8sAddons.

Should we use sequential addon installation for minikube as well?

No, you're right, minikube doesn't suffer from this issue. I agree with you that it's the function configureMicrok8sAddons that needs love ❤️

[vvagaytsev]

Thanks @worldofgeese! Could you try this build, please?

[vvagaytsev]

@worldofgeese the fix has been released in 0.13.9, please try it out.