From 05ae3987545e73313a94cbf7d7545fb042f5a825 Mon Sep 17 00:00:00 2001 From: Rakavitha Kodhandapani Date: Fri, 10 Jan 2025 09:53:19 +0530 Subject: [PATCH] added next steps in appropriate sections --- .../installation/learning-environment/self-hosted-kafka.md | 6 ++++-- .../production-environment/ingress-controller/istio.md | 4 ++-- .../production-environment/kafka/managed-kafka.md | 1 + 3 files changed, 7 insertions(+), 4 deletions(-) diff --git a/docs-gb/installation/learning-environment/self-hosted-kafka.md b/docs-gb/installation/learning-environment/self-hosted-kafka.md index 6e02858c08..cd29a28dcd 100644 --- a/docs-gb/installation/learning-environment/self-hosted-kafka.md +++ b/docs-gb/installation/learning-environment/self-hosted-kafka.md @@ -223,7 +223,9 @@ settings for Kafka configuration. uid: 5c041e69-f36b-4f14-8f0d-c8790003cb3e ``` -### Customzing the settings +After you integrated Seldon Core 2 with Kafka, you need to [Install an Ingress Controller](../production-environment/ingress-controller/istio.md) that adds an abstraction layer for traffic routing by receiving traffic from outside the Kubernetes platform and load balancing it to Pods running within the Kubernetes cluster. + +### Customzing the settings (optional) To customize the settings you can add and modify the Kafka configuration using Helm, for example to add compression for producers. @@ -240,7 +242,7 @@ To customize the settings you can add and modify the Kafka configuration using H -f values-runtime-kafka-compression.yaml \ --install ``` -### Configuring topic and consumer isolation +### Configuring topic and consumer isolation (optional) If you are using a shared Kafka cluster with other applications, it is advisable to isolate topic names and consumer group IDs from other cluster users to prevent naming conflicts. This can be achieved by configuring the following two settings: diff --git a/docs-gb/installation/production-environment/ingress-controller/istio.md b/docs-gb/installation/production-environment/ingress-controller/istio.md index 876a188a29..2faacb8f63 100644 --- a/docs-gb/installation/production-environment/ingress-controller/istio.md +++ b/docs-gb/installation/production-environment/ingress-controller/istio.md @@ -150,11 +150,11 @@ It is important to expose `seldon-service` service to enable communication betwe ``` virtualservice.networking.istio.io/iris-route created ``` -#### Optional: Enable HTTPS/TLS +#### (Optional) Enable HTTPS/TLS To secure your Ingress with HTTPS, you can configure TLS settings in the `Gateway` resource using a certificate and key. This involves additional steps like creating Kubernetes secrets for your certificates. -#### Next Steps: +### Next Steps [Verify the installation](/docs-gb/installation/test-installation.md) #### Additional Resources diff --git a/docs-gb/installation/production-environment/kafka/managed-kafka.md b/docs-gb/installation/production-environment/kafka/managed-kafka.md index b94305db70..134f64145a 100644 --- a/docs-gb/installation/production-environment/kafka/managed-kafka.md +++ b/docs-gb/installation/production-environment/kafka/managed-kafka.md @@ -526,3 +526,4 @@ security: --namespace seldon-system \ --install ``` +After you integrated Seldon Core 2 with Kafka, you need to [Install an Ingress Controller](../ingress-controller/istio.md) that adds an abstraction layer for traffic routing by receiving traffic from outside the Kubernetes platform and load balancing it to Pods running within the Kubernetes cluster. \ No newline at end of file