Do kubeadm init from cloud-init

未关闭
#7 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
44/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
go, kubernetes

调研方向

The issue describes moving kubeadm configuration and setup logic into cloud-init, including a systemd unit; it does not name specific files or tests. Start by locating the provisioning and cloud-init setup, then trace the existing SSH-driven kubeadm and Calico sequence. Done means provisioning runs that setup through cloud-init and waits for the unit after SSH; the optional SSH-free notification idea is a separate follow-up.

由索引模型根据 Issue 内容生成。

描述

Right now, we wait for SSH before we do anything, including copying the kubeadm config, then init, then Calico, etc...

But it would be cleaner to just shove all of that setup in the cloud-init config itself. It would write the kubeadm config, and then the systemd unit which runs all the logic. That should make provisioning a bit faster. Once we get SSH, we can just wait until the systemd unit is active. (Though it'd be nice to actually avoid blocking on SSH entirely for bringup and instead get notified via e.g. virtio-serial or systemd's AF_VSOCK-powered integration.)

主要语言
Go
星标
18
派生
10
平均合并
1 天 2 小时
30 天内合并 PR
7

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

bootc-dev/bink 的其他 Issue

查看 bootc-dev/bink 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。