kubernetes/minikube

How to provide an image pull secret when using "--image-repository" with an internal registry that does not allow anonymous pull requests?

Open

#10,019 opened on Dec 21, 2020

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Go (5,222 forks)batch import
area/registryhelp wantedkind/featurelifecycle/frozenpriority/backlog

Repository metrics

Stars
 (31,799 stars)
PR merge metrics
 (Avg merge 12d 19h) (43 merged PRs in 30d)

Description

After a bit of a hiatus, I have been revisiting the whole topic of running minikube from purely local sources (i.e., any images should come from our own private registry). I revisted the issue https://github.com/kubernetes/minikube/issues/8298 that I created in June. The first problem I am running into is that our internal registry does not support anonymous pull access. In the above mentioned issue, @tstromberg mentioned two sources on how to provide a pull secret - but all of the already require a running cluster, as they both boil down to enabling the registry-creds plugin:

minikube addons configure registry-creds

But at that point all the infrastructure images would already have to be there, no? Further, this add-on only allows me to specify creds for ECR, GCR, Dockerhub or ACR - what about my own registry?

Contributor guide

Research direction
Investigate how to configure minikube to use a private registry with image pull secrets during cluster start (e.g., via image repository and insecure registry flags, or by pre creating a secret and passing it via extra config or a startup script). Check if the registry creds addon can be extended or if there is a way to specify custom registries. Look at minikube's source code for handling image pull secrets and test a solution.
Tech stack
go
Domain
infrastructuredevopscloud
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesDockerminikube
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60