Skip to content

Commit 41b0f04

Browse files
Merge pull request #1203 from redis/DOC-4833-rdi-k8s-deploy-fixes
DOC-4833 updated deploy instructions for K8s
2 parents 46848ad + 3e4d3df commit 41b0f04

File tree

2 files changed

+17
-12
lines changed

2 files changed

+17
-12
lines changed

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

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -156,12 +156,16 @@ kubectl create secret generic target-db-ssl --namespace=rdi \
156156

157157
## Deploy a pipeline
158158

159-
When you have created your configuration, including the [jobs]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines#job-files" >}}), use the
159+
When you have created your configuration, including the [jobs]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines#job-files" >}}), they are
160+
ready to deploy. Use [Redis Insight]({{< relref "/develop/tools/insight/rdi-connector" >}})
161+
to configure and deploy pipelines for both VM and K8s installations.
162+
163+
For VM installations, you can also use the
160164
[`redis-di deploy`]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-deploy" >}})
161-
command to deploy them:
165+
command to deploy a pipeline:
162166

163167
```bash
164168
redis-di deploy --dir <path to pipeline folder>
165169
```
166170

167-
You can also deploy a pipeline using [Redis Insight]({{< relref "/develop/tools/insight/rdi-connector" >}}).
171+

content/integrate/redis-data-integration/installation/install-k8s.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -520,10 +520,11 @@ You can verify that the RDI API works by adding the server in
520520

521521
## Using ingress controllers
522522

523-
If you want to expose the RDI API service via the K8s
523+
You must ensure that an appropriate
524+
[ingress controller](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/)
525+
is available in your K8s cluster to expose the RDI API service via the K8s
524526
[`Ingress`](https://kubernetes.io/docs/concepts/services-networking/ingress/)
525-
resource, you must ensure that an appropriate
526-
[ingress controller](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/) is available in your K8s cluster. Follow the documentation of your cloud provider or of
527+
resource. Follow the documentation of your cloud provider or of
527528
the ingress controller to install the controller correctly.
528529

529530
### Using the `nginx` ingress controller on AKS
@@ -548,12 +549,12 @@ section to learn how to do this.
548549

549550
## Deploy a pipeline
550551

551-
When the Helm installation is complete, and you have prepared the source database for CDC,
552-
you are ready to start using RDI. See the guides to
553-
[configuring]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines" >}}) and
554-
[deploying]({{< relref "/integrate/redis-data-integration/data-pipelines/deploy" >}})
555-
RDI pipelines for more information. You can also configure and deploy a pipeline
556-
using [Redis Insight]({{< relref "/develop/tools/insight/rdi-connector" >}}).
552+
When the Helm installation is complete and you have prepared the source database for CDC,
553+
you are ready to start using RDI.
554+
Use [Redis Insight]({{< relref "/develop/tools/insight/rdi-connector" >}}) to
555+
[configure]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines" >}}) and
556+
[deploy]({{< relref "/integrate/redis-data-integration/data-pipelines/deploy" >}})
557+
your pipeline.
557558

558559
## Uninstall RDI
559560

0 commit comments

Comments
 (0)