Skip to content

Commit 1beeb1a

Browse files
andy-stark-redisandy-stark-redis
committed
DOC-4367 started K8s install guide
1 parent 99053d0 commit 1beeb1a

File tree

5 files changed

+607
-407
lines changed

5 files changed

+607
-407
lines changed

‎content/integrate/redis-data-integration/data-pipelines/data-pipelines.md‎

Lines changed: 3 additions & 73 deletions
Original file line numberDiff line numberDiff line change
@@ -328,81 +328,11 @@ find the preparation guides for the databases that RDI supports in the
328328
[Prepare source databases]({{< relref "/integrate/redis-data-integration/data-pipelines/prepare-dbs" >}})
329329
section.
330330

331-
## Set secrets
332-
333-
Before you deploy your pipeline, you must set the authentication secrets for the
334-
source and target databases. Each secret has a corresponding property name that
335-
you can pass to the
336-
[`redis-di set-secret`]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-set-secret" >}})
337-
command to set the property's value. You can then refer to these properties
338-
in `config.yaml` using the syntax "`${PROPERTY_NAME}`"
339-
(the sample [config.yaml file](#the-configyaml-file) shows these properties in use).
340-
For example, you would use the
341-
following command line to set the source database username to `myUserName`:
342-
343-
```bash
344-
redis-di set-secret SOURCE_DB_USERNAME myUserName
345-
```
346-
347-
The table below shows the property name for each secret. Note that the
348-
username and password are required for the source and target, but the other
349-
secrets are only relevant to TLS/mTLS connections.
350-
351-
| Property name | Description |
352-
| :-- | :-- |
353-
| `SOURCE_DB_USERNAME` | Username for the source database |
354-
| `SOURCE_DB_PASSWORD` | Password for the source database |
355-
| `SOURCE_DB_CACERT` | (For TLS only) Source database trust certificate |
356-
| `SOURCE_DB_KEY` | (For mTLS only) Source database private key |
357-
| `SOURCE_DB_CERT` | (For mTLS only) Source database public key |
358-
| `SOURCE_DB_KEY_PASSWORD` | (For mTLS only) Source database private key password |
359-
| `TARGET_DB_USERNAME` | Username for the target database |
360-
| `TARGET_DB_PASSWORD` | Password for the target database |
361-
| `TARGET_DB_CACERT` | (For TLS only) Target database trust certificate |
362-
| `TARGET_DB_KEY` | (For mTLS only) Target database private key |
363-
| `TARGET_DB_CERT` | (For mTLS only) Target database public key |
364-
| `TARGET_DB_KEY_PASSWORD` | (For mTLS only) Target database private key password |
365-
366331
## Deploy a pipeline
367332

368-
If you are hosting RDI on your own VMs, you can use the
369-
[`deploy`]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-deploy" >}})
370-
command to deploy a configuration, including the jobs, once you have created them.
371-
372-
If your RDI CLI is deployed as a pod in a Kubernetes cluster, you should perform the following
373-
steps to deploy a pipeline:
374-
375-
- Create a [ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/) from the
376-
YAML files in your `jobs` folder:
377-
378-
```bash
379-
kubectl create configmap redis-di-jobs --from-file=jobs/
380-
```
381-
382-
- Deploy your jobs:
383-
384-
```bash
385-
kubectl exec -it pod/redis-di-cli -- redis-di deploy
386-
```
387-
388-
{{< note >}}When you create or modify a ConfigMap, it will be available in the `redis-di-cli` pod
389-
after a short delay. Wait around 30 seconds before running the `redis-di deploy` command.{{< /note >}}
390-
391-
You have two options to update the ConfigMap:
392-
393-
- For smaller changes, you can edit the ConfigMap directly with this command:
394-
395-
```bash
396-
kubectl edit configmap redis-di-jobs
397-
```
398-
399-
- For bigger changes, such as adding another job file, edit the files in your local `jobs` folder and then run this command:
400-
401-
```bash
402-
kubectl create configmap redis-di-jobs --from-file=jobs/ --dry-run=client -o yaml | kubectl apply -f -
403-
```
404-
405-
{{< note >}} You must run `kubectl exec -it pod/redis-di-cli -- redis-di deploy` after updating the ConfigMap with either option.{{< /note >}}
333+
When your configuration is ready, you must deploy it to start using the pipeline. See
334+
[Deploy a pipeline]({{< relref "/integrate/redis-data-integration/data-pipelines/deploy" >}})
335+
to learn how to do this.
406336

407337
## Ingest pipeline lifecycle
408338

‎content/integrate/redis-data-integration/data-pipelines/deploy.md‎

Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
1+
---
2+
Title: Deploy a pipeline
3+
aliases: /integrate/redis-data-integration/ingest/data-pipelines/data-type-handling/
4+
alwaysopen: false
5+
categories:
6+
- docs
7+
- integrate
8+
- rs
9+
- rdi
10+
description: Learn how to deploy an RDI pipeline
11+
group: di
12+
linkTitle: Deploy
13+
summary: Redis Data Integration keeps Redis in sync with the primary database in near
14+
real time.
15+
type: integration
16+
weight: 2
17+
---
18+
19+
The sections below explain how to deploy a pipeline after you have created the required
20+
[configuration]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines" >}}).
21+
22+
## Set secrets
23+
24+
Before you deploy your pipeline, you must set the authentication secrets for the
25+
source and target databases. Each secret has a corresponding property name that
26+
you can pass to the
27+
[`redis-di set-secret`]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-set-secret" >}})
28+
command to set the property's value. You can then refer to these properties
29+
in `config.yaml` using the syntax "`${PROPERTY_NAME}`"
30+
(the sample [config.yaml file](#the-configyaml-file) shows these properties in use).
31+
For example, you would use the
32+
following command line to set the source database username to `myUserName`:
33+
34+
```bash
35+
redis-di set-secret SOURCE_DB_USERNAME myUserName
36+
```
37+
38+
The table below shows the property name for each secret. Note that the
39+
username and password are required for the source and target, but the other
40+
secrets are only relevant to TLS/mTLS connections.
41+
42+
| Property name | Description |
43+
| :-- | :-- |
44+
| `SOURCE_DB_USERNAME` | Username for the source database |
45+
| `SOURCE_DB_PASSWORD` | Password for the source database |
46+
| `SOURCE_DB_CACERT` | (For TLS only) Source database trust certificate |
47+
| `SOURCE_DB_KEY` | (For mTLS only) Source database private key |
48+
| `SOURCE_DB_CERT` | (For mTLS only) Source database public key |
49+
| `SOURCE_DB_KEY_PASSWORD` | (For mTLS only) Source database private key password |
50+
| `TARGET_DB_USERNAME` | Username for the target database |
51+
| `TARGET_DB_PASSWORD` | Password for the target database |
52+
| `TARGET_DB_CACERT` | (For TLS only) Target database trust certificate |
53+
| `TARGET_DB_KEY` | (For mTLS only) Target database private key |
54+
| `TARGET_DB_CERT` | (For mTLS only) Target database public key |
55+
| `TARGET_DB_KEY_PASSWORD` | (For mTLS only) Target database private key password |
56+
57+
## Deploy a pipeline
58+
59+
If you are hosting RDI on your own VMs, you can use the
60+
[`deploy`]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-deploy" >}})
61+
command to deploy a configuration, including the jobs, once you have created them.
62+
63+
If your RDI CLI is deployed as a pod in a Kubernetes cluster, you should perform the following
64+
steps to deploy a pipeline:
65+
66+
- Create a [ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/) from the
67+
YAML files in your `jobs` folder:
68+
69+
```bash
70+
kubectl create configmap redis-di-jobs --from-file=jobs/
71+
```
72+
73+
- Deploy your jobs:
74+
75+
```bash
76+
kubectl exec -it pod/redis-di-cli -- redis-di deploy
77+
```
78+
79+
{{< note >}}When you create or modify a ConfigMap, it will be available in the `redis-di-cli` pod
80+
after a short delay. Wait around 30 seconds before running the `redis-di deploy` command.{{< /note >}}
81+
82+
You have two options to update the ConfigMap:
83+
84+
- For smaller changes, you can edit the ConfigMap directly with this command:
85+
86+
```bash
87+
kubectl edit configmap redis-di-jobs
88+
```
89+
90+
- For bigger changes, such as adding another job file, edit the files in your local `jobs` folder and then run this command:
91+
92+
```bash
93+
kubectl create configmap redis-di-jobs --from-file=jobs/ --dry-run=client -o yaml | kubectl apply -f -
94+
```
95+
96+
{{< note >}} You must run `kubectl exec -it pod/redis-di-cli -- redis-di deploy` after updating the ConfigMap with either option.{{< /note >}}

0 commit comments

Comments
 (0)