blob: 7e8e3b335bda0b4cfa53d39dae0b19a2a6ad0bd9 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) Justin Chi (HUAWEI),Yifei Xue (HUAWEI)and Xinhui Hu (FIBERHOME)
This document introduces scenario descriptions for Euphrates 1.0 of
deployment with no SDN controller and no feature enabled.
.. contents::
:depth: 3
:local:
============
Introduction
============
This scenario is used to deploy an kubernets cluster.
Scenario components and composition
===================================
This scenario includes a set of kubernets services which are kubernets API Server,
Controller Manager, kube-proxy, kubelet,kube-dns,nginx-proxy,kubernetes-dashboard.
Nginx-proxy is used to balance all the services running on 3 control nodes behind
a VIP (Virtual IP address).
Scenario usage overview
=======================
To deploy with this scenario, you just need to assign the
k8s-nosdn-nofeature-ha.yaml to DHA file before deployment.
Limitations, Issues and Workarounds
===================================
References
==========
For more information on the OPNFV Euphrates release, please visit
http://www.opnfv.org/euphrates
|
