Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document the use of the cluster chart #3195

Closed
2 tasks done
Tracked by #2739
Rotfuks opened this issue Jan 30, 2024 · 0 comments · Fixed by giantswarm/cluster#103
Closed
2 tasks done
Tracked by #2739

Document the use of the cluster chart #3195

Rotfuks opened this issue Jan 30, 2024 · 0 comments · Fixed by giantswarm/cluster#103
Assignees
Labels
area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service team/turtles Team Turtles

Comments

@Rotfuks
Copy link
Contributor

Rotfuks commented Jan 30, 2024

Motivation

Now that we introduced the cluster chart and already use it in capa we need to make sure that there is documentation out there explaining how to use the cluster chart and what to take into account when working with the cluster and cluster-aws charts.

Tasks

Preview Give feedback

Outcome

  • we have sufficient documentation explaining the use of the cluster chart and it's context within the cluster- charts to internal engineers to ensure operational excellence.
@Rotfuks Rotfuks added this to Roadmap Jan 30, 2024
@Rotfuks Rotfuks converted this from a draft issue Jan 30, 2024
@Rotfuks Rotfuks added area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service team/turtles Team Turtles labels Jan 30, 2024
@Rotfuks Rotfuks moved this from Inbox 📥 to Up Next ➡️ in Roadmap Jan 31, 2024
@github-project-automation github-project-automation bot moved this from Up Next ➡️ to Done ✅ in Roadmap Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service team/turtles Team Turtles
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants