Kubernates之需要加上-s ip:port指定主机的问题-yellowcong

妖狐艹你老母 2022-05-23 00:57 28阅读 0赞

> 我遇到直接使用kubctl 名利的时候，必须加上`-s ip:port` 这个参数，当时避免了这个问题，后来才明白为啥还要加上`-s 127.0.0.1:8089`，是自己将默认的8080端口给改掉了。导致服务运行的时候，不知道端口了，默认 kubctl 会找localhost:8080的服务的。改这个需要修改四个配置文件，分别是父节点的`/etc/kubernetes/apiserver`，`/etckubernetes/config`和子节点的，`/etc/kubernetes/kubelet`配置文件，以及`/etckubernetes/config` 。然后先重启父节点，然后再重启子节点。然后就可以愉快的玩耍了，再也不需要输入 -s 的参数了。

## 修改apiserver配置 ##

vim /etc/kubernetes/apiserver
    
    
    ###
    # kubernetes system config
    #
    # The following values are used to configure the kube-apiserver
    #
    
    # The address on the local server to listen to.
    KUBE_API_ADDRESS="--insecure-bind-address=0.0.0.0"
    
    # The port on the local server to listen on.
    KUBE_API_PORT="--port=8080"
    
    # Port minions listen on
    # KUBELET_PORT="--kubelet-port=10250"
    
    # Comma separated list of nodes in the etcd cluster
    KUBE_ETCD_SERVERS="--etcd-servers=http://192.168.10.2:2379"
    
    # Address range to use for services
    KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16"
    
    # default admission control policies
    KUBE_ADMISSION_CONTROL="--admission-control=NamespaceLifecycle,NamespaceExists,LimitRanger,ResourceQuota"
    
    # Add your own!
    KUBE_API_ARGS=""

![这里写图片描述][70]

## 2.修改`/etckubernetes/config` ##

vim /etc/kubernetes/config
    
    # logging to stderr means we get it in the systemd journal
    KUBE_LOGTOSTDERR="--logtostderr=true"
    
    # journal message level, 0 is debug
    KUBE_LOG_LEVEL="--v=0"
    
    # Should this cluster be allowed to run privileged docker containers
    KUBE_ALLOW_PRIV="--allow-privileged=false"
    
    # How the controller-manager, scheduler, and proxy find the apiserver
    KUBE_MASTER="--master=http://192.168.10.2:8080"

![这里写图片描述][70 1]

## 3/重启服务 ##

重启服务后，可以看到，apiserver的路径为8080端口了。

systemctl restart etcd kube-apiserver.service kube-controller-manager kube-scheduler

![这里写图片描述][70 2]

### 修改子节点 ###

修改子节点的`/etckubernetes/config`和 `/etc/kubernetes/kubelet`这两个配置文件，config这个文件，和刚刚的主节点的一毛一样，至于kubelete这个，就需要重新修改一下了。  
vim /etc/kubernetes/kubelet

KUBELET_ADDRESS="--address=0.0.0.0"
    
    # The port for the info server to serve on
    # KUBELET_PORT="--port=10250"
    
    # You may leave this blank to use the actual hostname
    KUBELET_HOSTNAME="--hostname-override=192.168.10.2"
    
    # location of the api-server
    KUBELET_API_SERVER="--api-servers=http://192.168.10.2:8080"
    
    # pod infrastructure container
    KUBELET_POD_INFRA_CONTAINER="--pod-infra-container-image=registry.access.redhat.com/rhel7/pod-infrastructure:latest"
    
    # Add your own!
    KUBELET_ARGS=""

![这里写图片描述][70 3]

### 重启子节点 ###

systemctl restart kubelet kube-proxy
    
    #直接获取节点，可以看到，不需要加上kuberctl -s 127.0.0.1:8080 get nodes 
    kuberctl get nodes

可以看到，修改了端口，和监听，直接就可以kuberctl访问了，完全不需要加上-s ip:port了。

![这里写图片描述][70 4]

[70]: /images/20220523/ade67031407d44b0889d6ad2c78e2af8.png
[70 1]: /images/20220523/4bfe7ea8a9eb4b7bbfdacad2f7aec97b.png
[70 2]: /images/20220523/200b819179f14a8eb83f441539601437.png
[70 3]: /images/20220523/685a7ea13dcd4baa9f27b231afb4257c.png
[70 4]: /images/20220523/90160bea0cc64b9887b9dd6fe08ee753.png