Skip to content

Commit ccbe393

Browse files
authored
docs: added architecture diagram for managed cluster, control plane (#20)
Signed-off-by: Ali Mukadam <ali.mukadam@oracle.com>
1 parent d57662f commit ccbe393

File tree

8 files changed

+26
-6
lines changed

8 files changed

+26
-6
lines changed

docs/src/SUMMARY.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,8 @@
1212
- [Multi Cluster](./multi/multi.md)
1313
- [With Public Endpoints](./multi/pub-ep.md)
1414
- [With Private Endpoints](./multi/pri-ep.md)
15-
- [With Public Load Balancers]())
16-
- [With Private Load Balancers]()
1715
- [Advanced Customizations](./advanced/advanced.md)
18-
- [Customize DNS](./advanced/customizedns.md)
16+
- [Control plane](./advanced/controlplane.md)
17+
- [Data plane]()
18+
- [DNS](./advanced/dns.md)
1919
- [Terraform Options](./terraformoptions.md)

docs/src/advanced/controlplane.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# Control plane
2+
3+
Every Verrazzano cluster (whether with dev, prod or managed-cluster profile) has a control plane. This control plane allows a Verrazzano administrator to access the various admin services from outside the cluster through a load balancer.
4+
5+
On OCI, the Verrazzano Control Plane is front-ended by an OCI Load Balancer and the ingress-nginx controller. As such a number of configuration options are possible depending on the use case:
6+
7+
1. access: the control plane can be made public or private. By default, it is public.
8+
2. shape: the load balancer shape can be configured including the bandwidth, security posture
9+
3. DNS: the domain used to access the control plane services
10+
11+
Depending on the values you choose, your architecture and possibly other requirements, additional configuration may be necessary.
File renamed without changes.

docs/src/images/managedcluster.svg

Lines changed: 3 additions & 0 deletions
Loading

docs/src/images/singlecluster.svg

Lines changed: 1 addition & 1 deletion
Loading

docs/src/multi/multi.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,13 @@
11
# Multi Cluster
22

3+
A multi-cluster deployment in Verrazzano consists of an Admin cluster and at least 1 managed cluster. An Admin cluster contains all the same system components as in the single cluster:
4+
5+
![Single Cluster](../images/singlecluster.svg)
6+
7+
whereas a managed cluster typically consists only of the application workload, the service mesh and the observability components:
8+
9+
![Managed Cluster](../images/managedcluster.svg)
10+
311
- [With Public Endpoints](./pub-ep.md)
412
- [With Private Endpoints](./pri-ep.md)
513
- [With Public Load Balancers](./pub-lb.md)

docs/src/multi/pri-lb.md

Lines changed: 0 additions & 1 deletion
This file was deleted.

docs/src/multi/pub-lb.md

Lines changed: 0 additions & 1 deletion
This file was deleted.

0 commit comments

Comments
 (0)