本文介绍了如何设置service-node-port-range,然后能够使用新的端口范围部署服务?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我要求测试服务器使用端口范围20000-22767

I have a requirement that a test server should use the port range 20000 - 22767

我用命令编辑了kubeadm-config

kubectl edit cm kubeadm-config -n kube-system

当我查看结果时,我发现更改似乎已被存储:

When I look at the result I see that the change seems to have been stored:

$ kubeadm config view命令给我

apiServer:
  extraArgs:
    authorization-mode: Node,RBAC
    service-node-port-range: 20000-22767
  timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta1
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controlPlaneEndpoint: ""
controllerManager: {}
dns:
  type: CoreDNS
etcd:
  local:
    dataDir: /var/lib/etcd
imageRepository: k8s.gcr.io
kind: ClusterConfiguration
kubernetesVersion: v1.13.3
networking:
  dnsDomain: cluster.local
  podSubnet: 10.244.0.0/16
  serviceSubnet: 10.96.0.0/12
scheduler: {}

但是当我以后尝试在新的端口范围内安装某些东西时,我会收到错误消息

But when I later try to install something within hte new port range I get the error

helm upgrade --install --kubeconfig /external-storage/workspace/potapi-orchestration/clusters/at/admin.conf potapi-services charts/potapi-services -f charts/potapi-services/values.at.yaml
Error: UPGRADE FAILED: Service "potapi-services" is invalid: spec.ports[0].nodePort: Invalid value: 21011: provided port is not in the valid range. The range of valid ports is 30000-32767

我在这里摆弄了建议,但没有运气: https://github.com /kubernetes/kubeadm/issues/122

I have fiddled with the suggestions here but with no luck: https://github.com/kubernetes/kubeadm/issues/122

推荐答案

可以从默认值更新service-node-port-range.

我用--service-node-port-range=20000-22767更新了文件/etc/kubernetes/manifests/kube-apiserver.yaml.

apiserver已重新启动,并且端口范围已更新.

The apiserver was restarted and the port range was updated.

我写了博客帖子关于它.

这篇关于如何设置service-node-port-range,然后能够使用新的端口范围部署服务?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-29 17:18