Openshift 我只能'；“不要过去”；kube apiserver DoesNotExist“；在运行于libvirt KVM的okd4.6、4.7甚至OCP上

我知道这可能与网络有关，也可能与资源有关，甚至可能是我试图在KVM上创建一个集群的事实，但经过3周的循环，我需要一些帮助才能认输

高级：我在IBM云中的8CPU 32Gb服务器上安装了Redhat CentOS Linux 8.3.201版。在此基础上，我创建了一个引导服务器（8GB ram，25GB磁盘）和3个主节点（6GB ram，25GB磁盘）。它非常紧凑，但是引导引导和主节点连接在一起

我已经从网上下载了最新的openshift安装程序以及最新的Fedora34 bare metal.iso

./oc version
Client Version: 4.7.0-0.okd-2021-05-22-050008
Server Version: 4.7.0-0.okd-2021-05-22-050008
Kubernetes Version: v1.20.0-1073+df9c8387b2dc23-dirty

每次我尝试使用新的引导时，我都会清理旧版本 以下脚本：

INSTALL_DIR=${PWD}
echo "install_dir is " $INSTALL_DIR


rm -rf $INSTALL_DIR/.openshift*
rm -rf $INSTALL_DIR/openshift
rm -rf $INSTALL_DIR/manifests
rm -rf $INSTALL_DIR/auth

cp $INSTALL_DIR/install-config.yaml.withrealsecret install-config.yaml

$INSTALL_DIR/openshift-install create manifests --dir=$INSTALL_DIR

