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.

Sign up for GitHub

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

Rewording Cluster Autoscaling paragraph in the last blog #73

Merged
merged 2 commits into from
Dec 3, 2024
Merged

Rewording Cluster Autoscaling paragraph in the last blog #73

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
00ec907
Update 2024-11-26-in-kubernetes-we-trust.adoc
ibuziuk Dec 2, 2024
a2aab2e
Update _posts/2024-11-26-in-kubernetes-we-trust.adoc
ibuziuk Dec 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions _posts/2024-11-26-in-kubernetes-we-trust.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,9 +71,9 @@ attributes:
controller.devfile.io/storage-type: ephemeral
....

=== Autoscaling
=== Cluster Autoscaling

Although autoscaling is a powerful Kubernetes feature, you cannot always fall back on it, and should always consider predictive scaling by analyzing the load data on your environment to detect daily or weekly usage patterns. If your workloads follow some pattern, e.g. there are huge spikes based on the time of the day, you should consider provisioning worker nodes in advance (e.g. a lot of users turn on their smart speakers in the morning between 7 - 9 am, and there is a huge spike in the requests that on the infrastructure level is predicted and handled in advance).
Although link:https://kubernetes.io/docs/concepts/cluster-administration/cluster-autoscaling/[Cluster Autoscaling] is a powerful Kubernetes feature, you cannot always fall back on it and should always consider predictive scaling by analyzing load data on your environment to detect daily or weekly usage patterns. If your workloads follow a pattern and there are dramatic peaks throughout the day you should consider provisioning worker nodes accordingly (e.g. a lot of users turn on their smart speakers in the morning between 7 - 9 a.m. causing a huge spike in requests that can be predicted and handled in advance on the infrastructure level).

=== CPU Limits

Expand Down
Loading