fix: Update shoot cluster creation How-To in light of k8s update #268
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I am marking this as a draft, for one last screenshot update is still pending. Currently, the venerable "Internal server error" disallows me to actually instantiate a cluster and get a screenshot of a shoot with Kubernetes 1.27 being created. |
We explicitly reference Kubernetes 1.27. While at it, we re-create all screenshots and modify the prose due to minor UI changes.
colder-is-better
force-pushed
the
create-shoot-up
branch
from
786721d to
a458594
Compare
fghaas
approved these changes
Jan 9, 2024
| @@ -4,51 +4,60 @@ description: How to spin up a Kubernetes cluster with Gardener | |||
| # Creating a Kubernetes cluster | |||
|
|
|||
| If you want to create a Kubernetes cluster, you can do so via the {{gui}} using {{k8s_management_service}}. | |||
| This guide shows you how to do that, and how to deploy a sample application on such a cluster. | |||
| This guide shows you how to do that. | |||
| To get started, navigate to <https://{{gui_domain}}> and, in the side panel, choose *Containers → [{{k8s_management_service}}](https://{{gui_domain}}/containers/gardener)*. | ||
| You will land on a page named *{{k8s_management_service}} / Shoot Clusters*. | ||
| There, you can create and manage your {{k8s_management_service}}-based clusters. | ||
| In {{k8s_management_service}} terminology, a Kubernetes cluster is referred as a **Shoot** (as in, [new plant growth](https://en.wikipedia.org/wiki/Shoot)). |
There was a problem hiding this comment.
Helpful clarification with the link there. :)
|
|
||
|  | ||
|
|
||
| ### A note on quotas | ||
|
|
||
| Your {{k8s_management_service}} worker nodes are subject to [quotas](../../../reference/quotas/openstack.md) applicable to your {{brand}} project. | ||
| You should make sure that considering your selection of worker node [*flavor*](../../../reference/flavors/index.md) (which determines the number of virtual cores and virtual RAM allocated to each node), the _volume size_, and the _Autoscaler Max_ value, you are not at risk of violating any quota. | ||
| It would be best if you kept that in mind when selecting the worker node [*flavor*](../../../reference/flavors/index.md), setting the _volume size_ value, and also the _Autoscaler Max_ value, so you will not be at risk of violating any quota. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We explicitly reference Kubernetes 1.27. While at it, we re-create all screenshots and modify the prose due to minor UI changes.