Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Clarify how networking between data plane propeller and control plane data catalog can be configured in multi-cluster deployment #5345

Merged
merged 1 commit into from
May 16, 2024
Merged

Docs: Clarify how networking between data plane propeller and control plane data catalog can be configured in multi-cluster deployment #5345

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions docs/deployment/deployment/multicluster.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,13 +199,20 @@ the first cluster only.
insecure: false #enables secure communication over SSL. Requires a signed certificate
catalog:
catalog-cache:
endpoint: <your-Ingress-FQDN>:443
endpoint: <your-datacatalog-address>
insecure: false

.. note::

This step is needed so the ``flytepropeller`` instance in the data plane cluster is able to send notifications
back to the ``flyteadmin`` service in the control plane. The ``catalog`` service runs in the control plane and is used when caching is enabled.
back to the ``flyteadmin`` service in the control plane.

The ``catalog`` service runs in the control plane and is used when caching is enabled. Note that ``catalog`` is
not exposed via the ingress by default and does not have its own authentication mechanism. The ``catalog`` service
in the control plane cluster can for instance be made available to the ``flytepropeller`` services in the data plane
clusters with an internal load balancer service (see e.g. `GKE documentation <https://cloud.google.com/kubernetes-engine/docs/how-to/internal-load-balancing#create>`_
or `AWS Load Balancer Controller <https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/service/nlb/>`_).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
or `AWS Load Balancer Controller <https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/service/nlb/>`_).
or `AWS Load Balancer Controller <https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/service/nlb/>`_)

if the clusters use the same VPC network.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy to modify the formulation.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks good to me.

3. Install Flyte data plane Helm chart:

Expand Down
Loading