Rolling updates are one way to release. Two others are built from the same pieces.
Blue/green runs the new version as a second complete Deployment and switches all traffic at once by changing the Service's selector, for example from version=blue to version=green. Switching back is the same change in reverse, so keep the old color running until the new one has proved itself.
A canary runs a few Pods of the new version beside the stable ones, sharing the labels the Service selects, so it receives roughly its share of Pods' worth of requests. Promote it by moving the stable Deployment to the new version and then removing the canary; for exact percentages, use Gateway API weights.
Releases often meet maintenance. A PodDisruptionBudget says how many Pods of a set must stay available (minAvailable) or may be missing (maxUnavailable) during voluntary disruptions such as drains.
A blue/green switch and a disruption budget.