kubernetes-sigs/cluster-api

Stop/Start Cluster?

Open

#9,476 opened on Sep 21, 2023

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Go (1,532 forks)auto 404
help wantedkind/featurepriority/backlogtriage/accepted

Repository metrics

Stars
 (4,267 stars)
PR merge metrics
 (PR metrics pending)

Description

What would you like to be added (User Story)?

As a user, I want to stop cluster to release the resource for saving costs, and later, i want to have the ability to start the cluster and resume the existing workload.

Detailed Description

For cloud based k8s offer like AKS, EKS. They allow either stop or scale down to 0 instance for reducing costs. But if we manage cluster through capi, there isn't a method to totally release all resources including cp.

So, is it possible to implement such feature in CAPI?

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

Contributor guide

Research direction
Investigate how CAPI currently handles cluster lifecycle, particularly the pause/unpause and scale to zero patterns in cloud providers like AKS and EKS. Look at existing issues and proposals for stop/start functionality.
Tech stack
go
Domain
infrastructurecloud
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.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30