Rolling upgrades and canary deployments for live NFs

Rolling Updates for Telecom NFs

Rolling updates are the default Kubernetes deployment strategy, replacing old pod instances with new ones incrementally. The maxUnavailable parameter controls how many pods can be down simultaneously, while maxSurge controls how many extra pods can be created above the desired count. For telecom NFs, setting maxUnavailable to zero ensures no capacity loss during upgrades, while maxSurge of twenty-five percent adds temporary extra capacity. Combined with readiness probes that only pass after the new NF version completes initialization and NRF registration, rolling updates provide zero-downtime…