/logo_transparent.png

蜷缩的蜗牛

专注云原生运维

Docker 运行 Android 云手机

前言

市面上已经存在很多云手机厂商如多多云、雷电云、河马云手机等 但是如果自己有现成的服务器的话 可以直接搭建云手机

Istio多集群系列-单控制面跨AZ集群区域负载均衡

基于安全容灾考虑,生产K8S集群是多可用区。多可用区集群必然涉及跨可用区调用,由于是海外业务,使用的是AWS云,AWS内部跨可用区流量不像国内云厂商跨可用区流量不收费,是需要收费而且特贵。

基于成本和容灾考虑使用Istio的地域负载均衡功能,优先调度到同可用区,出现问题时调度到另一可用区。

现使用 kind 在本地创建一套多节点集群,通过标签模拟多可用区场景。

由于办公电脑是M1,而Istio1.13并不支持M1,所以选用Istio1.16,K8S1.24版本

创建多节点集群模拟跨AZ

kind配置

 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
mkdir -p multicluster
cd multicluster
cat << EOF > kind-cluster1.yaml
kind: Cluster
apiVersion: "kind.x-k8s.io/v1alpha4"
networking:
  apiServerAddress: "172.26.128.224" # 本机IP,可不设置。
  podSubnet: "10.10.0.0/16"
  serviceSubnet: "10.11.0.0/16"
nodes:
  - role: control-plane
    image: registry.cn-hangzhou.aliyuncs.com/seam/node:v1.24.15
  - role: worker
    image: registry.cn-hangzhou.aliyuncs.com/seam/node:v1.24.15
    kubeadmConfigPatches:
    - |
      kind: JoinConfiguration
      nodeRegistration:
        kubeletExtraArgs:
          node-labels: "topology.kubernetes.io/region=az01,topology.kubernetes.io/zone=az01"
  - role: worker
    image: registry.cn-hangzhou.aliyuncs.com/seam/node:v1.24.15
    kubeadmConfigPatches:
    - |
      kind: JoinConfiguration
      nodeRegistration:
        kubeletExtraArgs:
          node-labels: "topology.kubernetes.io/region=az02,topology.kubernetes.io/zone=az02"
EOF

Istio多集群系列-同一网络多控制面部署

(多集群网络架构

本文基于Istio 1.16.2,k8s 1.24

创建两套k8s集群

 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
40
41
mkdir -p multicluster
cd multicluster
cat << EOF > kind-cluster1.yaml
kind: Cluster
apiVersion: "kind.x-k8s.io/v1alpha4"
networking:
  apiServerAddress: "172.26.128.224"
  podSubnet: "10.10.0.0/16"
  serviceSubnet: "10.11.0.0/16"
nodes:
  - role: control-plane
    image: registry.cn-hangzhou.aliyuncs.com/seam/node:v1.24.15
  - role: worker
    image: registry.cn-hangzhou.aliyuncs.com/seam/node:v1.24.15
    kubeadmConfigPatches:
    - |
      kind: JoinConfiguration
      nodeRegistration:
        kubeletExtraArgs:
          node-labels: "topology.kubernetes.io/region=sg,topology.kubernetes.io/zone=az01"
EOF

cat << EOF > kind-cluster2.yaml
kind: Cluster
apiVersion: "kind.x-k8s.io/v1alpha4"
networking:
  apiServerAddress: "172.26.128.224"
  podSubnet: "10.12.0.0/16"
  serviceSubnet: "10.13.0.0/16"
nodes:
  - role: control-plane
    image: registry.cn-hangzhou.aliyuncs.com/seam/node:v1.24.15
  - role: worker
    image: registry.cn-hangzhou.aliyuncs.com/seam/node:v1.24.15
    kubeadmConfigPatches:
    - |
      kind: JoinConfiguration
      nodeRegistration:
        kubeletExtraArgs:
          node-labels: "topology.kubernetes.io/region=sg,topology.kubernetes.io/zone=az02"
EOF
1
2
3
4
5
kind create cluster --name cluster1 --kubeconfig=istio-multicluster --config=kind-cluster1.yaml
kind create cluster --name cluster2 --kubeconfig=istio-multicluster --config=kind-cluster2.yaml

kubectl config rename-context kind-cluster1  cluster1 --kubeconfig istio-multicluster
kubectl config rename-context kind-cluster2  cluster2 --kubeconfig istio-multicluster

SLA、SLO 和 SLI 的关系

SLO、SLA 和 SLI 的定义

什么是SLI

SLI或服务水平指标是对所提供服务水平某些方面的可量化衡量标准。它是您收集的有关服务的主要数据,用于指示其性能。从本质上讲,SLI是衡量服务质量的参数

02-Kube-Controller-Manager源码分析(主流程)

本文基于1.29.0版本

本文主要分析 kubernetes/cmd/kube-controller-manager 部分,该部分主要涉及各种类型的controller的参数解析,及初始化,例如 deployment controller 和statefulset controller。

代码结构

 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
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
tree  cmd/kube-controller-manager 
cmd/kube-controller-manager
├── OWNERS
├── app
│   ├── apps.go # 包含:startDeploymentController、startReplicaSetController、startStatefulSetController、startDaemonSetController
│   ├── autoscaling.go # startHPAController
│   ├── batch.go
│   ├── bootstrap.go
│   ├── certificates.go
│   ├── certificates_test.go
│   ├── cloudproviders.go
│   ├── config  # config: controller manager执行的上下文
│   │   └── config.go
│   ├── controllermanager.go
│   ├── controllermanager_test.go
│   ├── core.go
│   ├── core_test.go
│   ├── discovery.go
│   ├── flags_providerless.go
│   ├── flags_providers.go
│   ├── import_known_versions.go
│   ├── networking.go
│   ├── options   # 包含不同controller的option参数
│   │   ├── attachdetachcontroller.go
│   │   ├── cronjobcontroller.go
│   │   ├── csrsigningcontroller.go
│   │   ├── daemonsetcontroller.go
│   │   ├── deploymentcontroller.go
│   │   ├── deprecatedcontroller.go
│   │   ├── endpointcontroller.go
│   │   ├── endpointslicecontroller.go
│   │   ├── endpointslicemirroringcontroller.go
│   │   ├── ephemeralcontroller.go
│   │   ├── garbagecollectorcontroller.go
│   │   ├── hpacontroller.go
│   │   ├── jobcontroller.go
│   │   ├── legacyserviceaccounttokencleaner.go
│   │   ├── namespacecontroller.go
│   │   ├── nodeipamcontroller.go
│   │   ├── nodelifecyclecontroller.go
│   │   ├── options.go
│   │   ├── options_test.go
│   │   ├── persistentvolumebindercontroller.go
│   │   ├── podgccontroller.go
│   │   ├── replicasetcontroller.go
│   │   ├── replicationcontroller.go
│   │   ├── resourcequotacontroller.go
│   │   ├── serviceaccountcontroller.go
│   │   ├── statefulsetcontroller.go
│   │   ├── ttlafterfinishedcontroller.go
│   │   └── validatingadmissionpolicycontroller.go
│   ├── plugins.go
│   ├── plugins_providerless.go
│   ├── plugins_providers.go
│   ├── policy.go
│   ├── rbac.go
│   ├── testing
│   │   └── testserver.go
│   └── validatingadmissionpolicystatus.go
├── controller-manager.go   # main入口函数
└── names
    └── controller_names.go

5 directories, 55 files
0%