kubernetes/minikube

Non-interactive minikube addons configure?

Open

#8,283 opened on May 27, 2020

View on GitHub
 (11 comments) (15 reactions) (0 assignees)Go (31,799 stars) (5,222 forks)batch import
help wantedkind/featurelifecycle/frozenpriority/backlog

Description

I'm trying to fully script a minikube start command so I can share it between developers.

I want to use metallb addon introduced recently, which requires LoadBalancer Start and End IPs (I can construct it with output from minikube ip) to be configured via minikube addons configure metallb.

Can this be set non-interactively? By default, it always spawns the input, and you have to input the addresses yourselves.

Contributor guide

Tech stack
go
Domain
cli
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingminikube addon system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the minikube addons configure command implementation, likely in pkg/minikube/addons/ or similar. Check how the metallb addon configuration is handled and find where the interactive input prompts occur. Look for existing flags that could be extended or make the command accept environment variables or command line arguments. The issue asks for a non interactive way to provide the IP range.
Non-interactive minikube addons configure? · kubernetes/minikube#8283 | Good First Issue