Do not use attribute to avoid setting to wrong version

JakeSCahill · web-flow · commit ee2918e42e9e · 2025-12-24T11:03:11.000Z
diff --git a/modules/upgrade/pages/k-upgrade-operator.adoc b/modules/upgrade/pages/k-upgrade-operator.adoc
@@ -11,7 +11,11 @@
 
 . If the new version of the Redpanda Operator introduces changes to the custom resource definitions (CRDs), apply these changes first. Upgrading CRDs ensures that the Kubernetes API can manage and interact with Redpanda resources according to the new specifications.
 +
-include::deploy:partial$kubernetes/install-crds.adoc[]
+[,bash]
+----
+kubectl kustomize "https://github.com/redpanda-data/redpanda-operator//operator/config/crd?ref=<operator-version>" \
+  | kubectl apply --server-side -f -
+----
 
 . Back up your current Helm values for the Redpanda Operator Helm chart:
 +
@@ -48,4 +52,4 @@ deployment "redpanda-controller-operator" successfully rolled out
 
 == Next steps
 
-xref:upgrade:k-rolling-upgrade.adoc[].
+xref:upgrade:k-rolling-upgrade.adoc[].

Original file line number	Diff line number	Diff line change
`@@ -11,7 +11,11 @@`
`11`	`11`
`12`	`12`	`. If the new version of the Redpanda Operator introduces changes to the custom resource definitions (CRDs), apply these changes first. Upgrading CRDs ensures that the Kubernetes API can manage and interact with Redpanda resources according to the new specifications.`
`13`	`13`	`+`
`14`		`-include::deploy:partial$kubernetes/install-crds.adoc[]`
	`14`	`+[,bash]`
	`15`	`+----`
	`16`	`+kubectl kustomize "https://github.com/redpanda-data/redpanda-operator//operator/config/crd?ref=<operator-version>" \`
	`17`	`+ \| kubectl apply --server-side -f -`
	`18`	`+----`
`15`	`19`
`16`	`20`	`. Back up your current Helm values for the Redpanda Operator Helm chart:`
`17`	`21`	`+`
`@@ -48,4 +52,4 @@ deployment "redpanda-controller-operator" successfully rolled out`
`48`	`52`
`49`	`53`	`== Next steps`
`50`	`54`
`51`		`-xref:upgrade:k-rolling-upgrade.adoc[].`
	`55`	`+xref:upgrade:k-rolling-upgrade.adoc[].`