From a4e3881896f06ae7f3ef44a7413bea8691bc7c2e Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Sat, 24 Jan 2026 14:40:55 +0100 Subject: [PATCH] chore: sync content to repo (#9560) Co-authored-by: kamranahmedse <4921183+kamranahmedse@users.noreply.github.com> --- ...ptimizing-resource-usage@PP4ld_vvjpY3QltBBsXKD.md | 2 +- ...pod-to-pod-communication@44rhdieUCWsGFC_1__9kk.md | 8 ++++---- ...lling-updates--rollbacks@yMSXdwDO36CLtp2TBC7aB.md | 12 +++++++----- 3 files changed, 12 insertions(+), 10 deletions(-) diff --git a/src/data/roadmaps/kubernetes/content/monitoring--optimizing-resource-usage@PP4ld_vvjpY3QltBBsXKD.md b/src/data/roadmaps/kubernetes/content/monitoring--optimizing-resource-usage@PP4ld_vvjpY3QltBBsXKD.md index 5db32da80..2c442f776 100644 --- a/src/data/roadmaps/kubernetes/content/monitoring--optimizing-resource-usage@PP4ld_vvjpY3QltBBsXKD.md +++ b/src/data/roadmaps/kubernetes/content/monitoring--optimizing-resource-usage@PP4ld_vvjpY3QltBBsXKD.md @@ -8,4 +8,4 @@ Visit the following resources to learn more: - [@official@Metrics Server](https://kubernetes.io/docs/tasks/debug/debug-cluster/resource-metrics-pipeline/#metrics-server) - [@official@Horizontal Pod Autoscaling](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) - [@article@Kubernetes Resource Monitoring: Best Practices](https://www.redhat.com/en/blog/kubernetes-resource-monitoring-best-practices) -- [@article@Optimizing Kubernetes Resource Utilization](https://thenewstack.io/optimizing-kubernetes-resource-utilization/) +- [@article@Optimizing Kubernetes Resource Utilization](https://thenewstack.io/optimizing-kubernetes-resource-utilization/) \ No newline at end of file diff --git a/src/data/roadmaps/kubernetes/content/networking--pod-to-pod-communication@44rhdieUCWsGFC_1__9kk.md b/src/data/roadmaps/kubernetes/content/networking--pod-to-pod-communication@44rhdieUCWsGFC_1__9kk.md index df0e549b8..c786b8bb9 100644 --- a/src/data/roadmaps/kubernetes/content/networking--pod-to-pod-communication@44rhdieUCWsGFC_1__9kk.md +++ b/src/data/roadmaps/kubernetes/content/networking--pod-to-pod-communication@44rhdieUCWsGFC_1__9kk.md @@ -8,7 +8,7 @@ Reliable pod-to-pod networking is a core requirement for building distributed an Visit the following resources to learn more: -* [@official@Cluster Networking - Kubernetes Documentation](https://kubernetes.io/docs/concepts/cluster-administration/networking/) -* [@official@Network Policies - Kubernetes Documentation](https://kubernetes.io/docs/concepts/services-networking/network-policies/) -* [@article@Kubernetes Networking Explained](https://www.tigera.io/learn/guides/kubernetes-networking/) -* [@video@Kubernetes Networking Deep Dive](https://www.youtube.com/watch?v=t98ekMiz0hQ) +- [@official@Cluster Networking - Kubernetes Documentation](https://kubernetes.io/docs/concepts/cluster-administration/networking/) +- [@official@Network Policies - Kubernetes Documentation](https://kubernetes.io/docs/concepts/services-networking/network-policies/) +- [@article@Kubernetes Networking Explained](https://www.tigera.io/learn/guides/kubernetes-networking/) +- [@video@Kubernetes Networking Deep Dive](https://www.youtube.com/watch?v=t98ekMiz0hQ) \ No newline at end of file diff --git a/src/data/roadmaps/kubernetes/content/rolling-updates--rollbacks@yMSXdwDO36CLtp2TBC7aB.md b/src/data/roadmaps/kubernetes/content/rolling-updates--rollbacks@yMSXdwDO36CLtp2TBC7aB.md index 9c198d5cb..13fa0b527 100644 --- a/src/data/roadmaps/kubernetes/content/rolling-updates--rollbacks@yMSXdwDO36CLtp2TBC7aB.md +++ b/src/data/roadmaps/kubernetes/content/rolling-updates--rollbacks@yMSXdwDO36CLtp2TBC7aB.md @@ -1,9 +1,11 @@ -# Kuberenetes +# Rolling Updates and Rollbacks -Kubernetes, also known as K8s, is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications. It allows developers to focus on writing code while Kubernetes handles the underlying infrastructure. Kubernetes uses declarative configuration files to specify the desired state of an application, and can automatically scale applications based on demand, handle failovers, and manage networking and storage. It is widely used in cloud-native architectures that rely on microservices and containers for production deployments. +Rolling updates and rollbacks are methods for updating applications without downtime. A rolling update gradually replaces old versions of an application with new ones, ensuring that some instances of the application are always available. If problems arise during the update, a rollback allows you to revert to the previous, stable version of the application. Visit the following resources to learn more: -- [@official@Overview of Kubernetes](https://kubernetes.io/docs/concepts/overview/) -- [@video@Kubernetes Explained in 100 Seconds](https://www.youtube.com/watch?v=PziYflu8cB8) -- [@video@Kubernetes Tutorial for Beginners](https://www.youtube.com/watch?v=X48VuDVv0do&t=1s) \ No newline at end of file +- [@official@Performing a Rolling Update](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/) +- [@article@How do you rollback deployments in Kubernetes?](https://learnkube.com/kubernetes-rollbacks) +- [@video@Kubernetes Deployments: A Guide to the Rolling Update Deployment Strategy](https://semaphore.io/blog/kubernetes-rolling-update-deployment) +- [@video@Kubernetes Rollbacks Tutorial](https://www.youtube.com/watch?v=9hK11Ov74U4) +- [@video@Kubernetes Deployment strategies | Rolling Update Deployment | Argo rollout | ADAM](https://www.youtube.com/watch?v=cy3KXqgJOrE) \ No newline at end of file