# kubectl

kubectl is the Kubernetes command-line tool.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Bypassing the 256KB Kubernetes CRD Limit with Server-Side Apply

DevFeed: [Bypassing the 256KB Kubernetes CRD Limit with Server-Side Apply](<https://devfeed.tech/articles/bypassing-the-256kb-kubernetes-crd-limit-with-server-side-apply-109721.md>)

Original publisher: [Read original article](<https://blog.devops.dev/bypassing-the-256kb-kubernetes-crd-limit-with-server-side-apply-53ada7b4ce89?source=rss----33f8b2d9a328---4>)

Author: Techie Crow

Published: 2026-10-30T18:59:19Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [annotation](<https://devfeed.tech/tags/annotation.md>), [annotations](<https://devfeed.tech/tags/annotations.md>), [apply](<https://devfeed.tech/tags/apply.md>), [argo-cd](<https://devfeed.tech/tags/argo-cd.md>), [cert-manager](<https://devfeed.tech/tags/cert-manager.md>), [crd](<https://devfeed.tech/tags/crd.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [devops](<https://devfeed.tech/tags/devops.md>), [error](<https://devfeed.tech/tags/error.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-operators](<https://devfeed.tech/tags/kubernetes-operators.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [operators](<https://devfeed.tech/tags/operators.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [resources](<https://devfeed.tech/tags/resources.md>), [schemas](<https://devfeed.tech/tags/schemas.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [ssa](<https://devfeed.tech/tags/ssa.md>), [type-safe](<https://devfeed.tech/tags/type-safe.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

Large Kubernetes CRDs can exceed the 262,144-byte annotation limit because client-side `kubectl apply` stores a duplicate of the full manifest in `kubectl.kubernetes.io/last-applied-configuration`; extensive OpenAPI v3 validation schemas can make CRDs especially large. The excerpt identifies Server-Side Apply (SSA) as the workaround, but does not include the promised procedure or example.

### Source excerpt

Continue reading on DevOps.dev "

## Kubernetes CrashLoopBackOff: A Practical Troubleshooting Guide

DevFeed: [Kubernetes CrashLoopBackOff: A Practical Troubleshooting Guide](<https://devfeed.tech/articles/kubernetes-crashloopbackoff-a-practical-troubleshooting-guide-103395.md>)

Original publisher: [Read original article](<https://blog.devops.dev/kubernetes-crashloopbackoff-a-practical-troubleshooting-guide-3649ddde6902?source=rss----33f8b2d9a328---4>)

Author: Oluwayemi Aina

Published: 2026-10-27T10:18:09Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [CrashLoopBackOff troubleshooting](<https://devfeed.tech/topics/crashloopbackoff-troubleshooting.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [application](<https://devfeed.tech/tags/application.md>), [attention](<https://devfeed.tech/tags/attention.md>), [can](<https://devfeed.tech/tags/can.md>), [cause](<https://devfeed.tech/tags/cause.md>), [code](<https://devfeed.tech/tags/code.md>), [commands](<https://devfeed.tech/tags/commands.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [container](<https://devfeed.tech/tags/container.md>), [crash](<https://devfeed.tech/tags/crash.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [devops](<https://devfeed.tech/tags/devops.md>), [don-t](<https://devfeed.tech/tags/don-t.md>), [events](<https://devfeed.tech/tags/events.md>), [example](<https://devfeed.tech/tags/example.md>), [exit](<https://devfeed.tech/tags/exit.md>), [guide](<https://devfeed.tech/tags/guide.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [practical](<https://devfeed.tech/tags/practical.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [tech](<https://devfeed.tech/tags/tech.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>)

### AI overview

CrashLoopBackOff reports repeated container termination with delayed restart attempts; it does not identify the root cause. The guide recommends finding the affected pod with `kubectl get pods`, inspecting its state and events with `kubectl describe pod`, and reading the previous instance's logs with `kubectl logs --previous` when available. Correlate termination reason, exit code, events, and logs to investigate application errors, configuration or dependency failures, probe problems, and memory limits; an exit code alone may not establish the cause. Check that liveness probe paths, ports, and timing match the application, and consider a startup probe if initialization takes longer. Apply one evidence-based fix at a time, then verify the pod remains healthy, readiness succeeds, and the application works. The supplied text ends during its explanation of previous logs, so this overview relies on the included source summary and excerpt.

### Source excerpt

If you have worked with Kubernetes, you may have encountered a pod that starts, fails, restarts, and repeats the same cycle. Eventually, Kubernetes reports: CrashLoopBackOff The first instinct is often to restart the pod or redeploy the application. However, restarting a pod does not fix the underlying problem if the application continues to fail. In this guide, we'll walk through a systematic way to investigate the issue, identify common causes, and choose the appropriate fix. What does CrashLoopBackOff mean? CrashLoopBackOff means a container in a pod has repeatedly terminated, and Kubernetes is delaying subsequent restart attempts. It is a status indicating a restart problem, not the root cause itself. The underlying issue could be an application crash, incorrect configuration, a missing dependency, a failed health check, or insufficient memory. Step 1: Identify the affected pod Start by listing pods in the namespace where your application runs: kubectl get pods -n <namespace> Example output: NAME READY STATUS RESTARTS api-service-7d9f8c9b-x2k4p 0/1 CrashLoopBackOff 5 Record the pod name and its restart count. If you don't know the namespace, you can list pods across namespaces: kubectl get pods -A Step 2: Inspect the pod events Next, examine the pod's configuration, container states, and recent events: kubectl describe pod <pod-name> -n <namespace> Pay attention to: The container's last termination state. The exit code and termination reason. Liveness and readiness probe failures. Events mentioning failed mounts, image problems, or resource limits. For example, a termination reason of OOMKilled suggests the container was terminated after exceeding its memory limit. Don't assume every CrashLoopBackOff is a memory issue. Use the evidence from the pod description to narrow the investigation. Step 3: Read the previous container logs This is one of the most useful troubleshooting commands: kubectl logs <pod-name> -n <namespace> --previous The --previous flag requests

## From Image to Ready Pod: A Step-by-Step Kubernetes / OpenShift Troubleshooting Guide

DevFeed: [From Image to Ready Pod: A Step-by-Step Kubernetes / OpenShift Troubleshooting Guide](<https://devfeed.tech/articles/from-image-to-ready-pod-a-step-by-step-kubernetes-openshift-troubleshooting-guide-90784.md>)

Original publisher: [Read original article](<https://blog.devops.dev/from-image-to-ready-pod-a-step-by-step-kubernetes-openshift-troubleshooting-guide-767f9edbeec0?source=rss----33f8b2d9a328---4>)

Author: Nirbhay Singh

Published: 2026-10-20T13:26:06Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [kubectl](<https://devfeed.tech/topics/kubectl.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [devops](<https://devfeed.tech/tags/devops.md>), [docker](<https://devfeed.tech/tags/docker.md>), [guide](<https://devfeed.tech/tags/guide.md>), [image](<https://devfeed.tech/tags/image.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [pod](<https://devfeed.tech/tags/pod.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>)

### AI overview

A deployment progress deadline means the new pods did not become Ready in time, but does not identify the cause. The excerpt recommends tracing the pod lifecycle in order--from image build and registry push through scheduling, image pull, volume mounting, container startup, listening, and readiness probe--to find the first failing stage. It says `oc` supports the same command syntax as `kubectl` and adds OpenShift-specific tools and features, including `oc debug`, `oc rsh`, `oc set probe`, routes, and projects. The excerpt does not provide the detailed commands or stage-specific signals.

### Source excerpt

How to work through any failed deployment, from the image to the Ready pod, with kubectl and oc side by side and every command explained. Continue reading on DevOps.dev "

## Day 64: Fix Python App Deployed on Kubernetes Cluster.A Real DevOps Troubleshooting Story

DevFeed: [Day 64: Fix Python App Deployed on Kubernetes Cluster.A Real DevOps Troubleshooting Story](<https://devfeed.tech/articles/day-64-fix-python-app-deployed-on-kubernetes-cluster-a-real-devops-troubleshooting-story-89420.md>)

Original publisher: [Read original article](<https://blog.devops.dev/day-64-fix-python-app-deployed-on-kubernetes-cluster-a-real-devops-troubleshooting-story-35e79bdf052d?source=rss----33f8b2d9a328---4>)

Author: Yashvi Kothari

Published: 2026-10-17T20:01:02Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [AIOps for Kubernetes](<https://devfeed.tech/topics/aiops-for-kubernetes.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>), [container-networking](<https://devfeed.tech/topics/container-networking.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [devops](<https://devfeed.tech/tags/devops.md>), [flask](<https://devfeed.tech/tags/flask.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [linux](<https://devfeed.tech/tags/linux.md>), [python](<https://devfeed.tech/tags/python.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>)

### AI overview

The excerpt identifies a wrong container image as the observed Deployment issue: it uses `poroko/flask-app-demo` instead of the specified `poroko/flask-demo-app`; the container port is already 5000. It recommends correcting the image, then inspecting the separately named `python-service-datacenter`: its displayed mapping shows NodePort 32345, while the excerpt says to verify that `targetPort` is 5000 and patch it if needed. The text also includes conflicting later directions to edit a nonexistent `python-deployment-datacenter` Service and use port 5000, so the exact service configuration is unclear. It provides verification commands but no confirmed successful rollout or accessibility result.

### Source excerpt

Your Kubernetes Deployment can be perfectly configured and still fail to run your application. That sounds strange until you understand one thing: Kubernetes doesn't know what you intended to deploy. It only knows what you configured. One wrong Docker image name. One incorrect service port. One mismatched selector. That's enough to take an application offline. On Day 64 of my 100 Days of DevOps journey, I encountered exactly this problem. A Python Flask application was deployed to Kubernetes, but it wasn't coming up. The task sounded simple: Make the application accessible through NodePort 32345. The actual lesson went much deeper. 100 Days of DevOps One of the DevOps engineers was trying to deploy a python app on Kubernetes cluster. Unfortunately, due to some mis-configuration, the application is not coming up. Please take a look into it and fix the issues. Application should be accessible on the specified nodePort. The deployment name is python-deployment-datacenter, its using poroko/flask-demo-app image. The deployment and service of this app is already deployed. nodePort should be 32345 and targetPort should be python flask app's default port. Note: The kubectl utility on the jump-host has been configured to work with the Kubernetes cluster. Run these commands on the jump-host: Check the current deployment and service: kubectl get deployment python-deployment-datacenter kubectl get svc kubectl get pods Fix the deployment's container port to Flask's default 5000: kubectl edit deployment python-deployment-datacenter Make sure the container has: ports: - containerPort: 5000thor@jump-host ~$ kubectl get deployment python-deployment-datacenter -o yaml apiVersion: apps/v1 kind: Deployment metadata: annotations: deployment.kubernetes.io/revision: "1" kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"apps/v1","kind":"Deployment","metadata":{"annotations":{},"name":"python-deployment-datacenter","namespace":"default"},"spec":{"replicas":1,"selector":{"ma

## Day 62: Manage Secrets in Kubernetes.Stop Hardcoding Passwords Like It's 2005

DevFeed: [Day 62: Manage Secrets in Kubernetes.Stop Hardcoding Passwords Like It's 2005](<https://devfeed.tech/articles/day-62-manage-secrets-in-kubernetes-stop-hardcoding-passwords-like-it-s-2005-66373.md>)

Original publisher: [Read original article](<https://blog.devops.dev/day-62-manage-secrets-in-kubernetes-stop-hardcoding-passwords-like-its-2005-66ba69893070?source=rss----33f8b2d9a328---4>)

Author: Yashvi Kothari

Published: 2026-10-06T21:06:01Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>), [HashiCorp Vault](<https://devfeed.tech/topics/hashicorp-vault.md>), [ls](<https://devfeed.tech/topics/ls.md>)

Tags: [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [debian](<https://devfeed.tech/tags/debian.md>), [devops](<https://devfeed.tech/tags/devops.md>), [ecommerce](<https://devfeed.tech/tags/ecommerce.md>), [generic](<https://devfeed.tech/tags/generic.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-secrets](<https://devfeed.tech/tags/kubernetes-secrets.md>), [latest-tag](<https://devfeed.tech/tags/latest-tag.md>), [license](<https://devfeed.tech/tags/license.md>), [linux](<https://devfeed.tech/tags/linux.md>), [password](<https://devfeed.tech/tags/password.md>), [pod](<https://devfeed.tech/tags/pod.md>), [secrets](<https://devfeed.tech/tags/secrets.md>)

### AI overview

The challenge creates a Kubernetes generic Secret named `ecommerce` from `/opt/ecommerce.txt`, then mounts it at `/opt/games` in a `secret-xfusion` pod running `debian:latest` with a sleep command. The excerpt says to verify the pod reaches Running and check the mounted file from the container. It also cautions that Kubernetes Secrets are base64 encoded, not encrypted by default, and recommends RBAC, encryption at rest, or external secret managers for production. The source text ends mid-instruction, but the supplied article text includes these implementation steps.

### Source excerpt

Your application needs credentials. A database password. An API key. A software license. The easiest mistake? Putting it directly inside your Kubernetes YAML file. It works. Until it doesn't. Because anything stored in plain text eventually becomes someone else's problem. Good DevOps engineers don't ask: "How do I make this run?" They ask: "How do I make this run safely at scale?" That is where Kubernetes Secrets enter the picture. The Problem: Applications Need Secrets, But Humans Create Risks Imagine this: env: - name: DATABASE_PASSWORD value: "SuperSecret123" Your password is now: In Git history Visible to teammates Stored in CI/CD logs Potentially exposed forever Deleting the line later does not remove the history. The internet remembers. Kubernetes Secret: The Secure Storage Layer A Kubernetes Secret stores sensitive information separately from your application configuration. Think of it like this: Application | ↓ Kubernetes Secret | ↓ Password / API Key / License Your application knows: "I need this secret." But it does not need to know: "Where did this value come from?" That separation is powerful. Day 62 Challenge: Store License Data Securely 100 Days of DevOps The Nautilus DevOps team is working to deploy some tools in Kubernetes cluster. Some of the tools are licence based so that licence information needs to be stored securely within Kubernetes cluster. Therefore, the team wants to utilize Kubernetes secrets to store those secrets. Below you can find more details about the requirements: We already have a secret key file ecommerce.txt under the /opt/ directory. Create a generic secret named ecommerce, it should contain the password/license-number present in ecommerce.txt file. Also create a pod named secret-xfusion. Configure pod's spec as container name should be secret-container-xfusion, image should be debian with latest tag (remember to mention the tag with image). Use sleep command for container so that it remains in running state. Consume the created

## Kubernetes Pods Explained: A Simple Guide to Understanding Pods

DevFeed: [Kubernetes Pods Explained: A Simple Guide to Understanding Pods](<https://devfeed.tech/articles/kubernetes-pods-explained-a-simple-guide-to-understanding-pods-63838.md>)

Original publisher: [Read original article](<https://blog.devops.dev/kubernetes-pods-explained-a-simple-guide-to-understanding-pods-462431a45f4d?source=rss----33f8b2d9a328---4>)

Author: DevOps voice

Published: 2026-10-02T08:04:47Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [devops](<https://devfeed.tech/tags/devops.md>), [devops-practice](<https://devfeed.tech/tags/devops-practice.md>), [docker](<https://devfeed.tech/tags/docker.md>), [k8s](<https://devfeed.tech/tags/k8s.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-pods](<https://devfeed.tech/tags/kubernetes-pods.md>), [pods](<https://devfeed.tech/tags/pods.md>)

### AI overview

The excerpt introduces the distinction that Kubernetes runs containers through Pods rather than directly, and frames understanding the relationship among containers, Pods, and nodes as a foundation for understanding Kubernetes. It does not provide the promised details about how Pods work, scale, or are created.

### Source excerpt

What a Pod is, why Kubernetes uses it, how Pods scale, and how to create your first Pod Continue reading on DevOps.dev "

## How to Debug a Stuck Kubernetes Rollout with a Hands-On Lab

DevFeed: [How to Debug a Stuck Kubernetes Rollout with a Hands-On Lab](<https://devfeed.tech/articles/how-to-debug-a-stuck-kubernetes-rollout-with-a-hands-on-lab-63486.md>)

Original publisher: [Read original article](<https://www.freecodecamp.org/news/how-to-debug-a-stuck-kubernetes-rollout-with-a-hands-on-lab/>)

Author: Praneeth Kodumagulla

Published: 2026-10-01T11:02:33Z

Content type: tutorial

Language: en

Sources: [Free Code Camp](<https://devfeed.tech/sources/freecodecamp-programming-tutorials-python-javascript-git-more.md>)

Topics: [kubectl](<https://devfeed.tech/topics/kubectl.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [cluster](<https://devfeed.tech/tags/cluster.md>), [command](<https://devfeed.tech/tags/command.md>), [containers](<https://devfeed.tech/tags/containers.md>), [controller](<https://devfeed.tech/tags/controller.md>), [debug](<https://devfeed.tech/tags/debug.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [devops](<https://devfeed.tech/tags/devops.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [docker](<https://devfeed.tech/tags/docker.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [lab](<https://devfeed.tech/tags/lab.md>)

### AI overview

This hands-on Kubernetes tutorial uses a disposable lab to demonstrate three causes of a stuck rollout: an unavailable image, a failing readiness probe, and an unmatched node selector. It shows how to trace Deployment, ReplicaSet, and Pod ownership; inspect Events and EndpointSlices; identify which Pods answered Service requests; distinguish a client-side wait timeout from the controller's progress deadline; and verify recovery. Its findings come from a single-node local lab and finite HTTP samples.

### Source excerpt

You update a Deployment, run kubectl rollout status, and wait. The command times out. But when you send a request to the Service, it still answers. So did the update finish? And if it didn't, which Po

## SSO-Backed kubectl Access Across Many Clusters

DevFeed: [SSO-Backed kubectl Access Across Many Clusters](<https://devfeed.tech/articles/sso-backed-kubectl-access-across-many-clusters-64206.md>)

Original publisher: [Read original article](<https://goteleport.com/blog/sso-backed-kubectl-access-multiple-clusters/>)

Author: info@goteleport.com (Daniele Polencic)

Published: 2026-10-01T00:00:00Z

Content type: tutorial

Language: en

Sources: [Teleport](<https://devfeed.tech/sources/teleport.md>)

Topics: [kubectl](<https://devfeed.tech/topics/kubectl.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

This tutorial explains how OIDC token audiences affect kubectl authentication across development, staging, and production Kubernetes clusters. A shared audience lets the same cached token authenticate to every cluster, while separate audiences can make production reject non-production tokens before RBAC applies. It also covers how duplicate user names in merged kubeconfig files can cause a context to request the wrong audience, and recommends choosing the smallest set of audiences that limits where copied tokens can authenticate.

### Source excerpt

Learn how to configure multi-cluster kubectl access.

## Deploy Microcks on OVHcloud Managed Kubernetes Service (MKS)

DevFeed: [Deploy Microcks on OVHcloud Managed Kubernetes Service (MKS)](<https://devfeed.tech/articles/deploy-microcks-on-ovhcloud-managed-kubernetes-service-mks-58601.md>)

Original publisher: [Read original article](<https://blog.ovhcloud.com/en/posts/deploy-microcks-ovhcloud-mks/>)

Author: Aurélie Vache

Published: 2026-09-21T12:00:00Z

Content type: tutorial

Language: en

Sources: [OVHcloud Blog](<https://devfeed.tech/sources/ovhcloud-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [API](<https://devfeed.tech/topics/api.md>), [gateway](<https://devfeed.tech/topics/gateway.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [MongoDB](<https://devfeed.tech/topics/mongodb.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Postman](<https://devfeed.tech/topics/postman.md>)

Tags: [accelerating-with-ovhcloud](<https://devfeed.tech/tags/accelerating-with-ovhcloud.md>), [api](<https://devfeed.tech/tags/api.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [envoy](<https://devfeed.tech/tags/envoy.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [gateway-api](<https://devfeed.tech/tags/gateway-api.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [managed-kubernetes](<https://devfeed.tech/tags/managed-kubernetes.md>), [mks](<https://devfeed.tech/tags/mks.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [ovhcloud](<https://devfeed.tech/tags/ovhcloud.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### AI overview

A tutorial for deploying the open-source Microcks API mocking and testing tool on an OVHcloud Managed Kubernetes Service cluster. It covers exposing Microcks through the Kubernetes Gateway API, Envoy Gateway, and an OVHcloud Public Cloud Load Balancer, with prerequisites and initial cluster setup.

### Source excerpt

Learn how to deploy Microcks on an OVHcloud Managed Kubernetes cluster and expose it with Gateway API, Envoy Gateway, and cert-manager TLS.

## Kubernetes Architecture: Control Plane, Scheduler, and Kubelet

DevFeed: [Kubernetes Architecture: Control Plane, Scheduler, and Kubelet](<https://devfeed.tech/articles/what-is-kubernetes-39552.md>)

Original publisher: [Read original article](<https://kodekloud.com/blog/kubernetes-basics-architecture-pods-services/>)

Author: Nimesha Jinarajadasa

Published: 2026-09-17T06:25:02Z

Content type: tutorial

Language: en

Sources: [KodeKloud](<https://devfeed.tech/sources/kubernetes-kodekloud-blog-devops-cloud-kubernetes-ai-tutorials-more.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [api server](<https://devfeed.tech/topics/api-server.md>), [container](<https://devfeed.tech/topics/container.md>), [etcd](<https://devfeed.tech/topics/etcd.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [containers](<https://devfeed.tech/tags/containers.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [controllers](<https://devfeed.tech/tags/controllers.md>), [etcd](<https://devfeed.tech/tags/etcd.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-architecture](<https://devfeed.tech/tags/kubernetes-architecture.md>), [kubernetes-networking](<https://devfeed.tech/tags/kubernetes-networking.md>), [node](<https://devfeed.tech/tags/node.md>), [scheduler](<https://devfeed.tech/tags/scheduler.md>)

### AI overview

A beginner-friendly tutorial explaining how Kubernetes maintains the desired state of containerized applications. It covers the control plane, API server, etcd, controllers, scheduler, and kubelet.

### Source excerpt

Learn how Kubernetes works, from the control plane and scheduler to kubelet, pods, and Services, with simple answers to interview questions.

## 7 Best Kubernetes Management Tools Tested & Ranked for 2026

DevFeed: [7 Best Kubernetes Management Tools Tested & Ranked for 2026](<https://devfeed.tech/articles/7-best-kubernetes-management-tools-tested-ranked-for-2026-50998.md>)

Original publisher: [Read original article](<https://www.portainer.io/blog/best-kubernetes-management-tools>)

Author: Portainer Team

Published: 2026-07-29T00:00:00Z

Content type: comparison

Language: en

Sources: [Portainer](<https://devfeed.tech/sources/portainer-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Portainer](<https://devfeed.tech/topics/portainer.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [GitOps](<https://devfeed.tech/topics/gitops.md>), [podman](<https://devfeed.tech/topics/podman.md>), [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Gke](<https://devfeed.tech/topics/gke.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>), [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [7-best](<https://devfeed.tech/tags/7-best.md>), [admin](<https://devfeed.tech/tags/admin.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [continuous-delivery](<https://devfeed.tech/tags/continuous-delivery.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [docker](<https://devfeed.tech/tags/docker.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [gke](<https://devfeed.tech/tags/gke.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [management](<https://devfeed.tech/tags/management.md>), [platform](<https://devfeed.tech/tags/platform.md>), [portainer](<https://devfeed.tech/tags/portainer.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [support](<https://devfeed.tech/tags/support.md>), [tools](<https://devfeed.tech/tags/tools.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

A comparison of Kubernetes management tools that presents Portainer as a self-hosted platform for managing Kubernetes, Docker, and Podman across cloud and on-premises environments. The excerpt highlights its GUI, cluster support, CLI compatibility, repository integration, webhook syncing, continuous delivery, and GitOps automation.

### Source excerpt

Portainer : Kubernetes management platform for enterprises with intuitive UI, multi-orchestrator support , visual RBAC, and minimal learning curve for...

## How to Build a Kubernetes Troubleshooting AI Agent with LangChain and kubectl

DevFeed: [How to Build a Kubernetes Troubleshooting AI Agent with LangChain and kubectl](<https://devfeed.tech/articles/how-to-build-a-kubernetes-troubleshooting-ai-agent-with-langchain-and-kubectl-17484.md>)

Original publisher: [Read original article](<https://kodekloud.com/blog/kubernetes-troubleshooting-ai-agent-langchain-kubectl/>)

Author: Pramodh Kumar M

Published: 2026-07-27T17:26:08Z

Content type: tutorial

Language: en

Sources: [KodeKloud](<https://devfeed.tech/sources/kubernetes-kodekloud-blog-devops-cloud-kubernetes-ai-tutorials-more.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>), [LangChain](<https://devfeed.tech/topics/langchain.md>), [Tutorial](<https://devfeed.tech/topics/tutorial.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-for-kubernetes](<https://devfeed.tech/tags/ai-agent-for-kubernetes.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [aiops-for-kubernetes](<https://devfeed.tech/tags/aiops-for-kubernetes.md>), [automation](<https://devfeed.tech/tags/automation.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [crashloopbackoff-troubleshooting](<https://devfeed.tech/tags/crashloopbackoff-troubleshooting.md>), [devops](<https://devfeed.tech/tags/devops.md>), [human-in-the-loop-agent](<https://devfeed.tech/tags/human-in-the-loop-agent.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubectl-ai-agent](<https://devfeed.tech/tags/kubectl-ai-agent.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-rbac-for-ai-agents](<https://devfeed.tech/tags/kubernetes-rbac-for-ai-agents.md>), [kubernetes-troubleshooting-ai-agent](<https://devfeed.tech/tags/kubernetes-troubleshooting-ai-agent.md>), [kubernetes-troubleshooting-automation](<https://devfeed.tech/tags/kubernetes-troubleshooting-automation.md>), [langchain](<https://devfeed.tech/tags/langchain.md>), [langchain-kubernetes-agent](<https://devfeed.tech/tags/langchain-kubernetes-agent.md>), [langgraph](<https://devfeed.tech/tags/langgraph.md>), [langgraph-agent-tutorial](<https://devfeed.tech/tags/langgraph-agent-tutorial.md>), [python](<https://devfeed.tech/tags/python.md>), [react-agent-python](<https://devfeed.tech/tags/react-agent-python.md>), [security](<https://devfeed.tech/tags/security.md>), [tool](<https://devfeed.tech/tags/tool.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

A tutorial on building a Kubernetes troubleshooting AI agent with LangChain v1 and kubectl. It describes a diagnostic ladder for investigating pod failures, read-only tools, approval requirements for write operations, separate identities for remediation, and a golden trace suite for evaluating results.

### Source excerpt

Most pod failures resolve into six root causes, and the investigation is identical every time. Here is how to build an agent that runs that investigation for you, with a hard boundary between reading a cluster and changing one.

## Building AI Agents That Manage Kubernetes

DevFeed: [Building AI Agents That Manage Kubernetes](<https://devfeed.tech/articles/building-ai-agents-that-manage-kubernetes-17481.md>)

Original publisher: [Read original article](<https://kodekloud.com/blog/building-ai-agents-that-manage-kubernetes/>)

Author: Nimesha Jinarajadasa

Published: 2026-07-27T05:00:53Z

Content type: tutorial

Language: en

Sources: [KodeKloud](<https://devfeed.tech/sources/kubernetes-kodekloud-blog-devops-cloud-kubernetes-ai-tutorials-more.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [python](<https://devfeed.tech/tags/python.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

A hands-on tutorial for building a supervised AI agent that manages Kubernetes through an LLM and kubectl tool-calling loop. The agent reads cluster state, proposes approved actions such as scaling a deployment, applies guardrails and human approval, and verifies the result on a throwaway cluster.

### Source excerpt

Build a supervised AI agent that manages Kubernetes: an LLM in a kubectl tool loop with real guardrails. Full hands-on tutorial, live output.

## Navigating OVHcloud File Storage with Manila CSI (RWX) on Kubernetes clusters (MKS)

DevFeed: [Navigating OVHcloud File Storage with Manila CSI (RWX) on Kubernetes clusters (MKS)](<https://devfeed.tech/articles/navigating-ovhcloud-file-storage-with-manila-csi-rwx-on-kubernetes-clusters-mks-50600.md>)

Original publisher: [Read original article](<https://blog.ovhcloud.com/en/posts/manila-csi-ovhcloud-file-storage/>)

Author: Aurélie Vache

Published: 2026-07-16T12:16:24Z

Content type: tutorial

Language: en

Sources: [OVHcloud Blog](<https://devfeed.tech/sources/ovhcloud-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [openstack](<https://devfeed.tech/topics/openstack.md>), [Filesystems](<https://devfeed.tech/topics/filesystems.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [clusters](<https://devfeed.tech/tags/clusters.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [file](<https://devfeed.tech/tags/file.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-clusters](<https://devfeed.tech/tags/kubernetes-clusters.md>), [managed-kubernetes](<https://devfeed.tech/tags/managed-kubernetes.md>), [mks](<https://devfeed.tech/tags/mks.md>), [openstack](<https://devfeed.tech/tags/openstack.md>), [ovhcloud](<https://devfeed.tech/tags/ovhcloud.md>), [pv](<https://devfeed.tech/tags/pv.md>), [stateful](<https://devfeed.tech/tags/stateful.md>), [storage](<https://devfeed.tech/tags/storage.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

A tutorial on integrating OVHcloud File Storage with OVHcloud Managed Kubernetes Service using the OpenStack Manila CSI driver. It explains how to provide shared NFS-backed persistent storage for stateful Kubernetes workloads and outlines the required tools, configuration, and deployment steps.

### Source excerpt

If you run stateful applications on Kubernetes, one common challenge is providing shared persistent storage that can be accessed by multiple workloads.

## Flux marks 10 years of continuous delivery and GitOps development

DevFeed: [Flux marks 10 years of continuous delivery and GitOps development](<https://devfeed.tech/articles/blog-flux-turns-10-48654.md>)

Original publisher: [Read original article](<https://fluxcd.io/blog/2026/07/flux-turns-10/>)

Author: Leigh Capili

Published: 2026-07-07T11:00:00Z

Content type: article

Language: en

Sources: [Flux - Blog](<https://devfeed.tech/sources/flux-blog.md>)

Topics: [flux](<https://devfeed.tech/topics/flux.md>), [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>), [GitOps](<https://devfeed.tech/topics/gitops.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [Script](<https://devfeed.tech/topics/script.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [continuous-delivery](<https://devfeed.tech/tags/continuous-delivery.md>), [devops](<https://devfeed.tech/tags/devops.md>), [flux](<https://devfeed.tech/tags/flux.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [repo](<https://devfeed.tech/tags/repo.md>), [scripts](<https://devfeed.tech/tags/scripts.md>), [self-service](<https://devfeed.tech/tags/self-service.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

Flux's tenth-anniversary retrospective traces the project from its 2016 initial commit through its early role in continuous delivery and GitOps. It covers Flux's Kubernetes workflow, the emergence of Operators and Helm Operator, and the project's later need to evolve beyond a monolithic architecture.

### Source excerpt

On Jul 7, 2016, Peter Bourgon made the initial commit a6fbd68a to iterate on a fresh way to do continuous delivery. Today, that commit is one decade old, and we celebrate 10 years of Flux. "Happy Birthday to Flux, the project that anticipated all of my needs and solves all my problems on a daily basis!" -- Kingdon Barrett, Flux Maintainer, DevOps Engineer @ Navteca The early repo shows Peter and Michael Bridgen implementing the fluxd daemon and fluxctl CLI; the repo also contains user stories on why people might want to use flux. An accompanying blogpost from Weaveworks invents the term GitOps with a relatable anecdote about production outages, disaster recovery, and "Operations by Pull Request." By August 2018, Stefan Prodan has joined Michael in contributing to the project. At this stage, Flux is gaining adoption amongst edgy teams of practitioners deploying Kubernetes v1.11. Flux runs inside your namespace, and dev teams can install it fully self-service. It clones your repo, runs scripts, checks container registries for image tags, and applies your changes with kubectl. GitOps is taking off, and Kubernetes is becoming people's day jobs. Extending Kubernetes 2016 also brings us a blog post from a company called CoreOS: Introducing Operators: Putting Operational Knowledge into Software [archive] It introduces "The Operator Pattern", which pairs Kubernetes' Third Party Resources with a controller implementing some domain knowledge around software to assist SREs. The diagrams are lovely. CoreOS works with others upstream and in the following year Custom Resource Definitions (CRDs) replace TPRs in Kubernetes 1.7. We start thinking about this in the Flux project, and in 2018 Tamara Kaufler writes the first iteration of Helm Operator: flux#947. We all get our first real taste of GitOps for Helm. Helm is still v2, so it still uses the Tiller in-cluster daemon. Remember that? In May of 2019 Hidde Beydals joins Stefan in contributing to Helm Operator, and we're learning ho

## Kubernetes Tutorial: Deploy, Expose, Scale, and Self-Heal Your First App

DevFeed: [Kubernetes Tutorial: Deploy, Expose, Scale, and Self-Heal Your First App](<https://devfeed.tech/articles/kubernetes-tutorial-deploy-your-first-app-on-kubernetes-today-17485.md>)

Original publisher: [Read original article](<https://kodekloud.com/blog/kubernetes-tutorial-deploy-first-app/>)

Author: Nimesha Jinarajadasa

Published: 2026-07-06T08:25:48Z

Content type: tutorial

Language: en

Sources: [KodeKloud](<https://devfeed.tech/sources/kubernetes-kodekloud-blog-devops-cloud-kubernetes-ai-tutorials-more.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Tutorial](<https://devfeed.tech/topics/tutorial.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>), [YAML](<https://devfeed.tech/topics/yaml.md>), [container](<https://devfeed.tech/topics/container.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [beginners](<https://devfeed.tech/tags/beginners.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [guide](<https://devfeed.tech/tags/guide.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [scale](<https://devfeed.tech/tags/scale.md>), [self-healing](<https://devfeed.tech/tags/self-healing.md>), [state](<https://devfeed.tech/tags/state.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [yaml](<https://devfeed.tech/tags/yaml.md>)

### AI overview

A beginner-friendly, hands-on tutorial that walks through deploying an application to a Kubernetes cluster, exposing it with a Service, scaling it, observing self-healing, and repeating the deployment declaratively with YAML and kubectl.

### Source excerpt

A hands-on Kubernetes tutorial for beginners: deploy your first app, expose and scale it, see self-healing, and use YAML with kubectl.

## 5 Best kubectl Alternatives for Kubernetes Management

DevFeed: [5 Best kubectl Alternatives for Kubernetes Management](<https://devfeed.tech/articles/5-best-kubectl-alternatives-for-kubernetes-management-51041.md>)

Original publisher: [Read original article](<https://www.portainer.io/blog/kubectl-alternatives>)

Author: Portainer Team

Published: 2026-06-30T00:00:00Z

Content type: comparison

Language: en

Sources: [Portainer](<https://devfeed.tech/sources/portainer-blog.md>)

Topics: [kubectl](<https://devfeed.tech/topics/kubectl.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Portainer](<https://devfeed.tech/topics/portainer.md>), [container](<https://devfeed.tech/topics/container.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [rancher](<https://devfeed.tech/topics/rancher.md>)

Tags: [alternatives](<https://devfeed.tech/tags/alternatives.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [portainer](<https://devfeed.tech/tags/portainer.md>), [rancher](<https://devfeed.tech/tags/rancher.md>)

### AI overview

A comparison of alternatives to kubectl for managing Kubernetes clusters. It examines visual interfaces, terminal tools, and management platforms that can reduce command-line and YAML overhead, especially for teams operating multiple clusters.

### Source excerpt

The top kubectl alternatives include Portainer, Lens, k9s, Rancher, and Headlamp, each offering a different approach to Kubernetes management.

## Server-side apply: what happens when you run kubectl apply

DevFeed: [Server-side apply: what happens when you run kubectl apply](<https://devfeed.tech/articles/server-side-apply-what-happens-when-you-run-kubectl-apply-19145.md>)

Original publisher: [Read original article](<https://learnkube.com/server-side-apply-kubernetes>)

Author: Chiara Salvatore

Published: 2026-06-30T00:00:00Z

Content type: article

Language: en

Sources: [Learnk8s](<https://devfeed.tech/sources/learnk8s.md>)

Topics: [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [apply](<https://devfeed.tech/tags/apply.md>), [argo-cd](<https://devfeed.tech/tags/argo-cd.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [controller](<https://devfeed.tech/tags/controller.md>), [controllers](<https://devfeed.tech/tags/controllers.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [field](<https://devfeed.tech/tags/field.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [helm](<https://devfeed.tech/tags/helm.md>), [hotfix](<https://devfeed.tech/tags/hotfix.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [logging](<https://devfeed.tech/tags/logging.md>), [manifest](<https://devfeed.tech/tags/manifest.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [operators](<https://devfeed.tech/tags/operators.md>), [ownership](<https://devfeed.tech/tags/ownership.md>)

### AI overview

Kubernetes server-side apply puts field ownership in the API server so apply-style tools can report conflicts instead of silently overwriting one another's changes to shared objects. The excerpt contrasts this with client-side apply, still described as kubectl's default: kubectl fetches the OpenAPI schema before apply or create, and apply checks whether the resource exists before deciding what to do. The excerpt ends during the update example, so it does not provide the full mechanics or further comparison.

### Source excerpt

Client-side apply can silently overwrite changes made by other tools. Server-side apply moves field ownership to the API server. Here is how it works and why it matters.

## Kubernetes Troubleshooting: How to Fix Common Errors in 2026

DevFeed: [Kubernetes Troubleshooting: How to Fix Common Errors in 2026](<https://devfeed.tech/articles/kubernetes-troubleshooting-how-to-fix-common-errors-in-2026-51064.md>)

Original publisher: [Read original article](<https://www.portainer.io/blog/kubernetes-troubleshooting>)

Author: Portainer Team

Published: 2026-05-27T00:00:00Z

Content type: tutorial

Language: en

Sources: [Portainer](<https://devfeed.tech/sources/portainer-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [container](<https://devfeed.tech/topics/container.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [clusters](<https://devfeed.tech/tags/clusters.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [errors](<https://devfeed.tech/tags/errors.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [pod](<https://devfeed.tech/tags/pod.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>)

### AI overview

A practical guide to troubleshooting Kubernetes errors across clusters, nodes, pods, containers, configurations, networking, and resource allocations. It emphasizes recognizing predictable failure patterns, diagnosing root causes across multiple layers, and using a structured workflow to resolve issues faster.

### Source excerpt

Stuck in CrashLoopBackOff or Pending pods? This Kubernetes troubleshooting guide helps you diagnose faster and fix the most common errors.

## Safe deployments with Temporal Worker Versioning on Kubernetes

DevFeed: [Safe deployments with Temporal Worker Versioning on Kubernetes](<https://devfeed.tech/articles/safe-deployments-with-temporal-worker-versioning-on-kubernetes-35967.md>)

Original publisher: [Read original article](<https://temporal.io/blog/safe-deployments-with-temporal-worker-versioning-on-kubernetes>)

Author: Michael Jones

Published: 2026-04-22T00:00:00Z

Content type: tutorial

Language: en

Sources: [Temporal](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [deployments](<https://devfeed.tech/tags/deployments.md>), [docker](<https://devfeed.tech/tags/docker.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [temporal](<https://devfeed.tech/tags/temporal.md>), [versioning](<https://devfeed.tech/tags/versioning.md>)

### AI overview

This tutorial demonstrates how Temporal Worker Versioning on Kubernetes can safely deploy Workflow code changes while preserving in-flight Workflows. It uses a research agent Workflow with expensive LLM calls to illustrate the risks of naive deployments and the deployment pattern that addresses them.

### Source excerpt

Non-determinism errors killing your in-flight Workflows? Michael Jones shows how Temporal's Worker Versioning lets old and new Workers run side by side, so nothing gets lost on deploy.

## Kubernetes 1.36 - New security features

DevFeed: [Kubernetes 1.36 - New security features](<https://devfeed.tech/articles/kubernetes-1-36-new-security-features-53241.md>)

Original publisher: [Read original article](<https://webflow.sysdig.com/blog/kubernetes-1-36-new-security-features>)

Author: Victor Jimenez Cerrada

Published: 2026-04-15T00:00:00Z

Content type: article

Language: en

Sources: [Sysdig](<https://devfeed.tech/sources/sysdig-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Security](<https://devfeed.tech/topics/security.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [configuration](<https://devfeed.tech/topics/configuration.md>)

Tags: [admission-controller](<https://devfeed.tech/tags/admission-controller.md>), [api](<https://devfeed.tech/tags/api.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [deprecation](<https://devfeed.tech/tags/deprecation.md>), [dynamic-resource-allocation-kubernetes](<https://devfeed.tech/tags/dynamic-resource-allocation-kubernetes.md>), [exploits](<https://devfeed.tech/tags/exploits.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-1-36](<https://devfeed.tech/tags/kubernetes-1-36.md>), [kubernetes-1-36-enhancements](<https://devfeed.tech/tags/kubernetes-1-36-enhancements.md>), [kubernetes-1-36-release](<https://devfeed.tech/tags/kubernetes-1-36-release.md>), [kubernetes-1-36-security-changes](<https://devfeed.tech/tags/kubernetes-1-36-security-changes.md>), [kubernetes-admission-control-changes](<https://devfeed.tech/tags/kubernetes-admission-control-changes.md>), [kubernetes-deprecations-1-36](<https://devfeed.tech/tags/kubernetes-deprecations-1-36.md>), [kubernetes-dra](<https://devfeed.tech/tags/kubernetes-dra.md>), [kubernetes-externalips-deprecation](<https://devfeed.tech/tags/kubernetes-externalips-deprecation.md>), [kubernetes-security-best-practices](<https://devfeed.tech/tags/kubernetes-security-best-practices.md>), [kubernetes-security-features-2026](<https://devfeed.tech/tags/kubernetes-security-features-2026.md>), [kubernetes-upgrade-1-36](<https://devfeed.tech/tags/kubernetes-upgrade-1-36.md>), [man-in-the-middle](<https://devfeed.tech/tags/man-in-the-middle.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

An overview of security changes planned for Kubernetes 1.36, including the deprecation of externalIPs, separation of kubectl user preferences from cluster configuration, and changes to pod certificate fields.

### Source excerpt

Kubernetes 1.36 will be released soon, bringing 60 enhancements. Of particular note is the effort made to improve dynamic resource allocation (DRA).In terms of security, there are 22 changes spanning admission control configurations, certificate handling, and more.Let's dig in!

## Kubeflow Community Distribution 26.03.1 Release Announcement

DevFeed: [Kubeflow Community Distribution 26.03.1 Release Announcement](<https://devfeed.tech/articles/kubeflow-community-distribution-26-03-1-release-announcement-17609.md>)

Original publisher: [Read original article](<https://blog.kubeflow.org/kubeflow-26.03-release/>)

Author: Kubeflow 26.03 Release Team

Published: 2026-04-11T05:00:00Z

Content type: release

Language: en

Sources: [Kubeflow](<https://devfeed.tech/sources/kubeflow.md>)

Topics: [releases](<https://devfeed.tech/topics/releases.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [MinIO](<https://devfeed.tech/topics/minio.md>), [istio](<https://devfeed.tech/topics/istio.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [ci](<https://devfeed.tech/tags/ci.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [minio](<https://devfeed.tech/tags/minio.md>), [network](<https://devfeed.tech/tags/network.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [release](<https://devfeed.tech/tags/release.md>), [storage](<https://devfeed.tech/tags/storage.md>), [ui](<https://devfeed.tech/tags/ui.md>), [updates](<https://devfeed.tech/tags/updates.md>), [versioning](<https://devfeed.tech/tags/versioning.md>)

### AI overview

The Kubeflow Community Distribution 26.03.1 release introduces calendar-based versioning and updates components including Kubernetes, Kubeflow Pipelines, KServe, Trainer, notebooks, the dashboard, Istio, and related dependencies. It also adds native OIDC support, conditional and parallel Local Runner control flows, SeaweedFS storage support, and completes MinIO deprecation.

### Source excerpt

The release versioning is now calendar-based (Year.Month.Patch). Around two base releases are planned per year with optional patch releases. The best-effort only community support is roughly 6 months and there is commercial support available from multiple vendors. Please update regularly as explained in our upgrading and extending section to benefit also from security and performance improvements. Release details: 26.03 and 26.03.1.

## Istio is Migrating Container Registries

DevFeed: [Istio is Migrating Container Registries](<https://devfeed.tech/articles/istio-is-migrating-container-registries-48816.md>)

Original publisher: [Read original article](<https://istio.io/latest/blog/2026/retirement-of-gcr.io/>)

Author: Steven Jin (Microsoft), John Howard (Solo.io)

Published: 2026-03-23T00:00:00Z

Content type: article

Language: en

Sources: [Istio](<https://devfeed.tech/sources/istio-blog.md>)

Topics: [istio](<https://devfeed.tech/topics/istio.md>), [migration](<https://devfeed.tech/topics/migration.md>), [container](<https://devfeed.tech/topics/container.md>), [Helm charts](<https://devfeed.tech/topics/helm-charts.md>), [Google Cloud Platform (GCP)](<https://devfeed.tech/topics/google-cloud.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [container](<https://devfeed.tech/tags/container.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [docker-hub](<https://devfeed.tech/tags/docker-hub.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [helm](<https://devfeed.tech/tags/helm.md>), [helm-charts](<https://devfeed.tech/tags/helm-charts.md>), [istio](<https://devfeed.tech/tags/istio.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [migration](<https://devfeed.tech/tags/migration.md>), [services](<https://devfeed.tech/tags/services.md>)

### AI overview

Istio is moving its container images from gcr.io/istio-release as part of a broader migration away from Google Cloud. The post explains how to identify affected clusters and update istioctl, Helm, and private-registry configurations to use the new registry.istio.io location before the old registry is retired on January 1, 2027.

### Source excerpt

The information in this post has been updated. See An Update on Our Container Registry Migration for the latest guidance. Due to changes in Istio's funding model, Istio images will no longer be available at gcr.io/istio-release starting January 1st, 2027. That is, clusters that reference images hosted on gcr.io/istio-release might fail to create new pods in 2027. In fact, we are fully migrating all Istio artifacts out of Google Cloud, including Helm charts. Future communications will cover the migration of Helm charts and other artifacts. This post will focus on what you can do today in response to the 2027 container registry migration. Am I affected? By default, Istio installations use Docker Hub (docker.io/istio) as their container registry, but many users choose to use the gcr.io/istio-release mirror. You can check whether you are using the mirror using the following command. $ kubectl get pods --all-namespaces -o json \ | jq -r '.items[] | select(.spec.containers[].image | startswith("gcr.io/istio-release")) | "\(.metadata.namespace)/\(.metadata.name)"' The above command will list all the pods that use images hosted on gcr.io/istio-release. If there are any such pods, you will likely need to migrate. Even if you are using Docker Hub as your registry, we suggest that you migrate to registry.istio.io in case Istio images are no longer available on Docker Hub in the future. See below for more details. What to do today Although we plan to keep images available on gcr.io/istio-release until late 2026, we have set up registry.istio.io as the new home for Istio images. Please migrate to using registry.istio.io as soon as possible. Using istioctl If you install Istio using istioctl, you can update your IstioOperator configuration as follows: # istiooperator.yaml apiVersion: install.istio.io/v1alpha1 kind: IstioOperator spec: # ... hub: registry.istio.io/release # Everything else can stay the same unless you reference `gcr.io/istio-release` images elsewhere and install I

## Using Mitmproxy to Observe kubectl Traffic

DevFeed: [Using Mitmproxy to Observe kubectl Traffic](<https://devfeed.tech/articles/using-mitmproxy-to-observe-kubectl-traffic-10924.md>)

Original publisher: [Read original article](<https://blog.scottlowe.org/2026/03/04/using-mitmproxy-to-observe-kubectl-traffic/>)

Author: Scott Lowe

Published: 2026-03-04T22:30:00Z

Content type: tutorial

Language: en

Sources: [Scott's Weblog](<https://devfeed.tech/sources/scott-s-weblog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Ubuntu](<https://devfeed.tech/topics/ubuntu.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Network](<https://devfeed.tech/topics/network.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [apt](<https://devfeed.tech/tags/apt.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [cilium](<https://devfeed.tech/tags/cilium.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cni](<https://devfeed.tech/tags/cni.md>), [commands](<https://devfeed.tech/tags/commands.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cri-o](<https://devfeed.tech/tags/cri-o.md>), [devops](<https://devfeed.tech/tags/devops.md>), [docker](<https://devfeed.tech/tags/docker.md>), [go](<https://devfeed.tech/tags/go.md>), [iac](<https://devfeed.tech/tags/iac.md>), [k8s](<https://devfeed.tech/tags/k8s.md>), [kubectl](<https://devfeed.tech/tags/kubectl.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [linux](<https://devfeed.tech/tags/linux.md>), [macos](<https://devfeed.tech/tags/macos.md>), [networking](<https://devfeed.tech/tags/networking.md>), [oci](<https://devfeed.tech/tags/oci.md>), [security](<https://devfeed.tech/tags/security.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [ubuntu](<https://devfeed.tech/tags/ubuntu.md>)

### AI overview

This tutorial explains how to use mitmproxy to observe traffic between kubectl and the Kubernetes API Server. It describes the tested Linux and Ubuntu environment, notes that the commands should work similarly on macOS, and discusses extracting client certificates from a Kubeconfig file for certificate-based authentication.

### Source excerpt

When I first started learning Kubernetes, I had the idea that observing the network traffic between a client system using kubectl and the Kubernetes API Server would be a useful thing to do. The source of the idea is unclear; I am unsure why I thought this would be useful as a learning tool. Regardless, I continued on with learning Kubernetes and never really pursued this idea--until this week. I found it can be a useful troubleshooting technique, but I will leave it up to you to determine if it is a useful learning technique. In this post, I will show you how to observe kubectl traffic using mitmproxy. This technique is inspired by/informed by Ahmet Alp Balkan's similarly-named blog post from 2019. Unfortunately, I found the instructions there to be incomplete (most likely just due to the passage of time and continued evolution of the tools involved). I used the following tools and environments in my testing: The tests were conducted on a Linux system running Ubuntu 24.04.4. The commands should work similarly on macOS. Mitmproxy was installed from the Ubuntu repositories using apt. kubectl version 1.33.3 was used to communicate to a self-managed cluster on AWS (in other words, not Amazon EKS) running Kubernetes 1.32.9. The cluster was bootstrapped using kubeadm. I wouldn't expect any major/significant differences with other versions of kubectl or Kubernetes. I was using a client certificate to authenticate to Kubernetes. It's unclear to me how this might work--if it works at all--with alternate authentication mechanisms. Prepare Client Certificates Before you can start mitmproxy, you'll first need to extract the client certificates from the Kubeconfig file. A couple of ways exist to do this; a blog post of mine from 2022 contains what I believe is the easiest way. The method involves yq (to extract information from the Kubeconfig) and base64 (to decode the client certificate and client key). Refer to the linked blog post for full details. First, extract the client cer

[Next page](<https://devfeed.tech/topics/kubectl.md?cursor=WyIyMDI2LTAzLTA0VDIyOjMwOjAwKzAwOjAwIiwgImZiYTkwYjRkLTY3MjItNDNhZS1iY2UwLTM5OTBkNTc4YzEyMiJd>)