gitchegumi/homelab
gitchegumi/homelab
Watch
1
0
Fork
You've already forked homelab
 0
Code Issues 1 Pull requests Projects 1 Wiki Activity Actions

Bootstrap the NucBox RKE2 server and enforce control-plane-only scheduling #1

New issue
Closed
opened 2026-08-29 00:22:48 -05:00 by portegumi · 1 comment
portegumi commented 2026-08-29 00:22:48 -05:00
Collaborator
Copy link

Description

Establish the NucBox G5 as the first RKE2 server, control-plane, and etcd node. Keeping ordinary workloads off this resource-constrained node protects cluster control-plane stability.

Scope

  • Record the selected RKE2 version and base configuration.
  • Install and configure the NucBox as an RKE2 server.
  • Apply and document a control-plane taint that excludes normal application workloads.
  • Establish a safe operator access method without committing kubeconfig or node-token material.

Acceptance criteria

  • The NucBox reports a healthy RKE2 server, control-plane, and etcd role.
  • Normal application pods cannot schedule on the NucBox without an explicit toleration.
  • Core cluster components required on the server remain healthy.
  • Version and non-secret configuration decisions are documented in the repository.
  • No node token, kubeconfig, private key, or other credential is committed.

Dependencies / blockers

None. This is the initial cluster bootstrap milestone.

## Description Establish the NucBox G5 as the first RKE2 server, control-plane, and etcd node. Keeping ordinary workloads off this resource-constrained node protects cluster control-plane stability. ## Scope - Record the selected RKE2 version and base configuration. - Install and configure the NucBox as an RKE2 server. - Apply and document a control-plane taint that excludes normal application workloads. - Establish a safe operator access method without committing kubeconfig or node-token material. ## Acceptance criteria - [x] The NucBox reports a healthy RKE2 server, control-plane, and etcd role. - [x] Normal application pods cannot schedule on the NucBox without an explicit toleration. - [x] Core cluster components required on the server remain healthy. - [x] Version and non-secret configuration decisions are documented in the repository. - [x] No node token, kubeconfig, private key, or other credential is committed. ## Dependencies / blockers None. This is the initial cluster bootstrap milestone.
gitchegumi commented 2026-08-29 00:44:16 -05:00
Owner
Copy link

Closing as complete

Closing as complete
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
app-migration
Migration of existing applications into Kubernetes

  
ci-cd
Forgejo Actions, runners, GitOps, and delivery automation

  
cluster
RKE2 cluster bootstrap and node lifecycle

  
Discussion
Use this label when the issue is meant to be a discussion. These items will not be actioned on, but may lead to new issues with action items.

  
documentation
Architecture, inventory, conventions, and runbooks

  
gpu
NVIDIA enablement and GPU workload scheduling

  
networking
Cluster networking, load balancing, addressing, and DNS

  
security
Security controls and secret-handling safeguards

  
storage
TrueNAS, CSI, NFS, iSCSI, and local persistent storage

  
uds
Defense Unicorns UDS prerequisites and deployment

No labels
app-migration
ci-cd
cluster
Discussion
documentation
gpu
networking
security
storage
uds
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Homelab k8s Setup
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gitchegumi/homelab#1
No description provided.