解决k8s默认端口的限制

前言 默认情况下，k8s 集群 nodePort 分配的端口范围为：30000-32767，如果 我们需要更多的端口，或者重新规划使用端口，需要进行调整 处理方法 找到kube-apiserver.yaml文件的绝对路径，其路径 为"/etc/kubernetes/manifests/kube-apiserver.yaml"，并添加参数"- – service-node-port-range=1-65535"，如下所示： apiVersion: v1 kind: Pod metadata: annotations: kubeadm.kubernetes.io/kube-apiserver.advertise-address.endpoint: 192.168.2.216:6443 creationTimestamp: null labels: component: kube-apiserver tier: control-plane name: kube-apiserver namespace: kube-system spec: containers: command: kube-apiserver –service-node-port-range=1-65535# 此行为添加的内容 –advertise-address=192.168.1.233 –allow-privileged=true –audit-log-maxage=30 –audit-log-maxbackup=10 –audit-log-maxsize=100 –authorization-mode=Node,RBAC –bind-address=0.0.0.0 –client-ca-file=/etc/kubernetes/pki/ca.crt –enable-admission-plugins=NodeRestriction –enable-bootstrap-token-auth=true –etcd-cafile=/etc/ssl/etcd/ssl/ca.pem –etcd-certfile=/etc/ssl/etcd/ssl/node-k8s-test-env-master-1.pem –etcd-keyfile=/etc/ssl/etcd/ssl/node-k8s-test-env-master-1-key.pem

–etcd- servers=https://192.168.1.233:2379,https://192.168.1.234:2379,https://192.168.1.235:2379 –feature- gates=ExpandCSIVolumes=true,RotateKubeletServerCertificate=true,TTLAfterFinished=true,CSI StorageCapacity=true –insecure-port=0 –kubelet-client-certificate=/etc/kubernetes/pki/apiserver-kubelet-client.crt –kubelet-client-key=/etc/kubernetes/pki/apiserver-kubelet-client.key –kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname –proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.crt –proxy-client-key-file=/etc/kubernetes/pki/front-proxy-client.key –requestheader-allowed-names=front-proxy-client –requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.crt –requestheader-extra-headers-prefix=X-Remote-Extra- –requestheader-group-headers=X-Remote-Group –requestheader-username-headers=X-Remote-User –secure-port=6443 –service-account-issuer=https://kubernetes.default.svc.cluster.local –service-account-key-file=/etc/kubernetes/pki/sa.pub –service-account-signing-key-file=/etc/kubernetes/pki/sa.key –service-cluster-ip-range=10.233.0.0/18 –tls-cert-file=/etc/kubernetes/pki/apiserver.crt –tls-private-key-file=/etc/kubernetes/pki/apiserver.key image: registry.cn-beijing.aliyuncs.com/kubesphereio/kube-apiserver:v1.21.5 imagePullPolicy: IfNotPresent livenessProbe: failureThreshold: 8 httpGet: host: 192.168.1.233 path: /livez port: 6443 scheme: HTTPS initialDelaySeconds: 10 periodSeconds: 10 timeoutSeconds: 15 name: kube-apiserver readinessProbe: failureThreshold: 3 httpGet: host: 192.168.1.233 path: /readyz port: 6443

scheme: HTTPS periodSeconds: 1 timeoutSeconds: 15 resources: requests: cpu: 250m startupProbe: failureThreshold: 24 httpGet: host: 192.168.1.233 path: /livez port: 6443 scheme: HTTPS initialDelaySeconds: 10 periodSeconds: 10 timeoutSeconds: 15 volumeMounts: mountPath: /etc/ssl/certs name: ca-certs readOnly: true mountPath: /etc/pki name: etc-pki readOnly: true mountPath: /etc/ssl/etcd/ssl name: etcd-certs-0 readOnly: true mountPath: /etc/kubernetes/pki name: k8s-certs readOnly: true hostNetwork: true priorityClassName: system-node-critical volumes: hostPath: path: /etc/ssl/certs type: DirectoryOrCreate name: ca-certs hostPath: path: /etc/pki type: DirectoryOrCreate name: etc-pki hostPath: path: /etc/ssl/etcd/ssl

type: DirectoryOrCreate name: etcd-certs-0 hostPath: path: /etc/kubernetes/pki type: DirectoryOrCreate name: k8s-certs status: {} 注：不需要重启，即时生效