Edit Kubernetes Deployment With No Manual File Changes

A Kubernetes Deployment is a YAML configuration defining a pod or group of pods in a cluster. It enables easy scaling, rolling updates, and fault tolerance. By modifying parameters like replicas or image tags, you can efficiently manage containerized applications, ensuring smooth operation and resource optimization. Let us delve to understanding how to edit a Kubernetes deployment with no manual changes in configuration files.

1. What Is Kubernetes?

Kubernetes, often abbreviated as K8s, is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications. It was originally developed by engineers at Google and is now maintained by the Cloud Native Computing Foundation (CNCF), a part of the Linux Foundation.

Containers are a lightweight and portable way to package and run applications and their dependencies, ensuring consistent behavior across different environments. Kubernetes provides a framework for managing these containers, allowing you to abstract away the underlying infrastructure and focus on defining how your applications should be deployed and managed.

2. Kubernetes Operations

Let us explore the various Kubernetes Operations.

2.1 Using the Set Operation in Kubernetes Deployments

The set operation in Kubernetes facilitates dynamic updates to resources, such as deployments, by modifying specific fields using a simple command. Using the kubectl set operation, you can dynamically edit a Kubernetes Deployment without directly modifying its YAML configuration file. This operation offers a convenient and efficient way to update deployment settings such as replicas, image tags, or environment variables. It ensures seamless management of containerized applications while maintaining cluster stability and reliability.

Here’s an example of how you can use kubectl set to update the number of replicas in a Deployment:

kubectl set replicas deployment/my-deployment-name --replicas=3

This command modifies the number of replicas for the specified deployment (my-deployment-name) to 3, effectively scaling the application horizontally.

2.1.1 Benefits

  • Straightforward syntax for updating resource fields
  • Efficient for scaling, modifying replicas, or updating image tags

2.2 Using the Patch Operation in Kubernetes Deployments

The patch operation in Kubernetes allows for making targeted updates to specific fields of an existing resource without replacing the entire resource configuration. This is particularly useful for making targeted updates to complex resources like Deployments. Here’s how you can use the patch operation to modify a Kubernetes Deployment:

kubectl patch deployment my-deployment-name -p '{"spec":{"replicas":3}}'

In this example, we’re using the patch operation to set the number of replicas for the Deployment named my-deployment-name to 3. The -p flag is used to specify the patch in JSON format.

Additionally, you can use the patch operation to update other fields such as image tags, environment variables, or labels. The patch operation gives you fine-grained control over your Kubernetes resources, allowing for efficient updates while minimizing disruption to your applications.

2.2.1 Benefits

  • Granular control over resource updates
  • Minimizes disruption to applications

2.3 Using the Edit Operation in Kubernetes Deployments

The edit operation in Kubernetes provides a convenient way to modify resources directly from the command line without needing to manually edit YAML files. Here’s how you can use the edit operation to modify a Kubernetes Deployment:

kubectl edit deployment my-deployment-name

Running this command will open the Deployment configuration in your default text editor, allowing you to make changes to the YAML directly. Once you save and close the editor, Kubernetes will apply the changes to the Deployment.

The edit operation provides a simple and intuitive way to make quick adjustments to your resources. However, it’s important to use caution when editing resources directly, as incorrect changes could lead to unexpected behavior or downtime. Additionally, the edit operation is suitable for making one-off changes or troubleshooting, but for more controlled updates and management, it’s recommended to use other methods like applying patches or using declarative configurations.

2.3.1 Benefits

  • Convenient for making quick adjustments or troubleshooting
  • Immediate feedback and visibility of changes

By leveraging these Kubernetes operations, Kubernetes administrators and developers can streamline the process of making ad-hoc changes to Deployments and other resources, improving efficiency and productivity in managing Kubernetes clusters.

3. Conclusion

In conclusion, Kubernetes offers several powerful operations for managing resources within your cluster efficiently. The patch operation allows for targeted updates to specific fields of existing resources, providing granular control while minimizing disruption to applications. Similarly, the set operation provides a straightforward method for dynamically updating resource fields such as replicas, image tags, or environment variables, streamlining the management process.

Additionally, the edit operation offers an interactive way to modify resource configurations directly from the command line, providing immediate feedback and visibility of changes.

By understanding and leveraging these operations – patch, set, and edit – Kubernetes administrators and developers can efficiently manage resources, ensuring smooth operation and optimal resource utilization in their clusters. It’s essential to choose the appropriate operation based on the specific requirements of your deployment, balancing the need for precision, efficiency, and control.


An experience full-stack engineer well versed with Core Java, Spring/Springboot, MVC, Security, AOP, Frontend (Angular & React), and cloud technologies (such as AWS, GCP, Jenkins, Docker, K8).
Notify of

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Inline Feedbacks
View all comments
Back to top button