Difference between revisions of "K8s Installation/Input"
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
<noinclude> | <noinclude> | ||
<section begin=Network Security Groups /> | |||
== Network Security Groups == | |||
All the source are <code>Any</code> | |||
{|class=wikitable | |||
|- | |||
!Protocol!! Port Range!! Note | |||
|- | |||
| TCP || 22,443, || Basic | |||
|- | |||
| TCP || 2379-2380 || Kubernetes etcd server client API (on master nodes in multi-master deployments) | |||
|- | |||
| TCP || 6443 || Kubernetes API port | |||
|- | |||
| TCP || 8001 || Dashboard | |||
|- | |||
| TCP || 10250-10255 || kubelet,kube-scheduler and kube-controller-manager | |||
|- | |||
| TCP || 30000 || | |||
|- | |||
| ICMP || ALL || | |||
|} | |||
<section end=Network Security Groups /> | |||
==Notes== | ==Notes== | ||
Revision as of 09:12, 29 July 2021
- PKC code base
- All installation must start with rigorous access to Administrative Accounts.
- The original data content from ROADMAPS.MIT.EDU
- Knowledge of Kubernetes and the CleanSlate project
- Minimally 3 Virtual Machine instances
- Ansible already setup for the administrative machine
- Install Kubernetes software on all three following this procedure Kubernetes Installation
- Ingress Configuration, combined with some SSH license setup for HTTPS.
Network Security Groups
All the source are Any
Protocol | Port Range | Note |
---|---|---|
TCP | 22,443, | Basic |
TCP | 2379-2380 | Kubernetes etcd server client API (on master nodes in multi-master deployments) |
TCP | 6443 | Kubernetes API port |
TCP | 8001 | Dashboard |
TCP | 10250-10255 | kubelet,kube-scheduler and kube-controller-manager |
TCP | 30000 | |
ICMP | ALL |
Notes
- A logic model must be provided for the job.