snctl config set --organization
command to set your default organization.
organization
option, you need to use the random string for the organization name, not the descriptive name. You can find the random string on the Dashboard, next to the organization’s descriptive name. For an example, see organizations.matrix
for an example.neo
by using a manifest file and save the manifest file instance-neo.yaml
.
Field | Description |
---|---|
apiVersion | Specify the version of Pulsar API server. |
kind | Specify the component to be created. |
status
and type
parameters for items under Conditions
are set to true
and ready
. This means that the instance neo
is created successfully.
snctl create pulsarinstance PULSAR_INSTANCE_NAME
command to create an instance. For details, see snctl reference.
neo
.
matrix
.
snctl
, you need to create a billing subscription. For more information, see subscribe to StreamNative Cloud.neo-1
by using a manifest file and save the manifest file clusterneo1.yaml
.
Field | Description |
---|---|
apiVersion | Specify the version of Pulsar API server. |
kind | Specify the component to be created. |
neo-1
.
snctl
version v1.0.0
, the Service Context feature provides a streamlined way to interact directly with your Pulsar clusters (using both Pulsar and Kafka protocols) without needing to manually specify connection details for every command.
A Service Context stores the necessary service URL and authentication information for connecting to a specific cluster. snctl
typically automatically discovers your StreamNative Cloud Pulsar clusters after you log in (snctl auth login
) and makes them available as contexts.
1. Viewing and Switching Contexts
You usually don’t need to manually create contexts for your cloud clusters. To see which context is currently active and switch between available contexts:
neo-1
):
pulsar
and kafka
commands will target the neo-1
cluster.
snctl context add-external-context
, snctl context list-external-context
, etc.)
2. Using pulsar
and kafka
Commands with the Active Context
Once a context is active, you can run pulsar
and kafka
commands directly:
<organization_name>
with your actual organization name if not set as default)
snctl
allows this using flags, and it will verify your user has permission to impersonate the specified service account.
--as-service-account
):
--use-service-account
):
This will prompt you to select from service accounts your user is allowed to impersonate.
snctl
, making it a more powerful and unified tool.
context
for that cluster. Then, you can access the cluster using the pulsarctl
CLI tool.
neo-1
cluster to the Pulsar client configuration file.
Input
pulsarctl
CLI tool to interact with the target cluster. For details, see Connect to cluster through pulsarctl and perform other operations.
matrix
as an example name.bot
by using a manifest file and save the manifest file sa-bot.yaml
.
Field | Description |
---|---|
apiVersion | Specify the version of Pulsar API server. |
kind | Specify the component to be created. |
status
and type
parameters for items under Conditions
are set to true
and ready
. This means that the service account bot
was created successfully.
snctl create serviceaccount SERVICE_ACCOUNT_NAME
command to create a service account. For details, see snctl reference.
status
block of the ServiceAccount
resource.
The following example shows how to download the service account credentials to a file called bot.json
.
Field | Description |
---|---|
client_id | It is an Auth0 Application that has been created. |
client_secret | It is used to authenticate to Auth0 for accessing snctl. |
snctl
, run the following command.
bot.json
.
bot
.
snctl
, you need to snctl version 0.16.0 or later.matrix
for an exampleironman
by using a manifest file and save the manifest file user-ironman.yaml
.
Field | Description |
---|---|
apiVersion | Specify the version of Pulsar API server. |
kind | Specify the component to be created. |
ironman@matrix.local
.