Fix broken upgrade finalization includes

Author: jhlodin

src/current/_includes/common/upgrade/disable-auto-finalization.md

@@ -8,10 +8,12 @@ Either of these settings prevents automatic finalization.
 {{site.data.alerts.end}}
 {% endcapture %}
 
-{% if page.path contains 'kubernetes' %}
+{% if page.name == 'upgrade-cockroachdb-kubernetes.md' %}
 
 <section class="filter-content" markdown="1" data-scope="operator">
-For clusters managed by the Operator, auto-finalization is disabled and cannot be enabled. A major version upgrade is not complete until it is manually [finalized](#finalize-a-major-version-upgrade-manually). The Operator does not yet support the [cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}) `cluster.auto_upgrade.enabled`.
+
+For clusters managed by the {{ site.data.products.public-operator }}, auto-finalization is disabled and cannot be enabled. A major version upgrade is not complete until it is manually [finalized](#finalize-a-major-version-upgrade-manually). The {{ site.data.products.public-operator }} does not support the [cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}) `cluster.auto_upgrade.enabled`.
+
 </section>
 
 <section class="filter-content" markdown="1" data-scope="manual">
@@ -22,6 +24,7 @@ To disable auto-finalization:
 
 1. Connect to the cluster using the SQL shell:
 
+    {% include_cached copy-clipboard.html %}
     ~~~ shell
     $ kubectl exec -it cockroachdb-client-secure \
     -- ./cockroach sql \
@@ -45,6 +48,7 @@ To disable auto-finalization:
 
 1. Connect to the cluster using the SQL shell:
 
+    {% include_cached copy-clipboard.html %}
     ~~~ shell
     $ kubectl exec -it cockroachdb-client-secure \
     -- ./cockroach sql \
@@ -58,6 +62,28 @@ Now, to complete a major-version upgrade, you must manually [finalize it](#final
 
 </section>
 
+{% else if page.name == 'upgrade-cockroachdb-kubernetes-operator.md' %}
+
+By default, auto-finalization is enabled, and a major-version upgrade is finalized when all nodes have rejoined the cluster using the new `cockroach` binary. This means that by default, a major-version upgrade cannot be rolled back. Instead, you must [restore the cluster to the previous version]({% link {{ page.version.version }}/restoring-backups-across-versions.md %}#support-for-restoring-backups-into-a-newer-version).
+
+To disable auto-finalization:
+
+1. Connect to the cluster using the SQL shell:
+
+    {% include_cached copy-clipboard.html %}
+    ~~~ shell
+    kubectl exec -it cockroachdb-client-secure \
+    -- ./cockroach sql \
+    --certs-dir=/cockroach-certs \
+    --host=cockroachdb-public
+    ~~~
+
+1. Set the [cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}) `cluster.auto_upgrade.enabled` to `false`.
+
+Now, to complete a major-version upgrade, you must manually [finalize it](#finalize-a-major-version-upgrade-manually) or [roll it back](#roll-back-a-major-version-upgrade).
+
+{{ new_flag }}
+
 {% else %}
 
 By default, auto-finalization is enabled, and a major-version upgrade is finalized when all nodes have rejoined the cluster using the new `cockroach` binary. This means that by default, a major-version upgrade cannot be rolled back. Instead, you must [restore the cluster to the previous version]({% link {{ page.version.version }}/restoring-backups-across-versions.md %}#support-for-restoring-backups-into-a-newer-version).