Stateful best practices #16
Open
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
|
This addresses this section of the TODO. I will have a closer look at it soon. |
|
Also, a single geographical region (this also applies to cluster nodes). |
dantwining
reviewed
Apr 15, 2021
|
|
||
| In particular, you should consider using: | ||
|
|
||
| - the [Service Catalog](https://kubernetes.io/docs/concepts/extend-kubernetes/service-catalog/), if you're cluster is deployed in the cloud or has access to a Service that exposes the Open Service Broker API. |
There was a problem hiding this comment.
Suggested change
| - the [Service Catalog](https://kubernetes.io/docs/concepts/extend-kubernetes/service-catalog/), if you're cluster is deployed in the cloud or has access to a Service that exposes the Open Service Broker API. | |
| - the [Service Catalog](https://kubernetes.io/docs/concepts/extend-kubernetes/service-catalog/), if your cluster is deployed in the cloud or has access to a Service that exposes the Open Service Broker API. |
|
|
||
| You should always have: | ||
|
|
||
| - a StroageClass named `default` defined in your cluster and |
There was a problem hiding this comment.
Suggested change
| - a StroageClass named `default` defined in your cluster and | |
| - a StorageClass named `default` defined in your cluster and |
|
|
||
| The admission controller adds the _defalt_ StorageClass if the PersistentVolumeClaim doesn't have one. | ||
|
|
||
| You can continue reading about the [default behaviour in StorageClasses on the official documentation](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/#defaulting-behavior). |
There was a problem hiding this comment.
Suggested change
| You can continue reading about the [default behaviour in StorageClasses on the official documentation](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/#defaulting-behavior). | |
| You can continue reading about the [default behaviour in StorageClasses in the official documentation](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/#defaulting-behavior). |
|
|
||
| Pods share resources such as CPU and memory with other Pods on the same Node. | ||
|
|
||
| If a Pods is using more resources than requested (but still less than the limits), it might end up committing for resources. |
There was a problem hiding this comment.
Suggested change
| If a Pods is using more resources than requested (but still less than the limits), it might end up committing for resources. | |
| If a Pod is using more resources than requested (but still less than the limits), it might end up committing for resources. |
|
|
||
| If a Pods is using more resources than requested (but still less than the limits), it might end up committing for resources. | ||
|
|
||
| The challenge is more problematic when Pods compete for disk I/O, particularly in Pods that uses storage. |
There was a problem hiding this comment.
Suggested change
| The challenge is more problematic when Pods compete for disk I/O, particularly in Pods that uses storage. | |
| The challenge is more problematic when Pods compete for disk I/O, particularly in Pods that use storage. |
|
https://dbexamstudy.blogspot.com/2021/11/is-kubernetes-slowing-down-my-database.html |
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.
I guess this could a section on his own.