You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Earlier this week I’ve been migrating crossplane resources from an old cluster to a new one. During this process we needed to reconcile about 400 terraform workspaces (half of them with remote state).
After adjusting TF provider pod resources (requests.memory: 2G, limits.memory: 2G, requests.cpu: 1000m, limits.cpu: 5000m) it was being evicted every 20 minutes with the following error:
Warning Evicted 117s kubelet The node was low on resource: ephemeral-storage. Threshold quantity: 7859887835, available: 7344104Ki. Container package-runtime was using 51370076Ki, request is 0, has larger consumption of ephemeral-storage. Normal Killing 117s kubelet Stopping container package-runtime Warning ExceededGracePeriod 107s kubelet Container runtime did not kill the pod within specified grace period.
The workaround was adjusting pod resources.request.ephemeral-storage to 60Gi and this increased time to eviction.
TF provider (v0.11.0) was configured to disable plugin cache because it had --max-reconcile-rate=10.
What environment did it happen in?
Crossplane Version: 1.14.3-up.1
Provider Version: 0.11.0
Kubernetes Version: 1.26.10
Kubernetes Distribution: AKS
The text was updated successfully, but these errors were encountered:
What happened?
Earlier this week I’ve been migrating crossplane resources from an old cluster to a new one. During this process we needed to reconcile about 400 terraform workspaces (half of them with remote state).
After adjusting TF provider pod resources (requests.memory: 2G, limits.memory: 2G, requests.cpu: 1000m, limits.cpu: 5000m) it was being evicted every 20 minutes with the following error:
The workaround was adjusting pod resources.request.ephemeral-storage to 60Gi and this increased time to eviction.
TF provider (v0.11.0) was configured to disable plugin cache because it had --max-reconcile-rate=10.
What environment did it happen in?
The text was updated successfully, but these errors were encountered: