Rancher安装文档-节点配置需求

节点需求

操作系统

Ubuntu 16.04 (64-bit)
Red Hat Enterprise Linux 7.5 (64-bit)
RancherOS 1.4 (64-bit)
Windows Server version 1803 (64-bit)

硬件

Hardware requirements scale based on the size of your Rancher deployment. Provision each individual node according to the requirements.

大小集群数节点数CPU核数内存
SmallUp to 5Up to 50416GB
MediumUp to 100Up to 500832GB
LargeOver 100Over 500Contact Rancher

Docker版本

需要以下版本
1.12.6
1.13.1
17.03.2
17.06 (Windows系统)

网络配置

节点IP

每个节点服务器需有静态IP。DHCP环境下需设置DHCP保留,保证每次该节点都被分配相同IP。

端口需求

如果采用HA模式部署Rancher,某些端口必须保证是打开状态。具体打开哪些端口要根据托管群集节点的服务器类型而定。例如,当节点服务器部署在基础设施(infrastructure)上,服务器的SSH端口必须打开。具体对应关系请参照下表:
Cluster Type Port Requirements
Rancher节点:
运行rancher/ranche 容器 的节点

Rancher 节点 - 入站规则

协议端口源节点说明
TCP80Load balancer/proxy that does external SSL terminationRancher UI/API when external SSL termination is used
TCP443etcd nodes
controlplane nodes
worker nodes
Hosted/Imported Kubernetes
any that needs to be able to use UI/API
Rancher agent, Rancher UI/API, kubectl

Rancher 节点 - 出站规则

协议端口目标节点说明
TCP22Any node IP from a node created using Node DriverSSH provisioning of nodes using Node Driver
TCP44335.160.43.145/32
35.167.242.46/32
52.33.59.17/32
git.rancher.io (catalogs)
TCP2376Any node IP from a node created using Node DriverDocker daemon TLS port used by Docker Machine
TCP6443Hosted/Imported Kubernetes APIKubernetes apiserver

etcd 节点

etcd 节点 - 入站规则

ProtocolPortSourceDescription
TCP2376Rancher nodesDocker daemon TLS port used by Docker Machine
(only needed when using Node Driver/Templates)
TCP2379etcd nodes
controlplane nodes
etcd client requests
TCP2380etcd nodes
controlplane nodes
etcd peer communication
UDP8472etcd nodes
controlplane nodes
worker nodes
Canal/Flannel VXLAN overlay networking
TCP9099etcd node itself (local traffic, not across nodes)
See Local node traffic
Canal/Flannel livenessProbe/readinessProbe
TCP10250controlplane nodeskubelet

etcd 节点 - 出站规则

ProtocolPortDestinationDescription
TCP443Rancher nodesRancher agent
TCP2379etcd nodesetcd client requests
TCP2380etcd nodesetcd peer communication
TCP6443controlplane nodesKubernetes apiserver
UDP8472etcd nodes
controlplane nodes
worker nodes
Canal/Flannel VXLAN overlay networking
TCP9099etcd node itself (local traffic, not across nodes)See Local node trafficCanal/Flannel livenessProbe/readinessProbe

控制(control plane)节点

控制节点 - 入站规则

ProtocolPortSourceDescription
TCP80Any that consumes Ingress servicesIngress controller (HTTP)
TCP443Any that consumes Ingress servicesIngress controller (HTTPS)
TCP2376Rancher nodesDocker daemon TLS port used by Docker Machine(only needed when using Node Driver/Templates)
TCP6443etcd nodes
controlplane nodes
worker nodes
Kubernetes apiserver
UDP8472etcd nodes
controlplane nodes
worker nodes
Canal/Flannel VXLAN overlay networking
TCP9099controlplane node itself (local traffic, not across nodes)
See Local node traffic
Canal/Flannel livenessProbe/readinessProbe
TCP10250controlplane nodeskubelet
TCP10254controlplane node itself (local traffic, not across nodes)
See Local node traffic
Ingress controller livenessProbe/readinessProbe
TCP/UDP30000-32767Any source that consumes NodePort servicesNodePort port range

控制节点 - 出站规则

ProtocolPortDestinationDescription
TCP443Rancher nodesRancher agent
TCP2379etcd nodesetcd client requests
TCP2380etcd nodesetcd peer communication
UDP8472etcd nodes
controlplane nodes
worker nodes
Canal/Flannel VXLAN overlay networking
TCP9099controlplane node itself (local traffic, not across nodes)
See Local node traffic
Canal/Flannel livenessProbe/readinessProbe
TCP10250etcd nodes controlplane nodesworker nodeskubelet
TCP10254controlplane node itself (local traffic, not across nodes)
See Local node traffic
Ingress controller livenessProbe/readinessProbe

