About fuel-wlightning

For a CronJob when I first apply my manifest, GKE Autopilot mutates the result and applies the minimum requirements properly. However when I go to kubect apply again, it fails with a validation failure.Is there a way to work around this?The manifest ...

Looks like GKE warden mutates it to:resources: limits: cpu: 250m ephemeral-storage: 1Gi memory: 1Gi requests: cpu: 250m ephemeral-storage: 1Gi memory: 1GiHere is what the original cronjob.yaml turns into with original apply and the same command run a...

So both including an additional limits section and dropping the requests in favor of limits both fail in different ways.There are two failing scenarios below, the first one has both limits and requests, and the second one just has limits.Both Limits ...

Interesting. What makes the CronJob different from a Deployment?If I apply a deployment with the same pod spec resources once to create and a second time to patch, it just amends the second request to minimums with the expected warnings.Execution Log...

Sorry! Here is the output of the two kubectl apply commands with the second failing. (with my e-mail redacted):$ kubectl apply -f cronjob.ymlnamespace/gke-val-fail createdWarning: autopilot-default-resources-mutator:Autopilot updated CronJob gke-val-...

My Stats

wilitow's Bio

Badges fuel-wlightning Earned

Recent Activity

kubectl apply of with low resource requests in CronJob on GKE Autopilot fails on second apply.

Re: kubectl apply of with low resource requests in CronJob on GKE Autopilot fails on second apply.

Re: kubectl apply of with low resource requests in CronJob on GKE Autopilot fails on second apply.

Re: kubectl apply of with low resource requests in CronJob on GKE Autopilot fails on second apply.

Re: kubectl apply of with low resource requests in CronJob on GKE Autopilot fails on second apply.