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

fix: Kubernetes Best Practices I Wish I Had Known Before #13856

Merged
merged 1 commit into from
Jan 21, 2025
Merged

fix: Kubernetes Best Practices I Wish I Had Known Before #13856

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 1 addition & 3 deletions content/blog/kubernetes-best-practices-i-wish-i-had-known-before/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,7 @@ Security isn’t just a nice-to-have in Kubernetes—it’s critical. If your cl
Monitoring in Kubernetes isn’t optional—it’s mandatory. With containers popping in and out of existence, you need robust observability to see what’s happening behind the scenes.

- [Prometheus + Grafana](https://github.com/prometheus-operator/kube-prometheus): A classic combo for metrics and dashboards.
- ELK / EFK / [Grafana Loki](https://grafana.com/oss/loki/)Stack: Elastic (or OpenSearch) for logs, plus Kibana and Fluentd/Fluent Bit for log collection or Grafana Loki for logs.
- ELK / EFK / [Grafana Loki](https://grafana.com/oss/loki/) Stack: Elastic (or OpenSearch) for logs, plus Kibana and Fluentd/Fluent Bit for log collection or Grafana Loki for logs.
- Jaeger / Zipkin / Tempo: For distributed tracing if you have microservices that call each other.

Set up alerts early. You don’t want your first sign of trouble to be “why is the app so slow?” from an angry user at midnight.
Expand Down Expand Up @@ -233,8 +233,6 @@ Kubernetes is like a Swiss Army knife: powerful, versatile, but also easy to mis

If you’ve already learned some lessons the hard way, you’re not alone. But the beauty of Kubernetes is that with each setback, you gain more experience to fine-tune your approach.

Now it’s your turn. Have a burning Kubernetes best practice you wish you had known earlier? Drop it in the comments or share on Twitter and tag me.

Let’s learn (and unlearn) together, so we can keep taming this Kubernetes beast like the pros we are. Or at least, like the pros we will be!

{{< blog/cta-button "Try Pulumi for Free" "/docs/get-started/" >}}
Loading