Deployment
This chart creates a deployment that runs multiple replicas of your application and automatically replaces any instances that fail or become unresponsive. It does not support Blue/Green and Canary deployments.
This is the default deployment chart. You can select Deployment
chart when you want to use only basic use cases which contain the following:
Create a Deployment to rollout a ReplicaSet. The ReplicaSet creates Pods in the background. Check the status of the rollout to see if it succeeds or not.
Declare the new state of the Pods. A new ReplicaSet is created and the Deployment manages moving the Pods from the old ReplicaSet to the new one at a controlled rate. Each new ReplicaSet updates the revision of the Deployment.
Rollback to an earlier Deployment revision if the current state of the Deployment is not stable. Each rollback updates the revision of the Deployment.
Scale up the Deployment to facilitate more load.
Use the status of the Deployment as an indicator that a rollout has stuck.
Clean up older ReplicaSets that you do not need anymore.
You can define application behavior by providing information in the following sections:
Key | Descriptions |
---|---|
| Select the Chart Version using which you want to deploy the application. Refer Chart Version section for more detail. |
| You can select the basic deployment configuration for your application on the Basic GUI section instead of configuring the YAML file. Refer Basic Configuration section for more detail. |
| If you want to do additional configurations, then click Advanced (YAML) for modifications. Refer Advanced (YAML) section for more detail. |
| You can enable |
Super-admins can lock keys in deployment template to prevent non-super-admins from modifying those locked keys. Refer Lock Deployment Configuration to know more.
1. Yaml File
Container Ports
This defines ports on which application services will be exposed to other services
Key | Description |
---|---|
| envoy port for the container |
| the duration of time that a connection is idle before the connection is terminated |
| name of the port |
| port for the container |
| port of the corresponding kubernetes service |
| nodeport of the corresponding kubernetes service |
| Used for high performance protocols like grpc where timeout needs to be disabled |
| Envoy container can accept HTTP2 requests |
EnvVariables
To set environment variables for the containers that run in the Pod.
EnvVariablesFromFieldPath
To set environment variables for the containers and fetching their values from pod-level fields.
Liveness Probe
If this check fails, kubernetes restarts the pod. This should return error code in case of non-recoverable error.
Key | Description |
---|---|
| It define the path where the liveness needs to be checked |
| It defines the time to wait before a given container is checked for liveliness |
| It defines the time to check a given container for liveness |
| It defines the number of successes required before a given container is said to fulfill the liveness probe |
| It defines the time for checking timeout |
| It defines the maximum number of failures that are acceptable before a given container is not considered as live |
| Custom headers to set in the request. HTTP allows repeated headers, you can override the default headers by defining .httpHeaders for the probe. |
| Scheme to use for connecting to the host (HTTP or HTTPS). Defaults to HTTP. |
| The kubelet will attempt to open a socket to your container on the specified port. If it can establish a connection, the container is considered healthy. |
MaxUnavailable
The maximum number of pods that can be unavailable during the update process. The value of "MaxUnavailable: " can be an absolute number or percentage of the replicas count. The default value of "MaxUnavailable: " is 25%.
MaxSurge
The maximum number of pods that can be created over the desired number of pods. For "MaxSurge: " also, the value can be an absolute number or percentage of the replicas count. The default value of "MaxSurge: " is 25%.
Min Ready Seconds
This specifies the minimum number of seconds for which a newly created Pod should be ready without any of its containers crashing, for it to be considered available. This defaults to 0 (the Pod will be considered available as soon as it is ready).
Readiness Probe
If this check fails, kubernetes stops sending traffic to the application. This should return error code in case of errors which can be recovered from if traffic is stopped.
Key | Description |
---|---|
| It define the path where the readiness needs to be checked |
| It defines the time to wait before a given container is checked for readiness |
| It defines the time to check a given container for readiness |
| It defines the number of successes required before a given container is said to fulfill the readiness probe |
| It defines the time for checking timeout |
| It defines the maximum number of failures that are acceptable before a given container is not considered as ready |
| Custom headers to set in the request. HTTP allows repeated headers, you can override the default headers by defining .httpHeaders for the probe. |
| Scheme to use for connecting to the host (HTTP or HTTPS). Defaults to HTTP. |
| The kubelet will attempt to open a socket to your container on the specified port. If it can establish a connection, the container is considered healthy. |
Pod Disruption Budget
You can create PodDisruptionBudget
for each application. A PDB limits the number of pods of a replicated application that are down simultaneously from voluntary disruptions. For example, an application would like to ensure the number of replicas running is never brought below the certain number.
or
You can specify either maxUnavailable
or minAvailable
in a PodDisruptionBudget and it can be expressed as integers or as a percentage.
Key | Description |
---|---|
| Evictions are allowed as long as they leave behind 1 or more healthy pods of the total number of desired replicas. |
| Evictions are allowed as long as at most 1 unhealthy replica among the total number of desired replicas. |
Ambassador Mappings
You can create ambassador mappings to access your applications from outside the cluster. At its core a Mapping resource maps a resource to a service.
Key | Description |
---|---|
| Set true to enable ambassador mapping else set false |
| used to specify id for specific ambassador mappings controller |
| used to specify cors policy to access host for this mapping |
| used to specify weight for canary ambassador mappings |
| used to specify hostname for ambassador mapping |
| used to specify path for ambassador mapping |
| used to provide custom labels for ambassador mapping |
| used to specify retry policy for ambassador mapping |
| Provide cors headers on flagger resource |
| used to specify whether to redirect the path of this mapping and where |
| used to create or define ambassador TLSContext resource |
| used to provide extra spec values which not present in deployment template for ambassador resource |
Autoscaling
This is connected to HPA and controls scaling up and down in response to request load.
Key | Description |
---|---|
| Set true to enable autoscaling else set false |
| Minimum number of replicas allowed for scaling |
| Maximum number of replicas allowed for scaling |
| The target CPU utilization that is expected for a container |
| The target memory utilization that is expected for a container |
| Used to give external metrics for autoscaling |
Flagger
You can use flagger for canary releases with deployment objects. It supports flexible traffic routing with istio service mesh as well.
Key | Description |
---|---|
| Set true to enable canary releases using flagger else set false |
| To provide multiple istio gateways for flagger |
| Add multiple hosts for istio service mesh with flagger |
| Define how the canary release should progress and at what interval |
| Annotation to add on flagger resource |
| Labels to add on flagger resource |
| Protocol to use for canary |
| Provide cors headers on flagger resource |
| Set to true if you want to create istio gateway as well with flagger |
| Add headers if any |
| Enable load testing for your canary release |
Fullname Override
fullnameOverride
replaces the release fullname created by default by devtron, which is used to construct Kubernetes object names. By default, devtron uses {app-name}-{environment-name} as release fullname.
Image
Image is used to access images in kubernetes, pullpolicy is used to define the instances calling the image, here the image is pulled when the image is not present,it can also be set as "Always".
imagePullSecrets
imagePullSecrets
contains the docker credentials that are used for accessing a registry.
regcred is the secret that contains the docker credentials that are used for accessing a registry. Devtron will not create this secret automatically, you'll have to create this secret using dt-secrets helm chart in the App store or create one using kubectl. You can follow this documentation Pull an Image from a Private Registry https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ .
serviceAccount
Key | Description |
---|---|
| Determines whether to create a ServiceAccount for pods or not. If set to |
| Specifies the name of the ServiceAccount to use. |
| Specify annotations for the ServiceAccount. |
HostAliases
the hostAliases field is used in a Pod specification to associate additional hostnames with the Pod's IP address. This can be helpful in scenarios where you need to resolve specific hostnames to the Pod's IP within the Pod itself.
Ingress
This allows public access to the url, please ensure you are using right nginx annotation for nginx class, its default value is nginx
Legacy deployment-template ingress format
Key | Description |
---|---|
| Enable or disable ingress |
| To configure some options depending on the Ingress controller |
| Path name |
| Host name |
| It contains security details |
Ingress Internal
This allows private access to the url, please ensure you are using right nginx annotation for nginx class, its default value is nginx
Key | Description |
---|---|
| Enable or disable ingress |
| To configure some options depending on the Ingress controller |
| Path name |
| Host name |
| It contains security details |
Init Containers
Specialized containers that run before app containers in a Pod. Init containers can contain utilities or setup scripts not present in an app image. One can use base image inside initContainer by setting the reuseContainerImage flag to true
.
Pause For Seconds Before Switch Active
To wait for given period of time before switch active the container.
Resources
These define minimum and maximum RAM and CPU available to the application.
Resources are required to set CPU and memory usage.
Limits
Limits make sure a container never goes above a certain value. The container is only allowed to go up to the limit, and then it is restricted.
Requests
Requests are what the container is guaranteed to get.
Service
This defines annotations and the type of service, optionally can define name also.
Volumes
It is required when some values need to be read from or written to an external disk.
Volume Mounts
It is used to provide mounts to the volume.
Affinity and anti-affinity
Spec is used to define the desire state of the given container.
Node Affinity allows you to constrain which nodes your pod is eligible to schedule on, based on labels of the node.
Inter-pod affinity allow you to constrain which nodes your pod is eligible to be scheduled based on labels on pods.
Key
Key part of the label for node selection, this should be same as that on node. Please confirm with devops team.
Values
Value part of the label for node selection, this should be same as that on node. Please confirm with devops team.
Tolerations
Taints are the opposite, they allow a node to repel a set of pods.
A given pod can access the given node and avoid the given taint only if the given pod satisfies a given taint.
Taints and tolerations are a mechanism which work together that allows you to ensure that pods are not placed on inappropriate nodes. Taints are added to nodes, while tolerations are defined in the pod specification. When you taint a node, it will repel all the pods except those that have a toleration for that taint. A node can have one or many taints associated with it.
Arguments
This is used to give arguments to command.
Command
It contains the commands for the server.
Key | Description |
---|---|
| To enable or disable the command |
| It contains the commands |
Containers
Containers section can be used to run side-car containers along with your main container within same pod. Containers running within same pod can share volumes and IP Address and can address each other @localhost. We can use base image inside container by setting the reuseContainerImage flag to true
.
Container Lifecycle Hooks
Container lifecycle hooks are mechanisms that allow users to define custom actions to be performed at specific stages of a container's lifecycle i.e. PostStart or PreStop.
Key | Description |
---|---|
| containerSpec to define container lifecycle hooks configuration |
| Lifecycle hooks for the container |
| Set true to enable lifecycle hooks for the container else set false |
| The postStart hook is executed immediately after a container is created |
| Sends an HTTP GET request to a specific endpoint on the container |
| Specifies the host (example.com) to which the HTTP GET request will be sent |
| Specifies the path (/example) of the endpoint to which the HTTP GET request will be sent |
| Specifies the port (90) on the host where the HTTP GET request will be sent |
| The preStop hook is executed just before the container is stopped |
| Executes a specific command, such as pre-stop.sh, inside the cgroups and namespaces of the container |
| The command to be executed is sleep 10, which tells the container to sleep for 10 seconds before it is stopped |
Prometheus
It is a kubernetes monitoring tool and the name of the file to be monitored as monitoring in the given case. It describes the state of the Prometheus.
rawYaml
Accepts an array of Kubernetes objects. You can specify any kubernetes yaml here and it will be applied when your app gets deployed.
Grace Period
Kubernetes waits for the specified time called the termination grace period before terminating the pods. By default, this is 30 seconds. If your pod usually takes longer than 30 seconds to shut down gracefully, make sure you increase the GracePeriod
.
A Graceful termination in practice means that your application needs to handle the SIGTERM message and begin shutting down when it receives it. This means saving all data that needs to be saved, closing down network connections, finishing any work that is left, and other similar tasks.
There are many reasons why Kubernetes might terminate a perfectly healthy container. If you update your deployment with a rolling update, Kubernetes slowly terminates old pods while spinning up new ones. If you drain a node, Kubernetes terminates all pods on that node. If a node runs out of resources, Kubernetes terminates pods to free those resources. It’s important that your application handle termination gracefully so that there is minimal impact on the end user and the time-to-recovery is as fast as possible.
Server
It is used for providing server configurations.
Deployment
It gives the details for deployment.
Key | Description |
---|---|
| It is the image tag |
| It is the URL of the image |
Service Monitor
It gives the set of targets to be monitored.
Db Migration Config
It is used to configure database migration.
Istio
These Istio configurations collectively provide a comprehensive set of tools for controlling access, authenticating requests, enforcing security policies, and configuring traffic behavior within a microservices architecture. The specific settings you choose would depend on your security and traffic management requirements.
Key | Description |
---|---|
| Istio enablement. When |
| It allows you to define access control policies for service-to-service communication. |
| Determines whether to ALLOW or DENY the request based on the defined rules. |
| Authorization providers are external systems or mechanisms used to make access control decisions. |
| List of rules defining the authorization policy. Each rule can specify conditions and requirements for allowing or denying access. |
| It allows for the fine-tuning of traffic policies and load balancing for specific services. You can define subsets of a service and apply different traffic policies to each subset. |
| Specifies subsets within the service for routing and load balancing. |
| Policies related to connection pool size, outlier detection, and load balancing. |
| Allowing external traffic to enter the service mesh through the specified configurations. |
| The external domain through which traffic will be routed into the service mesh. |
| Traffic to and from the gateway should be encrypted using TLS. |
| Specifies the name of the Kubernetes secret that contains the TLS certificate and private key. The TLS certificate is used for securing the communication between clients and the Istio gateway. |
| It allows you to enforce mutual TLS and control the authentication between services. |
| Mutual TLS. Mutual TLS is a security protocol that requires both client and server, to authenticate each other using digital certificates for secure communication. |
| Mutual TLS mode, specifying how mutual TLS should be applied. Modes include STRICT, PERMISSIVE, and DISABLE. |
| Configures port-specific mTLS settings. Allows for fine-grained control over the application of mutual TLS on specific ports. |
| Configuration for selecting workloads to apply PeerAuthentication. |
| Defines rules for authenticating incoming requests. |
| Rules for validating JWTs (JSON Web Tokens). It defines how incoming JWTs should be validated for authentication purposes. |
| Specifies the conditions under which the RequestAuthentication rules should be applied. |
| Enables the definition of rules for how traffic should be routed to different services within the service mesh. |
| Specifies the gateways to which the rules defined in the VirtualService apply. |
| List of hosts (domains) to which this VirtualService is applied. |
| Configuration for HTTP routes within the VirtualService. It define routing rules based on HTTP attributes such as URI prefixes, headers, timeouts, and retry policies. |
KEDA Autoscaling
KEDA is a Kubernetes-based Event Driven Autoscaler. With KEDA, you can drive the scaling of any container in Kubernetes based on the number of events needing to be processed. KEDA can be installed into any Kubernetes cluster and can work alongside standard Kubernetes components like the Horizontal Pod Autoscaler(HPA).
Example for autosccaling with KEDA using Prometheus metrics is given below:
Example for autosccaling with KEDA based on kafka is given below :
NetworkPolicy
Kubernetes NetworkPolicies control pod communication by defining rules for incoming and outgoing traffic.
Key | Description |
---|---|
| Enable or disable NetworkPolicy. |
| Additional metadata or information associated with the NetworkPolicy. |
| Labels to apply to the NetworkPolicy. |
| Each NetworkPolicy includes a podSelector which selects the grouping of pods to which the policy applies. The example policy selects pods with the label "role=db". An empty podSelector selects all pods in the namespace. |
| Each NetworkPolicy includes a policyTypes list which may include either Ingress, Egress, or both. |
| Controls incoming traffic to pods. |
| Controls outgoing traffic from pods. |
Winter-Soldier
Winter Soldier can be used to
cleans up (delete) Kubernetes resources
reduce workload pods to 0
NOTE: After deploying this we can create the Hibernator object and provide the custom configuration by which workloads going to delete, sleep and many more. for more information check the main repo
Given below is template values you can give in winter-soldier:
Key | values | Description |
---|---|---|
|
| decide the enabling factor |
|
| specific api version |
|
| This specify the action need to perform. |
| eg:- | It use to specify the timeZone used. (It uses standard format. please refer this) |
| array of [ | It use to define time period/range on which the user need to perform the specified action. you can have multiple timeRanges.
These settings will take |
|
| These is mandatory field when the |
|
| These value will take a list of methods to select the resources on which we perform specified |
here is an example,
Above settings will take action on Sat
and Sun
from 00:00 to 23:59:59, and on Mon
-Fri
from 00:00 to 08:00 and 20:00 to 23:59:59. If action:sleep
then runs hibernate at timeFrom and unhibernate at timeTo
. If action: delete
then it will delete workloads at timeFrom
and timeTo
. Here the action:scale
thus it scale the number of resource replicas to targetReplicas: [1,1,1]
. Here each element of targetReplicas
array is mapped with the corresponding elements of array timeRangesWithZone/timeRanges
. Thus make sure the length of both array is equal, otherwise the cnages cannot be observed.
The above example will select the application objects which have been created 10 hours ago across all namespaces excluding application's namespace. Winter soldier exposes following functions to handle time, cpu and memory.
ParseTime - This function can be used to parse time. For eg to parse creationTimestamp use ParseTime({{metadata.creationTimestamp}}, '2006-01-02T15:04:05Z')
AddTime - This can be used to add time. For eg AddTime(ParseTime({{metadata.creationTimestamp}}, '2006-01-02T15:04:05Z'), '-10h') ll add 10h to the time. Use d for day, h for hour, m for minutes and s for seconds. Use negative number to get earlier time.
Now - This can be used to get current time.
CpuToNumber - This can be used to compare CPU. For eg any({{spec.containers.#.resources.requests}}, { MemoryToNumber(.memory) < MemoryToNumber('60Mi')}) will check if any resource.requests is less than 60Mi.
Security Context
A security context defines privilege and access control settings for a Pod or Container.
To add a security context for main container:
To add a security context on pod level:
Topology Spread Constraints
You can use topology spread constraints to control how Pods are spread across your cluster among failure-domains such as regions, zones, nodes, and other user-defined topology domains. This can help to achieve high availability as well as efficient resource utilization.
Deployment Metrics
It gives the realtime metrics of the deployed applications
Key | Description |
---|---|
| It shows how often this app is deployed to production |
| It shows how often the respective pipeline fails |
| It shows the average time taken to deliver a change to production |
| It shows the average time taken to fix a failed pipeline |
2. Show application metrics
If you want to see application metrics like different HTTP status codes metrics, application throughput, latency, response time. Enable the Application metrics from below the deployment template Save button. After enabling it, you should be able to see all metrics on App detail page. By default it remains disabled.
![](https://docs.devtron.ai/~gitbook/image?url=https%3A%2F%2Fdevtron-public-asset.s3.us-east-2.amazonaws.com%2Fimages%2Fcreating-application%2Fdeployment-template%2Fdeployment_application_metrics.jpg&width=768&dpr=4&quality=100&sign=227d3eb5&sv=1)
Once all the Deployment template configurations are done, click on Save
to save your deployment configuration. Now you are ready to create Workflow to do CI/CD.
Helm Chart Json Schema
Helm Chart json schema is used to validate the deployment template values.
Other Validations in Json Schema
The values of CPU and Memory in limits must be greater than or equal to in requests respectively. Similarly, In case of envoyproxy, the values of limits are greater than or equal to requests as mentioned below.
Last updated