Skip to content

Add documentation to provide instructions for no downtime upgrade using helm #4153

@vepatel

Description

@vepatel

Is your feature request related to a problem? Please describe.
When user is upgrading IC version from 3.0.2 to later ones, the helm upgrade process is doing a recreate for deployment/daemonset and service due to naming and label changes introduced in 3.1.0 causing a downtime for customer.

This should also cover moving from a 2.x such as 2.4.2

Describe the solution you'd like
Add step-by-step instructions on how to upgrade without having to recreate these resources and add the document o docs.nginx.com

Metadata

Metadata

Assignees

Labels

backlogPull requests/issues that are backlog itemsdocumentationPull requests/issues for documentation

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions