kubernetes/minikube

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

Open

#19,285 创建于 2024年7月17日

在 GitHub 查看
 (3 评论) (0 反应) (1 负责人)Go (31,799 star) (5,222 fork)batch import
area/networkinghelp wantedpriority/important-soon

描述

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

贡献者指南

技术栈
go
领域
cliinfrastructure
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
blocked
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Basic knowledge of GoUnderstanding of minikube addonsFamiliarity with Calico CNI
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
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.