CDK Environment Manager, environment definition
ti&m CDK Environment Manager environment definition file
| Type | object |
|---|---|
| File match |
**/environment-definition.json
**/environment-definition.yaml
**/environment-definition.yml
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/cdk-environment-manager-environment-definition/latest.json |
| Source | https://www.schemastore.org/ti8m-cdk-environment-definition.json |
Validate with Lintel
npx @lintel/lintel check
Definition of an application environment
Properties
the name of the application-(component) defined by this environment
configuration sets, which can be referenced from the service definitions
list of services which are part of this environment
Definitions
List of environment variables set in the Container/Pod
The entrypoint that is used to start the image (Only works with docker-compose and OpenShift
4 nested properties
(optional) the initial delay to wait before starting to probe in seconds
(optional) the time in seconds to wait for an http response for each call to the probe endpoint
(optional) the number of times the probe is allowed to fail the health check before performing its duty (e.g., recreating a pod or marking a pod as unavailable)
(optional) the number of times the probe has to pass the health check before performing its duty (e.g., marking a pod as available)
4 nested properties
(optional) the initial delay to wait before starting to probe in seconds
(optional) the time in seconds to wait for an http response for each call to the probe endpoint
(optional) the number of times the probe is allowed to fail the health check before performing its duty (e.g., recreating a pod or marking a pod as unavailable)
(optional) the number of times the probe has to pass the health check before performing its duty (e.g., marking a pod as available)
4 nested properties
(optional) the initial delay to wait before starting to probe in seconds
(optional) the time in seconds to wait for an http response for each call to the probe endpoint
(optional) the number of times the probe is allowed to fail the health check before performing its duty (e.g., recreating a pod or marking a pod as unavailable)
(optional) the number of times the probe has to pass the health check before performing its duty (e.g., marking a pod as available)
How to roll out changed versions of the service (Recreate or Rolling)
2 nested properties
5 nested properties
Number of seconds to wait between pod updates
Number of seconds to wait between evaluations of the deployment status
Time to wait for a successful scale-up before rolling back to the previous deployment
Maximum temporary excess number of pods above the desired number of replicas
Maximum temporarily lacking pods compared to the desired number of replicas
true, if this service needs a database schema to persist information.
Image pull policy for openshift. Default: IfNotPresent
The service account to use for Openshift.
The name of the service account to use for Openshift.
Number of desired instances.
2 nested properties
2 nested properties
The number of cores, can be specified as integer cores, or in milli-cores (eg: '100m')
The amount of main memory in either of M,G (base 10) or Mi, Gi (base 2). (eg: '3Gi')
2 nested properties
The number of cores, can be specified as integer cores, or in milli-cores (eg: '100m')
The amount of main memory in either of M,G (base 10) or Mi, Gi (base 2). (eg: '3Gi')
2 nested properties
2 nested properties
The number of cores, can be specified as integer cores, or in milli-cores (eg: '100m')
The amount of main memory in either of M,G (base 10) or Mi, Gi (base 2). (eg: '3Gi')
2 nested properties
The number of cores, can be specified as integer cores, or in milli-cores (eg: '100m')
The amount of main memory in either of M,G (base 10) or Mi, Gi (base 2). (eg: '3Gi')
2 nested properties
nodeSelector key
nodeSelector value
Tolerations section for Openshift
4 nested properties
podAntiAffinity key
podAntiAffinity operator
podAntiAffinity values
podAntiAffinity topologyKey
marks this service as 'network load-balanced'. On AWS this is a simple alternative to setting up a router and ingresses, which is the preferred method.
list of configuration files to be mapped into the service-container
list of secret files to be mounted in the service-container
Custom data object which will be passed as is into the render context
(K8s/OpenShift only) Indicates whether a service account token should be mounted
(K8s/OpenShift only) Indicates whether information about services should be injected into pod's environment variables, matching the syntax of Docker links
(K8s/OpenShift only) The number of old ReplicationControllers to retain to allow for rollbacks
(optional) the initial delay to wait before starting to probe in seconds
(optional) the time in seconds to wait for an http response for each call to the probe endpoint
(optional) the number of times the probe is allowed to fail the health check before performing its duty (e.g., recreating a pod or marking a pod as unavailable)
(optional) the number of times the probe has to pass the health check before performing its duty (e.g., marking a pod as available)
2 nested properties
The number of cores, can be specified as integer cores, or in milli-cores (eg: '100m')
The amount of main memory in either of M,G (base 10) or Mi, Gi (base 2). (eg: '3Gi')
2 nested properties
The number of cores, can be specified as integer cores, or in milli-cores (eg: '100m')
The amount of main memory in either of M,G (base 10) or Mi, Gi (base 2). (eg: '3Gi')
nodeSelector key
nodeSelector value
podAntiAffinity key
podAntiAffinity operator
podAntiAffinity values
podAntiAffinity topologyKey
Toleration key. The key is any string, up to 253 characters. The key must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores.
Toleration operator. The operator is one of the following: Equal or Exists
Toleration value. The value is any string, up to 63 characters. The value must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores.
Toleration effect. The effect is one of the following: NoSchedule, PreferNoSchedule or NoExecute
The number of cores, can be specified as integer cores, or in milli-cores (eg: '100m')
The amount of main memory in either of M,G (base 10) or Mi, Gi (base 2). (eg: '3Gi')
list of configuration files to be mapped into the service-container
list of secret files to be mounted in the service-container
list of volumes needed by this service, may result in persistent volume-claims or transient volumes
List of labels
defines, which endpoints, if any, to expose to the outside of the cluster
list of paths (path-beginnings) to be routed to this service
The host to be used for this exposure, the global cluster host is the default.
the internal port of the service that exposes the path
TLS termination on OpenShift