This article will help you use the Kubernetes Operator for RisingWave (hereinafter ‘the Operator’) to deploy a RisingWave cluster in Kubernetes.
kind
on Docker Hub.kubectl
version ≥ 1.18sysctl
parameter net.ipv4.ip_forward to 1.If you'd like to install a certain version of the Operator
Operator | RisingWave | Kubernetes |
---|---|---|
v0.4.0 | v0.18.0+ | v1.21+ |
v0.3.6 | v0.18.0+ | v1.21+ |
You can find the release notes of each version here. |
cert-manager
is not fully initialized. Simply wait for another minute and rerun the command above.risingwave-<meta_store>-<state_backend>.yaml
. For example, risingwave-postgresql-s3.yaml
means that this manifest file uses PostgreSQL as the meta storage and AWS S3 as the state backend.
RisingWave supports using these systems or services as state backends.
spec:stateStore
section under the RisingWave resource (kind: RisingWave
).
spec: stateStore: dataDirectory
parameter in the risingwave.yaml
file that you want to use to deploy a RisingWave instance. If you have multiple RisingWave instances, ensure the value of dataDirectory
for the new instance is unique (the default value is hummock
). Otherwise, the new RisingWave instance may crash. Save the changes to the risingwave.yaml
file before running the kubectl apply -f <...risingwave.yaml>
command. The directory path cannot be an absolute address, such as /a/b
, and must be no longer than 180 characters.
ClusterIP
. But it is not accessible outside Kubernetes. Therefore, you need to create a standalone Pod for PostgreSQL inside Kubernetes.Create a Pod.
Attach to the Pod so that you can execute commands inside the container.
Connect to RisingWave via `psql`.