Unable to manually configure maxSurge for Knative Serving's Service corresponding Deployment

[wenzhaojie]

Ask your question here:

I found that I am unable to manually configure maxSurge for Knative Serving's Service. I used the kubectl edit deployment command to add {"spec":{"strategy":{"rollingUpdate":{"maxSurge":"100%","maxUnavailable":0}}}}, but the changes did not take effect.

What could be the reason for this? How can I resolve this?

Thank you!

[skonto]

Hi @wenzhaojie , Knative Serving defines an API to create enhanced services on K8s. This means that it has a controller logic that creates at the end of the day the deployment on behalf of the user (it creates a number of other resources too), with some specific defaults (there is an issue about that btw) and it will reconcile the deployment accordingly. The autoscaler mechanism manages deployment changes (eg. replicas during upgrades) on behalf of the user, based on statistics collected from the queue proxy side-car (injected along with user-containers), see more the discussion here, where maxSurge 25% (default) and why it is used.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.