工作节点

工作节点 - 入站规则

ProtocolPortSourceDescription
TCP80Any that consumes Ingress servicesIngress controller (HTTP)
TCP443Any that consumes Ingress servicesIngress controller (HTTPS)
TCP2376Rancher nodesDocker daemon TLS port used by Docker Machine(only needed when using Node Driver/Templates)
UDP8472etcd nodes
controlplane nodes
worker nodes
Canal/Flannel VXLAN overlay networking
TCP9099worker node itself (local traffic, not across nodes)
See Local node traffic
Canal/Flannel livenessProbe/readinessProbe
TCP10250controlplane nodeskubelet
TCP10254worker node itself (local traffic, not across nodes)
See Local node traffic
Ingress controller livenessProbe/readinessProbe
TCP/UDP30000-32767Any source that consumes NodePort servicesNodePort port range

工作节点 - 出站规则

ProtocolPortDestinationDescription
TCP443Rancher nodesRancher agent
TCP6443controlplane nodesKubernetes apiserver
UDP8472etcd nodes
controlplane nodes
worker nodes
Canal/Flannel VXLAN overlay networking
TCP9099worker node itself (local traffic, not across nodes)
See Local node traffic
Canal/Flannel livenessProbe/readinessProbe
TCP10254worker node itself (local traffic, not across nodes)
See Local node traffic
Ingress controller livenessProbe/readinessProbe

本地节点通信规则

Kubernetes 的健康检查服务(livenessProbereadinessProbe)是在本机运行的,多数情况下此通信也是被默认允许的。但是如果节点所在主机防火墙(如iptables)策略比较严格,或者节点有多个接口 (multihomed),此通信将被阻止。在这种情况下,必须配置防火墙(本地主机)或者安全组(AWS或OpenStack等云主机)来允许此通信。但要注意的是,在安全组嵌套其他安全组作为规则时,仅适用于该节点/实例的私有接口(interface)。

<h3 id="amazonec2-securitygroup-nodedriver">Amazon EC2 security group when using Node Driver</h3>
<p>If you are <a href="/docs/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/ec2/">Creating an Amazon EC2 Cluster</a>, you can choose to let Rancher create a Security Group called <code>rancher-nodes</code>. The following rules are automatically added to this Security Group.
</p>

rancher-nodes安全组

入站规则
TypeProtocolPort RangeSource
SSHTCP220.0.0.0/0
HTTPTCP800.0.0.0/0
Custom TCP RuleTCP4430.0.0.0/0
Custom TCP RuleTCP23760.0.0.0/0
Custom TCP RuleTCP2379-2380sg-xxx (rancher-nodes)
Custom UDP RuleUDP4789sg-xxx (rancher-nodes)
Custom TCP RuleTCP64430.0.0.0/0
Custom UDP RuleUDP8472sg-xxx (rancher-nodes)
Custom TCP RuleTCP10250-10252sg-xxx (rancher-nodes)
Custom TCP RuleTCP10256sg-xxx (rancher-nodes)
Custom TCP RuleTCP30000-327670.0.0.0/0
Custom UDP RuleUDP30000-327670.0.0.0/0
出站规则
TypeProtocolPort RangeDestination
All trafficAllAll0.0.0.0/0

参考:Rancher官方文档

Rancher是一个开源的容器管理平台,它提供了丰富的功能来简化和管理容器的部署和管理过程。其中一个重要的功能是警报驱动程序(Alerting Drivers),它可以帮助用户及时了解集群和容器的健康状况,并及时采取相应的措施。 Rancher支持多种警报驱动程序,其中之一是sachet配置。Sachet是一个基于Web的错误日志和异常信息聚合工具,它可以将来自不同源的警报信息集中展示,帮助用户更好地监控和分析系统中的问题。 要使用rancher-alerting-drivers-sachet配置,首先需要在Rancher中启用警报驱动程序插件。然后,您需要从Rancher的应用商店中安装rancher-alerting-drivers-sachet插件。安装完成后,您可以在Rancher的Alerting配置页面中配置Sachet。 在Sachet的配置中,您需要提供Sachet的API地址、API密钥等信息。这些信息将用于与Sachet服务器建立连接,将Rancher中的警报数据传输到Sachet中。您还可以选择配置警报的级别、触发条件等。 一旦配置完成,当Rancher中的警报触发时,警报信息将被发送到Sachet中,并在Sachet的控制台中显示出来。您可以通过Sachet的界面查看警报信息、分析问题,并采取相应的措施。 总的来说,rancher-alerting-drivers-sachet配置是在Rancher中启用和配置Sachet作为警报驱动程序的一种方式。它可以帮助用户更好地监控和管理容器集群,及时发现和解决问题,提高系统的稳定性和可靠性。
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值