diff options
| author |   Andreas Geissler <andreas-geissler@telekom.de> | 2023-04-21 14:21:37 +0200 |
|---|---|---|
| committer | Andreas Geissler <andreas-geissler@telekom.de> | 2023-06-01 15:44:40 +0200 |
| commit | e08eee030fd379fa7253e99626c314d021b1eacd (patch) | |
| tree | e5cf7bd85d6ea82d3de72e9f6fd802e3b7faa409 /docs/sections/guides/infra_guides/oom_infra_deployment_options.rst | |
| parent | 1a76edf1159156d832e62c268b54fd727f82057f (diff) | |
[DOC] Update London OOM documentation
Add information:
- new Deployment options (Production, Development)
- move Istio deployment to base installation
- add Gateway-API and Keycloak Installation instructions
- split and rename of a few files for updated structure
- changed rst section formatting as suggested in sphinx rtd theme
- add London Release Notes
Issue-ID: OOM-3159
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: I98b8541d51daba982fd6c8be0c85fae676d53c13
Diffstat (limited to 'docs/sections/guides/infra_guides/oom_infra_deployment_options.rst')
| -rw-r--r-- | docs/sections/guides/infra_guides/oom_infra_deployment_options.rst | 40 |
1 files changed, 40 insertions, 0 deletions
diff --git a/docs/sections/guides/infra_guides/oom_infra_deployment_options.rst b/docs/sections/guides/infra_guides/oom_infra_deployment_options.rst new file mode 100644 index 0000000000..dc206e0548 --- /dev/null +++ b/docs/sections/guides/infra_guides/oom_infra_deployment_options.rst @@ -0,0 +1,40 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 +.. International License. +.. http://creativecommons.org/licenses/by/4.0 +.. Copyright (C) 2022 Nordix Foundation + +.. Links +.. _Kubernetes: https://kubernetes.io/ +.. _Kubernetes best practices: https://kubernetes.io/docs/setup/best-practices/cluster-large/ +.. _kubelet config guide: https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/ + + + +ONAP Deployment Options +======================= + +OOM supports 2 different deployment options of ONAP. + +- Development Setup +- Production Setup + +In the following sections describe the different setups. + +Development setup +----------------- + +The development setup deploys ONAP components exposing its external services +via NodePorts and without TLS termination and internal traffic encryption. + +Production setup +---------------- + +The production setup deploys ONAP components exposing its external services +via Ingress with TLS termination. +Internal traffic encryption will be ensured by using Istio ServiceMesh. + +.. figure:: ../../resources/images/servicemesh/ServiceMesh.png + :align: center + +For external access we start to establish Authentication via Oauth2-proxy +and Keycloak which will be completed in the coming release. |