From 5fb0f0a6c9429cfbc7973cd92e1222fd350d488b Mon Sep 17 00:00:00 2001 From: April M <36110273+aimurphy@users.noreply.github.com> Date: Mon, 13 Apr 2026 11:42:53 -0700 Subject: [PATCH] remove collapsibles --- modules/getting-started/pages/operator.adoc | 18 +++--------------- modules/getting-started/pages/stack.adoc | 12 ------------ .../getting-started/pages/upgrade-0-2-0.adoc | 12 ------------ modules/getting-started/pages/upgrades.adoc | 12 ------------ modules/migration/pages/migrate-cluster.adoc | 3 --- 5 files changed, 3 insertions(+), 54 deletions(-) diff --git a/modules/getting-started/pages/operator.adoc b/modules/getting-started/pages/operator.adoc index 6e6446d..65e1a30 100644 --- a/modules/getting-started/pages/operator.adoc +++ b/modules/getting-started/pages/operator.adoc @@ -38,14 +38,11 @@ kubectl get deployment ---- + .Result -[%collapsible] -==== [source,console] ---- NAME READY UP-TO-DATE AVAILABLE AGE kaap 1/1 1 1 13m ---- -==== . Describe the deployment: + @@ -55,8 +52,6 @@ kubectl describe deployment kaap ---- + .Result -[%collapsible] -==== [source,console] ---- Name: kaap @@ -110,12 +105,8 @@ Events: ---- ------ ---- ---- ------- Normal ScalingReplicaSet 2m5s deployment-controller Scaled up replica set kaap-76dfd8ddf9 to 1 ---- -==== + You've now installed KAAP. -+ -By default, when KAAP is installed, the `PulsarCluster` CRDs are also created. -This setting is defined in the {product-short} `values.yaml` file as `crd: create: true`. . Get the available CRDs: + @@ -124,9 +115,10 @@ This setting is defined in the {product-short} `values.yaml` file as `crd: creat kubectl get crds | grep kaap ---- + +By default, when KAAP is installed, the `PulsarCluster` CRDs are also created. +This setting is defined in the {product-short} `values.yaml` file as `crd: create: true`. ++ .Result -[%collapsible] -==== [source,console] ---- autorecoveries.kaap.oss.datastax.com 2023-05-12T16:35:59Z @@ -138,7 +130,6 @@ proxies.kaap.oss.datastax.com 2023-05-12T16:36:02Z pulsarclusters.kaap.oss.datastax.com 2023-05-12T16:36:04Z zookeepers.kaap.oss.datastax.com 2023-05-12T16:36:06Z ---- -==== == Uninstall @@ -150,13 +141,10 @@ helm uninstall kaap ---- .Result -[%collapsible] -==== [source,console] ---- release "kaap" uninstalled ---- -==== == Next steps diff --git a/modules/getting-started/pages/stack.adoc b/modules/getting-started/pages/stack.adoc index 2018d54..b950ce4 100644 --- a/modules/getting-started/pages/stack.adoc +++ b/modules/getting-started/pages/stack.adoc @@ -28,8 +28,6 @@ helm install pulsar kaap/kaap-stack --values helm/examples/dev-cluster/values.ya ---- + .Result -[%collapsible] -==== [source,console] ---- NAME: kaap @@ -39,7 +37,6 @@ STATUS: deployed REVISION: 1 TEST SUITE: None ---- -==== . Ensure kaap-stack is up and running: + @@ -49,8 +46,6 @@ kubectl get deployment ---- + .Result -[%collapsible] -==== [source,console] ---- NAME READY UP-TO-DATE AVAILABLE AGE @@ -62,7 +57,6 @@ pulsar-kube-prometheus-sta-operator 1/1 1 1 5m19s pulsar-kube-state-metrics 1/1 1 1 5m19s pulsar-proxy 1/1 1 1 3m19s ---- -==== . Describe the deployment: + @@ -72,8 +66,6 @@ kubectl describe deployment kaap-stack ---- + .Result -[%collapsible] -==== [source,console] ---- Name: kaap @@ -127,7 +119,6 @@ Events: ---- ------ ---- ---- ------- Normal ScalingReplicaSet 12m deployment-controller Scaled up replica set kaap-76dfd8ddf9 to 1 ---- -==== You've now installed {pulsar-stack}. @@ -141,13 +132,10 @@ helm uninstall kaap-stack ---- .Result -[%collapsible] -==== [source,console] ---- release "kaap-stack" uninstalled ---- -==== == Next steps diff --git a/modules/getting-started/pages/upgrade-0-2-0.adoc b/modules/getting-started/pages/upgrade-0-2-0.adoc index 390dde9..6096a8f 100644 --- a/modules/getting-started/pages/upgrade-0-2-0.adoc +++ b/modules/getting-started/pages/upgrade-0-2-0.adoc @@ -30,8 +30,6 @@ kubectl apply -f https://github.com/datastax/kaap/releases/download/operator-0.2 ---- + .Result -[%collapsible] -==== [source,console] ---- customresourcedefinition.apiextensions.k8s.io/autorecoveries.kaap.oss.datastax.com serverside-applied @@ -49,7 +47,6 @@ customresourcedefinition.apiextensions.k8s.io/functionsworkers.kaap.oss.datastax customresourcedefinition.apiextensions.k8s.io/proxies.kaap.oss.datastax.com serverside-applied customresourcedefinition.apiextensions.k8s.io/zookeepers.kaap.oss.datastax.com serverside-applied ---- -==== . Copy the KAAP custom resources (CRs) and move them to `v1beta1`: + @@ -68,8 +65,6 @@ kubectl get -n $namespace pulsarclusters $name -o yaml | sed 's/apiVersion: kaap ---- + .Result -[%collapsible] -==== [source,console] ---- autorecovery.kaap.oss.datastax.com/pulsar-autorecovery configured @@ -81,7 +76,6 @@ proxy.kaap.oss.datastax.com/pulsar-proxy configured zookeeper.kaap.oss.datastax.com/pulsar-zookeeper configured pulsarcluster.kaap.oss.datastax.com/pulsar configured ---- -==== . Ensure the resources exist: + @@ -91,14 +85,11 @@ kubectl get -n $namespace pulsarclusters.v1beta1.kaap.oss.datastax.com $name ---- + .Result -[%collapsible] -==== [source,plain] ---- NAME AGE pulsar 12m ---- -==== . Upgrade the Helm chart to version 0.2.0: + @@ -110,8 +101,6 @@ helm upgrade kaap --version 0.2.0 -n $namespace kaap/kaap-stack -f helm/examples ---- + .Result -[%collapsible] -==== [source,plain] ---- ...Successfully got an update from the "kaap" chart repository @@ -124,7 +113,6 @@ STATUS: deployed REVISION: 2 TEST SUITE: None ---- -==== . Ensure everything is working correctly. + diff --git a/modules/getting-started/pages/upgrades.adoc b/modules/getting-started/pages/upgrades.adoc index 127f64f..a621833 100644 --- a/modules/getting-started/pages/upgrades.adoc +++ b/modules/getting-started/pages/upgrades.adoc @@ -51,8 +51,6 @@ helm install pulsar helm/pulsar-operator -f helm/examples/bookie-autoscaling/val ---- .Result -[%collapsible] -==== [source,console] ---- NAME: pulsar @@ -62,7 +60,6 @@ STATUS: deployed REVISION: 1 TEST SUITE: None ---- -==== If you want to add more brokers to handle requests, edit `helm/examples/bookie-autoscaling/values.yaml` to change the `broker.replicas` and `broker.config.managedLedgerDefault*` properties from `1` to `3`: @@ -88,8 +85,6 @@ helm upgrade pulsar helm/pulsar-operator -f helm/examples/bookie-autoscaling/val ---- .Result -[%collapsible] -==== [source,console] ---- Release "pulsar" has been upgraded. Happy Helming! @@ -100,7 +95,6 @@ STATUS: deployed REVISION: 5 TEST SUITE: None ---- -==== The operator upgrades the cluster to the new desired state. In this case, the operator adds two more broker pods, and touches nothing else. @@ -111,8 +105,6 @@ kubectl get pods -A ---- .Result -[%collapsible] -==== [source,console] ---- pulsar-cluster pulsar-autorecovery-57cfc8b84d-xvchb 1/1 Running 0 150m @@ -126,7 +118,6 @@ pulsar-cluster pulsar-proxy-5bd5cc4fb6-9pnl7 1/1 pulsar-cluster pulsar-zookeeper-0 1/1 Running 0 155m pulsar-cluster pulsar-zookeeper-metadata-zgfn4 0/1 Completed 0 153m ---- -==== You've successfully upgraded your deployment by changing only one YAML file. @@ -140,8 +131,6 @@ kubectl replace -f helm/pulsar-operator/crds ---- .Result -[%collapsible] -==== [source,console] ---- customresourcedefinition.apiextensions.k8s.io/autorecoveries.pulsar.oss.datastax.com replaced @@ -153,7 +142,6 @@ customresourcedefinition.apiextensions.k8s.io/proxies.pulsar.oss.datastax.com re customresourcedefinition.apiextensions.k8s.io/pulsarclusters.pulsar.oss.datastax.com replaced customresourcedefinition.apiextensions.k8s.io/zookeepers.pulsar.oss.datastax.com replaced ---- -==== == Next steps diff --git a/modules/migration/pages/migrate-cluster.adoc b/modules/migration/pages/migrate-cluster.adoc index 4691012..d4982a0 100644 --- a/modules/migration/pages/migrate-cluster.adoc +++ b/modules/migration/pages/migrate-cluster.adoc @@ -31,14 +31,11 @@ kubectl config get-contexts ---- + .Result -[%collapsible] -==== [source,console] ---- CURRENT NAME CLUSTER AUTHINFO NAMESPACE * gke_gcp-techpubs_us-east1-b_pulsar-cluster gke_gcp-techpubs_us-east1-b_pulsar-cluster gke_gcp-techpubs_us-east1-b_pulsar-cluster pulsar-cluster ---- -==== + Before running the migration tool, {company} recommends switching to K8's current context and ensuring connectivity, such as with `kubectl get pods`.