You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/faqs.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ It requires a compatible {pulsar-short} release to operate.
18
18
19
19
The following {pulsar-short} releases are supported:
20
20
21
-
* {luna-streaming} 2.8.0 or later
21
+
* {luna-streaming} 2.8.0 or later (formerly DataStax Luna Streaming)
22
22
* {pulsar} 2.9.0 or later
23
23
* {astra-stream}
24
24
@@ -33,7 +33,7 @@ Yes, {product} is open source using the Apache 2.0 license. You can find the sou
33
33
=== Does {product} support Kubernetes?
34
34
35
35
Yes.
36
-
You can run the {product} on {luna-streaming} or {pulsar-short} running on any Kubernetes platform, including Minikube, K8d, Kind, Google Kubernetes Engine (GKE), Microsoft Azure Kubernetes Service, Amazon Kubernetes Service (AKS), and other commonly used platforms.
36
+
You can run the {product} on {luna-streaming} or self-managed {pulsar-short} running on any Kubernetes platform, including Minikube, K8d, Kind, Google Kubernetes Engine (GKE), Microsoft Azure Kubernetes Service, Amazon Kubernetes Service (AKS), and other commonly used platforms.
37
37
For more information, see xref:installation:getting-started.adoc[].
Copy file name to clipboardExpand all lines: modules/installation/pages/getting-started.adoc
+16-11Lines changed: 16 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,18 +66,23 @@ Continue to the next section to learn how to use these connection details in a R
66
66
{luna-streaming}::
67
67
+
68
68
--
69
+
[TIP]
70
+
====
71
+
{luna-streaming} was formerly DataStax Luna Streaming.
72
+
====
73
+
69
74
[tabs]
70
75
====
71
76
Protocol handler (Helm chart)::
72
77
+
73
-
The {product} extension is included in the `luna-streaming-all` image used to deploy a Luna cluster.
74
-
The Luna Helm chart simplifies deployment of {product} as a protocol handler.
78
+
The {product} extension is included in the `luna-streaming-all` image used to deploy an {luna-streaming} cluster.
79
+
The {company} {pulsar-short} Helm chart simplifies deployment of {product} as a protocol handler.
75
80
+
76
-
The following steps explain how to deploy a {luna-streaming} Helm chart to create a simple {pulsar-short} cluster with the {product} extension ready for use.
81
+
The following steps explain how to deploy a {company} {pulsar-short} Helm chart to create a simple {pulsar-short} cluster with the {product} extension ready for use.
77
82
+
78
83
[IMPORTANT]
79
84
=====
80
-
The {company}Luna Helm chart used in this example is deprecated.
85
+
The {company}{pulsar-short} Helm chart used in this example is deprecated.
81
86
For Kubernetes deployments, {company} recommends xref:kaap-operator:ROOT:index.adoc[{kaap}].
82
87
=====
83
88
+
@@ -87,15 +92,15 @@ For Kubernetes deployments, {company} recommends xref:kaap-operator:ROOT:index.a
87
92
* Install https://kubernetes.io/docs/tasks/tools/[kubectl CLI] version 1.23.4 or later.
88
93
* Have access to a Kubernetes cluster with permission to create a namespace, deployments, and pods.
89
94
+
90
-
. Add the {company} Helm chart repo to your Helm store:
95
+
. Add the {company}{pulsar-short}Helm chart repo to your Helm store:
. Install the Helm chart using a xref:installation:attachment$values.yaml[minimal values file].
98
-
The following command creates a Helm release named `my-pulsar-cluster` using the {company}Luna Helm chart within a Kubernetes namespace named `datastax-pulsar`.
103
+
The following command creates a Helm release named `my-pulsar-cluster` using the {company}{pulsar-short} Helm chart within a Kubernetes namespace named `datastax-pulsar`.
99
104
This minimal configuration creates only the essential components and has no ingress or load balanced services.
The Luna Helm chart deployed {product} on the {pulsar-short} proxy and opened the correct port.
144
+
The {company}{pulsar-short} Helm chart deployed {product} on the {pulsar-short} proxy and opened the correct port.
140
145
The forwarded ports allow you to access {pulsar-short} and {product} services when running RabbitMQ client scripts and using CLI tools locally.
141
146
Your applications can now communicate with {pulsar-short} as if it were a real RabbitMQ host, as explained in the next section.
142
147
@@ -432,7 +437,7 @@ Additionally, the namespace's metrics should reflect that at least one message w
432
437
{luna-streaming}::
433
438
+
434
439
--
435
-
To use a RabbitMQ client with {product}, you use your {luna-streaming} {pulsar-short} tenant as the AMQP listener.
440
+
To use a RabbitMQ client with {product}, you use your {luna-streaming} tenant as the AMQP listener.
436
441
The following examples use a connection on `localhost:5672` with {product} as a protocol handler.
437
442
For other connection methods, see the documentation for your preferred RabbitMQ client library.
438
443
@@ -491,12 +496,12 @@ received message: test
491
496
deleted test-queue queue
492
497
----
493
498
+
494
-
. Use the {pulsar} admin CLI or the {luna-streaming} {pulsar-short} Admin Console to inspect your tenant's activity.
499
+
. Use the {pulsar} admin CLI or the {luna-streaming} Admin Console to inspect your tenant's activity.
495
500
Make sure the `test-queue` topic was created and a message was published and consumed.
496
501
497
502
Java client::
498
503
+
499
-
The following example uses a Java program to create a connection between RabbitMQ and your {luna-streaming} {pulsar-short} tenant, and then it establishes a message queue and sends a message.
504
+
The following example uses a Java program to create a connection between RabbitMQ and your {luna-streaming} tenant, and then it establishes a message queue and sends a message.
500
505
+
501
506
. Create a new Maven project:
502
507
+
@@ -620,7 +625,7 @@ Sent 'Hello World!'
620
625
Received 'Hello World!'
621
626
----
622
627
+
623
-
. Use the {pulsar-short} Admin CLI or the {luna-streaming} {pulsar-short} Admin Console to inspect your tenant's activity.
628
+
. Use the {pulsar-short} Admin CLI or the {luna-streaming} Admin Console to inspect your tenant's activity.
624
629
Make sure the `queuename` topic was created and a message was published and consumed.
0 commit comments