阿里云自建k8s对接SLB-阿里云开发者社区

阿里云自建k8s对接SLB

2021-11-19 1306

版权

本文内容由阿里云实名注册用户自发贡献，版权归原作者所有，阿里云开发者社区不拥有其著作权，亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容，填写侵权投诉表单进行举报，一经查实，本社区将立刻删除涉嫌侵权内容。

本文涉及的产品

应用型负载均衡 ALB，每月750个小时 15LCU

网络型负载均衡 NLB，每月750个小时 15LCU

传统型负载均衡 CLB，每月750个小时 15LCU

简介： 参考链接：https://github.com/kubernetes/cloud-provider-alibaba-cloud/blob/master/docs/getting-started.md

https://github.com/kubernetes/cloud-provider-alibaba-cloud/blob/master/docs/getting-started.md

1.创建ccm用到的cm

mkdir slb
cd slb
AccessKeyID=
AcceessKeySecret=
AccessKeyID-base64=`echo -n "$AccessKeyID" |base64`
AcceessKeySecret-base64=`echo -n "$AcceessKeySecret"|base64`
vim cloud-config.yaml
apiVersion: v1
kind: ConfigMap
metadata:  name: cloud-config
  namespace: kube-system
data:  cloud-config.conf: |-
{        "Global": {            "accessKeyID": "$AccessKeyID",            "accessKeySecret": "$AcceessKeySecret-base64"}}kubectl apply -f cloud-config.yaml

2.获取ccm用到的元数据

curl100.100.100.200/latest/meta-data/hostname
curl100.100.100.200/latest/meta-data/instance-id
vim /usr/lib/systemd/system/kubelet.service.d/10-kubeadm.conf
Environment="KUBELET_CLOUD_PROVIDER_ARGS=--cloud-provider=external --hostname-override=iZj6c3ydyj9t4ztmha08rbZ --provider-id=cn-hongkong.i-j6c3ydyj9t4ztmha08rb"Environment="--system-reserved=memory=300Mi --kube-reserved=memory=400Mi --eviction-hard=imagefs.available<15%,memory.available<300Mi,nodefs.available<10%,nodefs.inodesFree<5% --cgroup-driver=systemd"$KUBELET_CLOUD_PROVIDER_ARGS$KUBELET_CGROUP_ARGSsystemctl daemon-reload
systemctl restart kubelet

3.修改kube-apiserver

vim /etc/kubernetes/manifests/kube-apiserver.yaml
---cloud-provider=external

4.获取证书

cat /etc/kubernetes/pki/ca.crt|base64 -w 0
vim /etc/kubernetes/cloud-controller-manager.conf
kind: Config
contexts:- context:    cluster: kubernetes
    user: system:cloud-controller-manager
  name: system:cloud-controller-manager@kubernetes
current-context: system:cloud-controller-manager@kubernetes
users:- name: system:cloud-controller-manager
  user:    tokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
apiVersion: v1
clusters:- cluster:    certificate-authority-data: $ca.crt
    server: https://172.16.1.193:6443  name: kubernetes

5.创建ds

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:  name: system:cloud-controller-manager
rules:  - apiGroups:      - ""    resources:      - events
    verbs:      - create
      - patch
      - update
  - apiGroups:      - ""    resources:      - nodes
    verbs:      - get
      - list
      - watch
      - delete
      - patch
      - update
  - apiGroups:      - ""    resources:      - nodes/status
    verbs:      - patch
      - update
  - apiGroups:      - ""    resources:      - services
    verbs:      - get
      - list
      - watch
      - update
      - patch
  - apiGroups:      - ""    resources:      - services/status
    verbs:      - update
      - patch
  - apiGroups:    - ""    resources:    - serviceaccounts
    verbs:    - create
  - apiGroups:      - ""    resources:      - endpoints
    verbs:      - get
      - list
      - watch
      - create
      - patch
      - update
  - apiGroups:      - coordination.k8s.io
    resources:      - leases
    verbs:      - get
      - list
      - update
      - create
  - apiGroups:      - apiextensions.k8s.io
    resources:      - customresourcedefinitions
    verbs:      - get
      - update
      - create
      - delete
---apiVersion: v1
kind: ServiceAccount
metadata:  name: cloud-controller-manager
  namespace: kube-system
---kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:  name: system:cloud-controller-manager
roleRef:  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: system:cloud-controller-manager
subjects:- kind: ServiceAccount
  name: cloud-controller-manager
  namespace: kube-system
---apiVersion: apps/v1
kind: DaemonSet
metadata:  labels:    app: cloud-controller-manager
    tier: control-plane
  name: cloud-controller-manager
  namespace: kube-system
spec:  selector:    matchLabels:      app: cloud-controller-manager
      tier: control-plane
  updateStrategy:    rollingUpdate:      maxUnavailable: 1    type: RollingUpdate
  template:    metadata:      labels:        app: cloud-controller-manager
        tier: control-plane
      annotations:        scheduler.alpha.kubernetes.io/critical-pod: ""    spec:      serviceAccountName: cloud-controller-manager
      tolerations:      - operator: Exists
      nodeSelector:        node-role.kubernetes.io/master: ""      containers:      - name: cloud-controller-manager
        securityContext:          readOnlyRootFilesystem: true          allowPrivilegeEscalation: false          runAsNonRoot: true          runAsUser: 1200         command:        -  /cloud-controller-manager
        - --kubeconfig=/etc/kubernetes/cloud-controller-manager.conf
        - --cloud-config=/etc/kubernetes/config/cloud-config.conf
        - --metrics-bind-addr=0
