Discovery global configuration
The Side Car Global Configuration, acts as central configuration, shared by all components using the side car container.
Components that have discovery.enabled or metrics.enabled will have the side car container added to each of their deployments by default.
global:
sidecar:
resources:
requests:
cpu: 0.1
memory: 128Mi
limits:
cpu: 0.1
memory: 128Mi
resources
key | type | description |
---|---|---|
resources |
object |
Parent object to define requests and limits |
Resource configuration allows global limits
and requests
to be set for each of the deployed side car containers.
Values are set per container, the sum of these resources is used to define Pod requests and limits, allowing the Kubernetes scheduler to attempt to place pod on a node with sufficient resources.
Resource Limits
When a process in the container tries to consume more than the allowed amount of memory, the system kernel terminates the process that attempted the allocation, with an out of memory (OOM) error.
resources.requests
key | type | description |
---|---|---|
requests |
object |
Requested resources for Pod container |
requests.memory |
string |
Requested container memory in bytes. You can express memory as a plain integer or as a fixed-point number. See here for more details |
requests.cpu |
string |
Requested container cpu in units of Kubernetes CPUs. |
Specifying a resource request
will have Kubernete's kube-scheduler to attempt to schedule your pod on a node that satisfies your request.
resources.limits
key | type | description |
---|---|---|
limits |
object |
Enforce resource limits on a Pod's container |
limits.memory |
string |
Enforced maximum memory in bytes. You can express memory as a plain integer or as a fixed-point number. See here for more details |
limits.cpu |
string |
Enforced cpu usage limit in units of Kubernetes CPUs. |
When a resource limit
has been set the container will be prevented from exceeding the resource usage. In the case of memory
this may lead to an OOM
error on the container.