kubernetes/minikube

'--cni calico' should install the Calico API server

Open

#19,285 opened on Jul 17, 2024

View on GitHub
 (3 comments) (0 reactions) (1 assignee)Go (31,799 stars) (5,222 forks)batch import
area/networkinghelp wantedpriority/important-soon

Description

What Happened?

Currently, --cni calico does not install the Calico API server. That server is required for kubectl (and related tools like Helm and kapp) to manage Calico APIs.

Calico provides instructions for doing this manually, but it would be nice if it was automatic.

Attach the log file

N/A

Operating System

Windows

Driver

Docker

Contributor guide

Tech stack
go
Domain
cliinfrastructure
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of GoUnderstanding of minikube addonsFamiliarity with Calico CNI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Examine the Calico addon implementation in the minikube repository, likely in pkg/minikube/assets/addons/calico.go. Determine where the Calico API server deployment is missing. Follow Calico's documentation to add the necessary Kubernetes manifests or use the Calico operator. Check if there are any existing discussions in the issue comments.