question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

feature request: Standard way for microk8s to communicate about a local registry

See original GitHub issue

Many Kubernetes clusters support a local registry, to make pushing images directly to the cluster fast. But every cluster documents it with manual shell scripts:

Because every cluster is slightly different, this makes it hard for tools to automate this work for users.

The big idea

Clusters should use annotations on the kube-system namespace to document how to configure a registry

Detailed design

I propose 3 new “standard” annotations:

x-k8s.io/registry: the host of the registry (hostname and port), as seen from outside of the cluster x-k8s.io/registry-from-cluster: the host of the registry (hostname and port), as seen from inside the cluster x-k8s.io/registry-help: The URL of documentation where users can read more about how to set a registry up.

Tools that would benefit from local registries should read this annotation and display it to the user

What this means for microk8s

All microk8s clusters would have a registry-help annotation pointing users to https://microk8s.io/docs/registry-built-in

When you run microk8s enable registry, microk8s would automatically add the x-k8s.io/registry annotation to nodes in the cluster.

Prior Art

This proposal is based on what we’ve been recommending to people in Tilt, with a lot of success: https://docs.tilt.dev/choosing_clusters.html#custom-clusters

update 5/4 - changed the proposal to use the kube-system namespace instead of node annotations

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
ktsakalozoscommented, May 21, 2020

Looks good @nicks. You have my +1 on the PR.

0reactions
nickscommented, Jun 11, 2020

The KEP has been marked implementable! I suspect it will be straightforward to implement, and I think I understand the microk8s internals well enough to send a PR if that would help, but it might take me a little while to get to it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Standard way for microk8s to communicate about a ... - GitHub
Many Kubernetes clusters support a local registry, to make pushing images directly to the cluster fast. But every cluster documents it with ...
Read more >
How to use the built-in registry - MicroK8s
The registry shipped with MicroK8s is hosted within the Kubernetes cluster and is exposed as a NodePort service on port 32000 of the...
Read more >
How to use a local registry - MicroK8s
The following documentation explains how to use MicroK8s with local images, or images fetched from public or private registries. A familiarity with building, ......
Read more >
How to work with a private registry - MicroK8s
In the official Kubernetes documentation a method is described for creating a secret from the Docker login credentials and using this to access...
Read more >
Get started - MicroK8s
Install MicroK8s. MicroK8s will install a minimal, lightweight Kubernetes you can run and use on practically any machine. · Join the group ·...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found