Ability to configure microk8s before installation / before anything runs

[jack1902]

Summary

Currently, when installing microk8s across multiple VM' behind a single public egress IP, i encounter numerous issues around rate-limiting. This is solved by configuring microk8s to use a mirror-registry, but the difficulty is in regards to configuration. I cannot configure anything microk8s related before microk8s is installed, and as part of the installation, it starts microk8s which encounters issues due to rate-limiting.

If i was able to do any of the following, i would be much happier:

• configure microk8s prior to installing it (i cannot do this currently, as any paths that exist which are used by the snap instantly bomb out)
• install microk8s without it starting up immediately (this would enable me to edit files after install and before any container images are pulled)

Why is this important?

Automation fails when installing microk8s due to rate-limting, and i have to hope i get enough of an install to enable configuration after the fact. I cannot configure before installing due to the way folders are not allowed to exist before install

Are you interested in contributing to this feature?

[ktsakalozos]

Hi @jack1902,

Could you have a look at the launch configurations: https://microk8s.io/docs/explain-launch-config . They probably do what you are asking for.

[jack1902]

Hi @jack1902,

Could you have a look at the launch configurations: https://microk8s.io/docs/explain-launch-config . They probably do what you are asking for.

Is this possible with a registry that requires Auth? I can see how to configure a mirror registry for "pull", but can't seem to see an example which uses a registry which requires authentication