diff --git a/modules/getting-started/pages/operator.adoc b/modules/getting-started/pages/operator.adoc index 859dcec..ace7f7e 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: create: 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 9bddca8..092c38a 100644 --- a/modules/getting-started/pages/stack.adoc +++ b/modules/getting-started/pages/stack.adoc @@ -20,8 +20,6 @@ helm install pulsar kaap/kaap-stack --values helm/examples/dev-cluster/values.ya ---- + .Result -[%collapsible] -==== [source,console] ---- NAME: kaap @@ -31,7 +29,6 @@ STATUS: deployed REVISION: 1 TEST SUITE: None ---- -==== . Ensure kaap-stack is up and running: + @@ -41,8 +38,6 @@ kubectl get deployment ---- + .Result -[%collapsible] -==== [source,console] ---- NAME READY UP-TO-DATE AVAILABLE AGE @@ -54,7 +49,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: + @@ -64,8 +58,6 @@ kubectl describe deployment kaap-stack ---- + .Result -[%collapsible] -==== [source,console] ---- Name: kaap @@ -119,7 +111,6 @@ Events: ---- ------ ---- ---- ------- Normal ScalingReplicaSet 12m deployment-controller Scaled up replica set kaap-76dfd8ddf9 to 1 ---- -==== You've now installed {pulsar-stack}. @@ -133,13 +124,10 @@ helm uninstall kaap-stack ---- .Result -[%collapsible] -==== [source,console] ---- release "kaap-stack" uninstalled ---- -==== == Next steps diff --git a/modules/getting-started/pages/upgrades.adoc b/modules/getting-started/pages/upgrades.adoc index bbf6e53..4a57605 100644 --- a/modules/getting-started/pages/upgrades.adoc +++ b/modules/getting-started/pages/upgrades.adoc @@ -46,8 +46,6 @@ helm install pulsar helm/pulsar-operator -f helm/examples/bookie-autoscaling/val ---- .Result -[%collapsible] -==== [source,console] ---- NAME: pulsar @@ -57,7 +55,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`: @@ -83,8 +80,6 @@ helm upgrade pulsar helm/pulsar-operator -f helm/examples/bookie-autoscaling/val ---- .Result -[%collapsible] -==== [source,console] ---- Release "pulsar" has been upgraded. Happy Helming! @@ -95,7 +90,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. @@ -106,8 +100,6 @@ kubectl get pods -A ---- .Result -[%collapsible] -==== [source,console] ---- pulsar-cluster pulsar-autorecovery-57cfc8b84d-xvchb 1/1 Running 0 150m @@ -121,7 +113,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. @@ -135,8 +126,6 @@ kubectl replace -f helm/pulsar-operator/crds ---- .Result -[%collapsible] -==== [source,console] ---- customresourcedefinition.apiextensions.k8s.io/autorecoveries.pulsar.oss.datastax.com replaced @@ -148,7 +137,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 5002cc6..c9e723e 100644 --- a/modules/migration/pages/migrate-cluster.adoc +++ b/modules/migration/pages/migrate-cluster.adoc @@ -30,14 +30,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`.