#For terway configuration        - --configure-cloud-routes=false
        image: registry-vpc.cn-shanghai.aliyuncs.com/acs/cloud-controller-manager-amd64:v2.0.1
        livenessProbe:          failureThreshold: 8          httpGet:            host: 127.0.0.1            path: /healthz
            port: 10258            scheme: HTTP
          initialDelaySeconds: 15          timeoutSeconds: 15        resources:          requests:            cpu: 100m
            memory: 200Mi
          limits:            cpu: 1000m
            memory: 1Gi
        volumeMounts:        - mountPath: /etc/kubernetes/cloud-controller-manager.conf
          name: k8s
          readOnly: true        - name: cloud-config
          mountPath: /etc/kubernetes/config
      hostNetwork: true      volumes:      - hostPath:          path: /etc/kubernetes/cloud-controller-manager.conf
          type: File
        name: k8s
      - name: cloud-config
        configMap:          name: cloud-config
          items:          - key: cloud-config.conf
            path: cloud-config.conf

6.验证

由于是单节点集群测试，故使用local模式的流量策略

[root@izj6c3ydyj9t4ztmha08rbz slb]# kubectl get svc nginx -o yaml
apiVersion: v1
kind: Service
metadata:  creationTimestamp: "2021-11-18T22:36:48Z"  finalizers:  - service.k8s.alibaba/resources
  labels:    app: nginx
    service.beta.kubernetes.io/hash: 73b160d328a26d99ed855f80117a95610f38768c282bc4bc5606bdc3
  name: nginx
  namespace: default
  resourceVersion: "12502"  uid: 9c897582-0484-41b8-b983-32626599b4c1
spec:  allocateLoadBalancerNodePorts: true  clusterIP: 10.98.194.116  clusterIPs:  - 10.98.194.116
  externalTrafficPolicy: Local
  healthCheckNodePort: 30738  internalTrafficPolicy: Cluster
  ipFamilies:  - IPv4
  ipFamilyPolicy: SingleStack
  ports:  - nodePort: 32093    port: 80    protocol: TCP
    targetPort: 80  selector:    app: nginx
  sessionAffinity: None
  type: LoadBalancer
status:  loadBalancer:    ingress:    - ip: 47.242.151.91

7.访问测试

7.1 node节点访问

7.2 pod访问

7.3 查看日志

8.ram权限

ps: 如果是ram用户需要授权如下策略

{
"Version": "1",
"Statement": [
    {
"Action": [
"ecs:Describe*",
"ecs:AttachDisk",
"ecs:CreateDisk",
"ecs:CreateSnapshot",
"ecs:CreateRouteEntry",
"ecs:DeleteDisk",
"ecs:DeleteSnapshot",
"ecs:DeleteRouteEntry",
"ecs:DetachDisk",
"ecs:ModifyAutoSnapshotPolicyEx",
"ecs:ModifyDiskAttribute",
"ecs:CreateNetworkInterface",
"ecs:DescribeNetworkInterfaces",
"ecs:AttachNetworkInterface",
"ecs:DetachNetworkInterface",
"ecs:DeleteNetworkInterface",
"ecs:DescribeInstanceAttribute"      ],
"Resource": [
"*"      ],
"Effect": "Allow"    },
    {
"Action": [
"cr:Get*",
"cr:List*",
"cr:PullRepository"      ],
"Resource": [
"*"      ],
"Effect": "Allow"    },
    {
"Action": [
"slb:*"      ],
"Resource": [
"*"      ],
"Effect": "Allow"    },
    {
"Action": [
"cms:*"      ],
"Resource": [
"*"      ],
"Effect": "Allow"    },
    {
"Action": [
"vpc:*"      ],
"Resource": [
"*"      ],
"Effect": "Allow"    },
    {
"Action": [
"log:*"      ],
"Resource": [
"*"      ],
"Effect": "Allow"    },
    {
"Action": [
"nas:*"      ],
"Resource": [
"*"      ],
"Effect": "Allow"    }
  ]
}

阿里云自建k8s对接SLB

1.创建ccm用到的cm

2.获取ccm用到的元数据

3.修改kube-apiserver

4.获取证书

5.创建ds

6.验证

7.访问测试

7.1 node节点访问

7.2 pod访问

7.3 查看日志

8.ram权限

热门文章

最新文章

相关课程

相关电子书

推荐镜像

探索云世界

热门

云计算

大数据

云原生

人工智能

数据库

开发与运维

活动广场

任务中心

训练营

直播

乘风者计划

下载

镜像站

技术资料

阿里云自建k8s对接SLB

1.创建ccm用到的cm

2.获取ccm用到的元数据

3.修改kube-apiserver

4.获取证书

5.创建ds

6.验证

7.访问测试

7.1 node节点访问

7.2 pod访问

7.3 查看日志

8.ram权限

热门文章

最新文章

相关课程

相关电子书

推荐镜像