kubernetes/minikube

minikube-ingress-dns addons using two different images?

Open

#20629 opened on Apr 15, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (31,799 stars) (5,222 forks)batch import
help wantedpriority/important-longterm

Description

in the code I see

		"IngressDNS": "k8s-minikube/minikube-ingress-dns:0.0.3@sha256:4211a1de532376c881851542238121b26792225faa36a7b02dccad88fd05797c",
	}, map[string]string{
		"IngressDNS": "gcr.io",
	}),

also I see

				"IngressDNS": "cryptexlabs/minikube-ingress-dns:0.3.0@sha256:e252d2a4c704027342b303cc563e95d2e71d2a0f1404f55d676390e28d5093ab",
		}

I suspect maybe the cryptexlabs/minikube-ingress-dns is the one that neeeds to go

I beleive @sharifelgamal had a fork of this, do you remember that ?

Contributor guide

Tech stack
godockerkubernetes
Domain
infrastructurebackend
Issue type
bug
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
familiarity with minikube addonsbasic Go knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the addon configuration file (likely in pkg/addons/config.go or similar) to understand how the image references are defined. Check the comments on the issue to see if maintainers have clarified which image is correct. Look at the linked code snippets to determine if there is a conflict between the two image references. The goal is to propose a fix that consolidates to one correct image reference.