feat: Clarify NIC install & upgrade steps #816

ADubhlaoich · 2025-07-15T16:32:33Z

Proposed changes

This commit makes a number of changes to clarify what the precise steps are to install, upgrade and uninstall NGINX Ingress Controller

The Install document clarifies necessary steps
Uninstall steps have been moved to the bottom of the document
Upgrade instructions have been moved into their own document

The changes made focused on clarifying the critical path for one single user story, as lots of unnecessary contextual information was being provided, which was causing confusion.

With this commit, the general reading and execution flow for these deployment steps become more coherent. Similar changes may be made for Manifests documentation, if common steps are identified.

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩

This commit makes a number of changes to clarify what the precise steps are to install, upgrade and uninstall NGINX Ingress Controller - The Install document clarifies necessary steps - Uninstall steps have been moved to the bottom of the document - Upgrade instructions have been moved into their own document The changes made focused on clarifying the critical path for one single user story, as lots of unnecessary contextual information was being provided, which was causing confusion. With this commit, the general reading and execution flow for these deployment steps become more coherent. Similar changes may be made for Manifests documentation, if common steps are identified.

github-actions · 2025-07-15T16:35:38Z

✅ Deploy Preview will be available once build job completes!

Name	Link
😎 Deploy Preview	https://frontdoor-test-docs.nginx.com/previews/docs/816/

content/nic/installation/upgrade-version.md

pdabelf5 · 2025-07-18T14:55:49Z

content/nic/installation/installing-nic/installation-with-helm.md

+- Download the image using your NGINX Ingress Controller subscription certificate and key. View the [Get NGINX Ingress Controller from the F5 Registry]({{< ref "/nic/installation/nic-images/get-registry-image.md" >}}) topic.
+- The [Get the NGINX Ingress Controller image with JWT]({{< ref "/nic/installation/nic-images/get-image-using-jwt.md" >}}) topic describes how to use your subscription JWT token to get the image.


Only one of these is required, one or the other.

Yeah, this read like a mess to me.

I was trying to make the minimum amount of changes to pull the upgrade instructions out, but there's a larger series of things to fix here.

I'm pretty confident every document involving NGINX Plus includes the step to create the license secret, so even listing it here as a requisite might be redundant if you're following the instructions and the prerequisites linearly.

pdabelf5 · 2025-07-18T15:04:58Z

content/nic/installation/installing-nic/installation-with-helm.md

+- [Create a license Secret]({{< ref "/nic/installation/create-license-secret.md" >}}).
+- Download the image using your NGINX Ingress Controller subscription certificate and key. View the [Get NGINX Ingress Controller from the F5 Registry]({{< ref "/nic/installation/nic-images/get-registry-image.md" >}}) topic.
+- The [Get the NGINX Ingress Controller image with JWT]({{< ref "/nic/installation/nic-images/get-image-using-jwt.md" >}}) topic describes how to use your subscription JWT token to get the image.
+- The [Build NGINX Ingress Controller]({{< ref "/nic/installation/build-nginx-ingress-controller.md" >}}) topic explains how to push an image to a private Docker registry.


Suggested change

- The [Build NGINX Ingress Controller]({{< ref "/nic/installation/build-nginx-ingress-controller.md" >}}) topic explains how to push an image to a private Docker registry.

- The [Push the image to your private registry]({{< ref "/nic/installation/build-nginx-ingress-controller.md#push-image)" >}}) topic explains how to push an image to a private Docker registry.

pdabelf5 · 2025-07-18T15:11:00Z

content/nic/installation/installing-nic/installation-with-helm.md

-    --set controller.name=""
-    ```
+```shell
+helm install my-release -f values-plus.yaml .


The OCI example above uses --set arguments to pass the correct values to the helm command. We should be consistent. Also, the command does not describe what configuration should be included in the values file.

pdabelf5 · 2025-07-18T15:11:46Z

content/nic/installation/installing-nic/installation-with-helm.md


