close
The Wayback Machine - https://web.archive.org/web/20220308075749/https://github.com/canonical/microk8s/issues/2956
Skip to content
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

Jump to bottom

Potential addons to add to microk8s #2956

Open
Pflegusch opened this issue Mar 2, 2022 · 1 comment
Open

Potential addons to add to microk8s #2956

Pflegusch opened this issue Mar 2, 2022 · 1 comment
Labels
enhancement good first issue help wanted

Comments

@Pflegusch
Copy link

@Pflegusch Pflegusch commented Mar 2, 2022

@ktsakalozos I'm currently using multiple microk8s clusters and found the below tools quite useful and think that they could be a great addition to the list of add-ons.
Brief description of potential add-ons:

  • Loki: Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective and easy to operate. It does not index the contents of the logs, but rather a set of labels for each log stream.
  • Cert Manager: cert-manager is a Kubernetes add-on to automate the management and issuance of TLS certificates from various issuing sources. It will ensure certificates are valid and up to date periodically, and attempt to renew certificates at an appropriate time before expiry.
  • Kubernetes-CSI: This driver allows Kubernetes to access SMB Server on both Linux and Windows nodes.
  • Sealed Secrets: A way of encrypting sensitive secrets and therefore making it possible to save them in repositories etc.

Automatic configuration at installation could be a problem, as one needs to configure some stuff to make the cert-manager or csi driver workable, but I would give it a try and see what I can come up with. Let me know if you are interesting in having any of those :)
@ktsakalozos
Copy link
Member

@ktsakalozos ktsakalozos commented Mar 8, 2022

Hi @Pflegusch, this is a very nice set of addons that I am sure will find good use in several deployments.

With 1.24 release we are preparing a couple of changes on the addons framework to make them configurable and extendable. First you will be able to setup your own repositories with addons and load them on a MIcroK8s deployment. In [1] you will find a template repository that you can clone and later install in MicroK8s with:

microk8s addons repo add myawesomerepo https://github.com/myawesomeorg/myawesomerepo

Have a look at the HACKING.md for instructions on how addons are authored.

By default we will keep shipping the same addons we ship now. These addons will be split to core addons [2] that we (Canonical) will provide support for and community addons [3] that will be maintained by community members.

With v1.24 you will be able to edit the addons in place. All addons will be placed under /var/snap/microk8s/common/addons/ and you will be able to tune them to your liking. In your case this approach will help speedup the development process.

You can see how the above changes are shaping up in you snap install microk8s --classic --channel=latest/edge.

To sum-up your options are to create a public addons repo and/or put PRs for these addons to the community addons repo [3] so they are shipped with MIcroK8s by default.

We appreciate any effort you put into this and we will be here to help out. For realtime comunication you can find us in #microk8s on the kubernetes slack. Thank you.

[1] https://github.com/canonical/microk8s-addons-repo-template
[2] https://github.com/canonical/microk8s-core-addons
[3] https://github.com/canonical/microk8s-addons

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement good first issue help wanted
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@ktsakalozos @Pflegusch