Kondense is an automated memory sizing tool. It runs as a sidecar in kubernetes pods.
Kondense uses memory pressure to apply just the right amount of memory on a container to page out the unused memory while not getting out-of-memory killed.
Allocated memory is not a good proxy for required memory. Many libraries used during startup are loaded into memory only to be never touched again afterwards.
- The Kubernetes cluster must run on Linux.
- Kubernetes version >= 1.27.
- Containerd version >= 1.6.9.
- Kubernetes should have the feature gate
InPlacePodVerticalScalingenabled.
- Containers should have the binary
cat. - Containers should include the linux kernel version >= 4.20. Ensure the file
/sys/fs/cgroup/memory.pressureexists in the container to verify it.
Try the example on minikube:
minikube start --kubernetes-version=v1.29.2 --feature-gates=InPlacePodVerticalScaling=true
kubectl apply -f https://raw.githubusercontent.com/unagex/kondense/main/example/nginx.yamlLet's say we have a pod running nginx that we want to Kondense:
apiVersion: v1
kind: Pod
metadata:
name: kondense-test
spec:
serviceAccountName: nginx-user
containers:
- name: nginx
image: nginx:latest
resources:
limits:
cpu: 0.1
memory: 100MAdd Kondense as a sidecar:
apiVersion: v1
kind: Pod
metadata:
name: kondense-test
spec:
serviceAccountName: nginx-user
containers:
- name: nginx
image: nginx:latest
resources:
limits:
cpu: 0.1
memory: 100M
- name: kondense
image: kondense/kondense:1.0.1
resources:
limits:
cpu: 0.3
memory: 50MNotes:
- The pod should have a QoS of
Guaranteed. In other words, we need to add resources limits for each containers. - The service account
nginx-usershould have the following rules:
rules:
- apiGroups: [""]
resources: ["pods"]
verbs: ["get", "list", "watch", "patch"]
- apiGroups: [""]
resources: ["pods/exec"]
verbs: ["create"]After adding the kondense container, the nginx container memory will be updated dynamically without any container restart.
Kondense is configurable via environment variables in the kondense container.
...
- name: kondense
image: kondense/kondense:1.0.1
resources:
limits:
cpu: 0.3
memory: 50M
env:
- name: <CONTAINER NAME>_MEMORY_INTERVAL
value: "5"If we have a container named nginx in our pod, the variable name should be NGINX_MEMORY_INTERVAL.
| Name | Default value | Description |
|---|---|---|
| EXCLUDE | "" | Comma separated list of containers to not kondense. |
| <CONTAINER NAME>_MEMORY_MIN | 50M | Minimum memory of the container. Kondense will never resize below that limit. |
| <CONTAINER NAME>_MEMORY_MAX | 100G | Maximum memory of the container. Kondense will never resize above that limit. |
| <CONTAINER NAME>_MEMORY_TARGET_PRESSURE | 10000 | Target memory pressure in microseconds. Kondense will take corrective actions to obtain it. |
| <CONTAINER NAME>_MEMORY_INTERVAL | 10 | Kondense targets cumulative memory delays over the sampling period of this interval in seconds. |
| <CONTAINER NAME>_MEMORY_INTERVAL | 10 | Kondense targets cumulative memory delays over the sampling period of this interval in seconds. |
| <CONTAINER NAME>_MEMORY_MAX_INC | 0.5 | Maximum memory increase for one correction. e.g. 0.5 is a 50% increase. |
| <CONTAINER NAME>_MEMORY_MAX_DEC | 0.02 | Maximum memory decrease for one correction. e.g. 0.02 is a 2% decrease. |
| <CONTAINER NAME>_MEMORY_COEFF_INC | 20 | Kondense back off exponentially as we deviate from the target pressure. This coeff defines how sensitive we are to fluctations: when the coeff is 20, the curve reaches the adjustment limit when pressure is 20 times the target pressure. |
| <CONTAINER NAME>_MEMORY_COEFF_DEC | 10 | Kondense back off exponentially as we deviate from the target pressure. This coeff defines how sensitive we are to fluctations. The adjustment becomes exponentially more aggressive as observed pressure falls below the target pressure and reaches the adjustment limit. |
- Kondense is based on Facebook senpai
- Kondense is active on himself by default