$INSTALL_DIR/openshift-install create ignition-configs --dir=$INSTALL_DIR
cp metadata.json /var/www/html/okd4/
mv *.ign /var/www/html/okd4/
chown -R apache:apache /var/www/html/okd4/*.ign
chmod 777 /var/www/html/okd4/*.ign
chcon  --user system_u --type httpd_sys_content_t -Rv /var/www

在经历了大量难以理解的拉拽和文本流之后，大师们都加入并出现了

    ./oc get nodes
okd4-master1   Ready    master,worker   11h   v1.20.0+df9c838-1073  
okd4-master2   Ready    master,worker   11h   v1.20.0+df9c838-1073  
okd4-master3   Ready    master,worker   11h   v1.20.0+df9c838-1073  

但引导程序永远无法启动和运行Apiserver。我已经在OCP和OKD版本4.1、4.6和4.7上试过了

    Pod Status:openshift-kube-controller-manager/kube-controller-manager   DoesNotExist     
    Pod Status:openshift-cluster-version/cluster-version-operator          RunningNotReady 
    Pod Status:openshift-kube-scheduler/openshift-kube-scheduler        RunningNotReady
    Pod Status:openshift-kube-controller-manager/kube-controller-manager        DoesNotExist
    Pod Status:openshift-cluster-version/cluster-version-operator        Ready
    Pod Status:openshift-cluster-version/cluster-version-operator        Ready
    Pod Status:openshift-kube-apiserver/kube-apiserver        DoesNotExist
    Pod Status:openshift-kube-scheduler/openshift-kube-scheduler        Ready
    Pod Status:openshift-kube-controller-manager/kube-controller-manager        DoesNotExist        

我怀疑它与网络有关，但我认为我已经遵循了DNS，所有部分都可以解析，以及HAPROXY配置，否则主机就不会加入

在我发送大量信息并用输出充斥页面之前，是否有任何明显的问题需要检查

haproxy.cfg

frontend okd4_k8s_api_fe
    bind :6443
    default_backend okd4_k8s_api_be
    mode tcp
    option tcplog

backend okd4_k8s_api_be
    balance source
    #balance roundrobin
    mode tcp
    server      okd4-bootstrap 192.168.130.200:6443 check
    server      okd4-master1 192.168.130.201:6443 check
    server      okd4-master2 192.168.130.202:6443 check
    server      okd4-master3 192.168.130.203:6443 check

frontend okd4_machine_config_server_fe
    bind :22623
    default_backend okd4_machine_config_server_be
    mode tcp
    option tcplog

backend okd4_machine_config_server_be
    balance source
    #balance roundrobin
    mode tcp
    server      okd4-bootstrap 192.168.130.200:22623 check
    server      okd4-master1 192.168.130.201:22623 check
    server      okd4-master2 192.168.130.202:22623 check
    server      okd4-master3 192.168.130.203:22623 check

frontend okd4_http_ingress_traffic_fe
    bind :80
    default_backend okd4_http_ingress_traffic_be
    mode tcp
    option tcplog

backend okd4_http_ingress_traffic_be
    balance source
    #balance roundrobin
    mode tcp
    server      okd4-worker1 192.168.130.204:80 check
    server      okd4-worker2 192.168.130.205:80 check

frontend okd4_https_ingress_traffic_fe
    bind *:443
    default_backend okd4_https_ingress_traffic_be
    mode tcp
    option tcplog

backend okd4_https_ingress_traffic_be
    balance source
    #balance source
    mode tcp
    server      okd4-worker1 192.168.130.204:443 check
    server      okd4-worker2 192.168.130.205:443 check
```
```
install-config.yaml

apiVersion: v1
baseDomain: okd.local
metadata:
  name: lab

compute:
- hyperthreading: Enabled
  name: worker
  replicas: 0

controlPlane:
  hyperthreading: Enabled
  name: master
  replicas: 3

networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  networkType: OpenShiftSDN
  serviceNetwork:
  - 172.30.0.0/16

platform:
  none: {}

fips: false

pullSecret: '{"auths":{"cloud.openshift.com":{"auth":}}' (removed lots of text)
```

frontend okd4_k8s_api_fe
    bind :6443
    default_backend okd4_k8s_api_be
    mode tcp
    option tcplog

backend okd4_k8s_api_be
    balance source
    #balance roundrobin
    mode tcp
    server      okd4-bootstrap 192.168.130.200:6443 check
    server      okd4-master1 192.168.130.201:6443 check
    server      okd4-master2 192.168.130.202:6443 check
    server      okd4-master3 192.168.130.203:6443 check

frontend okd4_machine_config_server_fe
    bind :22623
    default_backend okd4_machine_config_server_be
    mode tcp
    option tcplog

backend okd4_machine_config_server_be
    balance source
    #balance roundrobin
    mode tcp
    server      okd4-bootstrap 192.168.130.200:22623 check
    server      okd4-master1 192.168.130.201:22623 check
    server      okd4-master2 192.168.130.202:22623 check
    server      okd4-master3 192.168.130.203:22623 check

frontend okd4_http_ingress_traffic_fe
    bind :80
    default_backend okd4_http_ingress_traffic_be
    mode tcp
    option tcplog

backend okd4_http_ingress_traffic_be
    balance source
    #balance roundrobin
    mode tcp
    server      okd4-worker1 192.168.130.204:80 check
    server      okd4-worker2 192.168.130.205:80 check

frontend okd4_https_ingress_traffic_fe
    bind *:443
    default_backend okd4_https_ingress_traffic_be
    mode tcp
    option tcplog

backend okd4_https_ingress_traffic_be
    balance source
    #balance source
    mode tcp
    server      okd4-worker1 192.168.130.204:443 check
    server      okd4-worker2 192.168.130.205:443 check
```
```
install-config.yaml

apiVersion: v1
baseDomain: okd.local
metadata:
  name: lab

compute:
- hyperthreading: Enabled
  name: worker
  replicas: 0

controlPlane:
  hyperthreading: Enabled
  name: master
  replicas: 3

networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  networkType: OpenShiftSDN
  serviceNetwork:
  - 172.30.0.0/16

platform:
  none: {}

fips: false

pullSecret: '{"auths":{"cloud.openshift.com":{"auth":}}' (removed lots of text)
```