-6. Once the upgrade process has finished, use `kubectl describe` on the deployment to verify the change by reviewing its events:
+The command deploys NGINX Ingress Controller in your Kubernetes cluster in the default configuration. The [Helm chart parameters](#helm-chart-parameters) lists the parameters that can be configured during installation.


This comment should also be included for OCI installations

travisamartin · 2025-07-18T18:11:48Z

content/nic/installation/upgrade-version.md

+kubectl apply -f https://raw.githubusercontent.com/nginx/kubernetes-ingress/v{{< nic-version >}}/deploy/crds.yaml
+```
+
+In the above command, `v{{< nic-version >}}` represents the version of NGINX Ingress Controller release rather than the Helm chart version.


Suggested change

In the above command, `v{{< nic-version >}}` represents the version of NGINX Ingress Controller release rather than the Helm chart version.

In the above command, `v{{< nic-version >}}` represents the version of the NGINX Ingress Controller release rather than the Helm chart version.

travisamartin · 2025-07-18T18:14:05Z

content/nic/installation/upgrade-version.md

+
+This section provides step-by-step instructions for upgrading NGINX Ingress Controller from version v3.x to v4.0.0.
+
+There are two necessary steps required: updating the `apiVersion` value of custom resources and configuring structured logging.


This might catch attention better as a bulleted list.

travisamartin · 2025-07-18T18:15:36Z

content/nic/installation/upgrade-version.md

+
+### Update custom resource apiVersion
+
+If the Helm chart you have been using is `v2.x`, before upgrading to NGINX Ingress Controller 4.0.0 you must update your GlobalConfiguration, Policy and TransportServer resources from `apiVersion: k8s.nginx.org/v1alpha1` to `apiVersion: k8s.nginx.org/v1`.


Suggested change

If the Helm chart you have been using is `v2.x`, before upgrading to NGINX Ingress Controller 4.0.0 you must update your GlobalConfiguration, Policy and TransportServer resources from `apiVersion: k8s.nginx.org/v1alpha1` to `apiVersion: k8s.nginx.org/v1`.

If you're using Helm chart version `v2.x`, update your `GlobalConfiguration`, `Policy`, and `TransportServer` resources from `apiVersion: k8s.nginx.org/v1alpha1` to `apiVersion: k8s.nginx.org/v1` before upgrading to NGINX Ingress Controller 4.0.0.

serial comma

travisamartin · 2025-07-18T18:16:01Z

content/nic/installation/upgrade-version.md

+
+If the Helm chart you have been using is `v2.x`, before upgrading to NGINX Ingress Controller 4.0.0 you must update your GlobalConfiguration, Policy and TransportServer resources from `apiVersion: k8s.nginx.org/v1alpha1` to `apiVersion: k8s.nginx.org/v1`.
+
+If the Helm chart you have been using is `v1.0.2` or earlier (NGINX Ingress Controller `v3.3.2`), upgrade to Helm chart `v1.4.2` (NGINX Ingress Controller `v3.7.2`) before updating your GlobalConfiguration, Policy and TransportServer resources.


Suggested change

If the Helm chart you have been using is `v1.0.2` or earlier (NGINX Ingress Controller `v3.3.2`), upgrade to Helm chart `v1.4.2` (NGINX Ingress Controller `v3.7.2`) before updating your GlobalConfiguration, Policy and TransportServer resources.

If the Helm chart you have been using is `v1.0.2` or earlier (NGINX Ingress Controller `v3.3.2`), upgrade to Helm chart `v1.4.2` (NGINX Ingress Controller `v3.7.2`) before updating your GlobalConfiguration, Policy, and TransportServer resources.

travisamartin · 2025-07-18T18:22:52Z

content/nic/installation/upgrade-version.md

+If a *GlobalConfiguration*, *Policy* or *TransportServer* resource is deployed with `apiVersion: k8s.nginx.org/v1alpha1`, it will be **deleted** during the upgrade process.
+{{</ warning >}}
+
+Once above specified custom resources are moved to `v1` ,please run below `kubectl` commands before upgrading to v4.0.0 Custom Resource Definitions (CRDs) to avoid [this issue](https://github.com/nginx/kubernetes-ingress/issues/7010).


Thought it might be helpful to describe the issue that's linked to.

Suggested change

Once above specified custom resources are moved to `v1` ,please run below `kubectl` commands before upgrading to v4.0.0 Custom Resource Definitions (CRDs) to avoid [this issue](https://github.com/nginx/kubernetes-ingress/issues/7010).

After you move the custom resources to `v1`, run the following `kubectl` commands before upgrading to v4.0.0 Custom Resource Definitions (CRDs) to avoid webhook errors caused by leftover `v1alpha1` resources. For details, see [GitHub issue #7010](https://github.com/nginx/kubernetes-ingress/issues/7010).

active voice

travisamartin · 2025-07-18T18:26:28Z

content/nic/installation/upgrade-version.md

+
+### Configure structured logging
+
+To configure structured logging, you must update your log deployment arguments from an integer to a string. The logs themselves can also be rendered in different formats.


Suggested change

To configure structured logging, you must update your log deployment arguments from an integer to a string. The logs themselves can also be rendered in different formats.

To configure structured logging, you must update your log deployment arguments from an integer to a string. You can also choose different formats for the log output.

active voice

travisamartin · 2025-07-18T18:27:20Z

content/nic/installation/upgrade-version.md

+
+{{%tab name="Helm"%}}
+
+The Helm value of `controller.logLevel` has been changed from an integer to a string.


Suggested change

The Helm value of `controller.logLevel` has been changed from an integer to a string.

The Helm value `controller.logLevel` is now a string instead of an integer.

travisamartin · 2025-07-18T18:30:06Z

content/nic/installation/upgrade-version.md

+
+The topic also contains guidance for [sending reports to NGINX Instance Manager]({{< ref "/nic/installation/create-license-secret.md#nim">}}), which is necessary for air-gapped environments.
+
+In prior versions, usage reporting with the cluster connector was required: it is no longer necessary, as it is built into NGINX Plus.


Suggested change

In prior versions, usage reporting with the cluster connector was required: it is no longer necessary, as it is built into NGINX Plus.

Earlier versions required usage reporting through the cluster connector. This is no longer needed because it's now built into NGINX Plus.

travisamartin · 2025-07-18T18:31:14Z

content/nic/installation/upgrade-version.md

+
+## Upgrade a version older than v3.1.0
+
+For NGINX Ingress Controller version v3.1.0, [changes were introduced](https://github.com/nginx/kubernetes-ingress/pull/3606) to Helm resource names, labels and annotations to fit with Helm best practices.


Suggested change

For NGINX Ingress Controller version v3.1.0, [changes were introduced](https://github.com/nginx/kubernetes-ingress/pull/3606) to Helm resource names, labels and annotations to fit with Helm best practices.

Starting in version 3.1.0, NGINX Ingress Controller uses updated Helm resource names, labels, and annotations to follow Helm best practices. [See the changes.](https://github.com/nginx/kubernetes-ingress/pull/3606)

style guide says to use serial commas

travisamartin · 2025-07-18T18:33:21Z

content/nic/installation/upgrade-version.md

+When using Helm to upgrade from a version prior to 3.1.0, certain resources like Deployment, DaemonSet and Service will be recreated during the process, which will result in downtime.
+
+We advise updating all resources to match the new naming convention: the following steps will minimize the aforementioned downtime.


Suggested change

When using Helm to upgrade from a version prior to 3.1.0, certain resources like Deployment, DaemonSet and Service will be recreated during the process, which will result in downtime.

We advise updating all resources to match the new naming convention: the following steps will minimize the aforementioned downtime.

When you upgrade with Helm from a version earlier than 3.1.0, some resources such as `Deployment`, `DaemonSet`, and `Service` are recreated. This causes downtime.

To reduce downtime, update all resources to use the new naming convention. The following steps help you do that.

"aforementioned" might be difficult for a global audience at an 8th grade reading level.

travisamartin · 2025-07-18T18:35:11Z

content/nic/installation/upgrade-version.md

+Selector: app=nginx-ingress-nginx-ingress
+```
+
+Checkout the latest available tag using `git checkout v{{< nic-version >}}`


Suggested change

Checkout the latest available tag using `git checkout v{{< nic-version >}}`

Check out the latest available tag using `git checkout v{{< nic-version >}}`

check out (v) -- two words

travisamartin · 2025-07-18T18:35:43Z

content/nic/installation/upgrade-version.md

+
+Checkout the latest available tag using `git checkout v{{< nic-version >}}`
+
+Navigate to `/kubernetes-ingress/charts/nginx-ingress`


Suggested change

Navigate to `/kubernetes-ingress/charts/nginx-ingress`

Go to `/kubernetes-ingress/charts/nginx-ingress`

Style guide says to use "go" instead of "navigate"

travisamartin · 2025-07-18T18:36:16Z

content/nic/installation/upgrade-version.md

+--set fullnameOverride="nginx-ingress-nginx-ingress"
+```
+
+It could look as follows:


Suggested change

It could look as follows:

It might look like this:

travisamartin · 2025-07-18T18:36:34Z

content/nic/installation/upgrade-version.md

+Selector: app=<helm_release_name>-nginx-ingress
+```
+
+Checkout the latest available tag using `git checkout v{{< nic-version >}}`


Suggested change

Checkout the latest available tag using `git checkout v{{< nic-version >}}`

Check out the latest available tag using `git checkout v{{< nic-version >}}`

travisamartin · 2025-07-18T18:36:42Z

content/nic/installation/upgrade-version.md

+
+Checkout the latest available tag using `git checkout v{{< nic-version >}}`
+
+Navigate to `/kubernetes-ingress/charts/nginx-ingress`.


Suggested change

Navigate to `/kubernetes-ingress/charts/nginx-ingress`.

Go to `/kubernetes-ingress/charts/nginx-ingress`.

travisamartin · 2025-07-18T18:36:59Z

content/nic/installation/upgrade-version.md

+--set controller.name=""
+```
+
+It could look as follows:


Suggested change

It could look as follows:

It might look like this:

travisamartin · 2025-07-18T18:38:52Z

content/nic/releases.md

@@ -158,10 +158,10 @@ versions: 1.25-1.32.
 16 Dec 2024

 With added support for [NGINX R33]({{< ref "/nginx/releases.md#nginxplusrelease-33-r33" >}}), deployments of F5 NGINX Ingress Controller using NGINX Plus now require a valid JSON Web Token to run.
-Please see the [Upgrading to v4]({{< ref "/nic/installation/installing-nic/upgrade-to-v4.md#create-license-secret" >}}) for full details on setting up your license `Secret`.
+Please see the [Upgrading to v4]({{< ref "/nic/installation/upgrade-version.md#upgrade-from-3x-to-4x" >}}) for full details on setting up your license `Secret`.


Suggested change

Please see the [Upgrading to v4]({{< ref "/nic/installation/upgrade-version.md#upgrade-from-3x-to-4x" >}}) for full details on setting up your license `Secret`.

For full details on setting up your license `Secret`, see [Upgrading to v4]({{< ref "/nic/installation/upgrade-version.md#upgrade-from-3x-to-4x" >}}).

We shoudl avoid please: https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/p/please

travisamartin · 2025-07-18T18:39:11Z

content/nic/releases.md


 API Version `v1alpha1` of `GlobalConfiguration`, `Policy` and `TransportServer` resources are now deprecated.
-Please see [Update custom resource apiVersion]({{< ref "/nic/installation/installing-nic/upgrade-to-v4.md#update-custom-resource-apiversion" >}}) for full details on updating your resources.
+Please see [Update custom resource apiVersion]({{< ref "/nic/installation/upgrade-version.md#upgrade-from-3x-to-4x" >}}) for full details on updating your resources.


Suggested change

Please see [Update custom resource apiVersion]({{< ref "/nic/installation/upgrade-version.md#upgrade-from-3x-to-4x" >}}) for full details on updating your resources.

For full details on updating your resources, see [Update custom resource apiVersion]({{< ref "/nic/installation/upgrade-version.md#upgrade-from-3x-to-4x" >}}).

ADubhlaoich requested review from a team as code owners July 15, 2025 16:32

github-actions bot added documentation Improvements or additions to documentation product/nic NGINX Ingress Controller related issues labels Jul 15, 2025

vepatel reviewed Jul 15, 2025

View reviewed changes

content/nic/installation/upgrade-version.md Show resolved Hide resolved

vepatel reviewed Jul 15, 2025

View reviewed changes

content/nic/installation/upgrade-version.md Show resolved Hide resolved

ADubhlaoich added 4 commits July 15, 2025 17:47

Merge branch 'main' into nic/upgrade-instructions

2386768

Merge branch 'main' into nic/upgrade-instructions

1ce25d2

Merge branch 'main' into nic/upgrade-instructions

cab2b43

Merge branch 'main' into nic/upgrade-instructions

fcb0ea5

ADubhlaoich requested a review from a team July 17, 2025 08:54

Merge branch 'main' into nic/upgrade-instructions

cea2a56

ADubhlaoich linked an issue Jul 17, 2025 that may be closed by this pull request

NIC Upgrades to current version (5.1) #806

Open

ADubhlaoich added 4 commits July 17, 2025 15:44

Merge branch 'main' into nic/upgrade-instructions

fe71933

Merge branch 'main' into nic/upgrade-instructions

5d8a199

feat: Move and rename old upgrade instructions

00b5ba8

Merge branch 'main' into nic/upgrade-instructions

b2b0195

ADubhlaoich requested a review from vepatel July 18, 2025 14:46

pdabelf5 reviewed Jul 18, 2025

View reviewed changes

ADubhlaoich added 2 commits July 18, 2025 16:44

Merge branch 'main' into nic/upgrade-instructions

b8d700d

Merge branch 'main' into nic/upgrade-instructions

c7ccbde

travisamartin reviewed Jul 18, 2025

View reviewed changes

		- Download the image using your NGINX Ingress Controller subscription certificate and key. View the [Get NGINX Ingress Controller from the F5 Registry]({{< ref "/nic/installation/nic-images/get-registry-image.md" >}}) topic.
		- The [Get the NGINX Ingress Controller image with JWT]({{< ref "/nic/installation/nic-images/get-image-using-jwt.md" >}}) topic describes how to use your subscription JWT token to get the image.

	- The [Build NGINX Ingress Controller]({{< ref "/nic/installation/build-nginx-ingress-controller.md" >}}) topic explains how to push an image to a private Docker registry.
	- The [Push the image to your private registry]({{< ref "/nic/installation/build-nginx-ingress-controller.md#push-image)" >}}) topic explains how to push an image to a private Docker registry.


		6. Once the upgrade process has finished, use `kubectl describe` on the deployment to verify the change by reviewing its events:
		The command deploys NGINX Ingress Controller in your Kubernetes cluster in the default configuration. The [Helm chart parameters](#helm-chart-parameters) lists the parameters that can be configured during installation.

	In the above command, `v{{< nic-version >}}` represents the version of NGINX Ingress Controller release rather than the Helm chart version.
	In the above command, `v{{< nic-version >}}` represents the version of the NGINX Ingress Controller release rather than the Helm chart version.


		This section provides step-by-step instructions for upgrading NGINX Ingress Controller from version v3.x to v4.0.0.

		There are two necessary steps required: updating the `apiVersion` value of custom resources and configuring structured logging.


		### Update custom resource apiVersion

		If the Helm chart you have been using is `v2.x`, before upgrading to NGINX Ingress Controller 4.0.0 you must update your GlobalConfiguration, Policy and TransportServer resources from `apiVersion: k8s.nginx.org/v1alpha1` to `apiVersion: k8s.nginx.org/v1`.

	If the Helm chart you have been using is `v2.x`, before upgrading to NGINX Ingress Controller 4.0.0 you must update your GlobalConfiguration, Policy and TransportServer resources from `apiVersion: k8s.nginx.org/v1alpha1` to `apiVersion: k8s.nginx.org/v1`.
	If you're using Helm chart version `v2.x`, update your `GlobalConfiguration`, `Policy`, and `TransportServer` resources from `apiVersion: k8s.nginx.org/v1alpha1` to `apiVersion: k8s.nginx.org/v1` before upgrading to NGINX Ingress Controller 4.0.0.

	Once above specified custom resources are moved to `v1` ,please run below `kubectl` commands before upgrading to v4.0.0 Custom Resource Definitions (CRDs) to avoid [this issue](https://github.com/nginx/kubernetes-ingress/issues/7010).
	After you move the custom resources to `v1`, run the following `kubectl` commands before upgrading to v4.0.0 Custom Resource Definitions (CRDs) to avoid webhook errors caused by leftover `v1alpha1` resources. For details, see [GitHub issue #7010](https://github.com/nginx/kubernetes-ingress/issues/7010).


		### Configure structured logging

		To configure structured logging, you must update your log deployment arguments from an integer to a string. The logs themselves can also be rendered in different formats.


		{{%tab name="Helm"%}}

		The Helm value of `controller.logLevel` has been changed from an integer to a string.

	The Helm value of `controller.logLevel` has been changed from an integer to a string.
	The Helm value `controller.logLevel` is now a string instead of an integer.


		The topic also contains guidance for [sending reports to NGINX Instance Manager]({{< ref "/nic/installation/create-license-secret.md#nim">}}), which is necessary for air-gapped environments.

		In prior versions, usage reporting with the cluster connector was required: it is no longer necessary, as it is built into NGINX Plus.

	In prior versions, usage reporting with the cluster connector was required: it is no longer necessary, as it is built into NGINX Plus.
	Earlier versions required usage reporting through the cluster connector. This is no longer needed because it's now built into NGINX Plus.


		## Upgrade a version older than v3.1.0

		For NGINX Ingress Controller version v3.1.0, [changes were introduced](https://github.com/nginx/kubernetes-ingress/pull/3606) to Helm resource names, labels and annotations to fit with Helm best practices.

	For NGINX Ingress Controller version v3.1.0, [changes were introduced](https://github.com/nginx/kubernetes-ingress/pull/3606) to Helm resource names, labels and annotations to fit with Helm best practices.
	Starting in version 3.1.0, NGINX Ingress Controller uses updated Helm resource names, labels, and annotations to follow Helm best practices. [See the changes.](https://github.com/nginx/kubernetes-ingress/pull/3606)

		When using Helm to upgrade from a version prior to 3.1.0, certain resources like Deployment, DaemonSet and Service will be recreated during the process, which will result in downtime.

		We advise updating all resources to match the new naming convention: the following steps will minimize the aforementioned downtime.

	Checkout the latest available tag using `git checkout v{{< nic-version >}}`
	Check out the latest available tag using `git checkout v{{< nic-version >}}`


		Checkout the latest available tag using `git checkout v{{< nic-version >}}`

		Navigate to `/kubernetes-ingress/charts/nginx-ingress`

	Navigate to `/kubernetes-ingress/charts/nginx-ingress`
	Go to `/kubernetes-ingress/charts/nginx-ingress`

	Please see the [Upgrading to v4]({{< ref "/nic/installation/upgrade-version.md#upgrade-from-3x-to-4x" >}}) for full details on setting up your license `Secret`.
	For full details on setting up your license `Secret`, see [Upgrading to v4]({{< ref "/nic/installation/upgrade-version.md#upgrade-from-3x-to-4x" >}}).

feat: Clarify NIC install & upgrade steps #816

Are you sure you want to change the base?

feat: Clarify NIC install & upgrade steps #816

Conversation

ADubhlaoich commented Jul 15, 2025

Proposed changes

Checklist

Footnotes

Uh oh!

github-actions bot commented Jul 15, 2025

✅ Deploy Preview will be available once build job completes!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

pdabelf5 Jul 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

pdabelf5 Jul 18, 2025 •

edited

Loading

	Please see [Update custom resource apiVersion]({{< ref "/nic/installation/upgrade-version.md#upgrade-from-3x-to-4x" >}}) for full details on updating your resources.
	For full details on updating your resources, see [Update custom resource apiVersion]({{< ref "/nic/installation/upgrade-version.md#upgrade-from-3x-to-4x" >}}).