openshift4离线部署_OpenShift 4.2 离线安装补充记录
OpenShift4.2詳細安裝參考同事王征的安裝手冊(感謝王征大師的研究和答疑解惑, 大坑文章都已經搞定了，我這里是一些小坑)
因為我這邊的環境有些不同，所以這里只是自己的補充記錄，詳細的需要對照來看.
1.架構
啟動的虛擬機通過bridge和主機網絡在同一個網段，ip規劃保持和文檔一致
Bootstrap nodes
192.168.7.12
master-0.ocp4.redhat.ren
192.168.7.13
master-1.ocp4.redhat.ren
192.168.7.14
master-2.ocp4.redhat.ren
192.168.7.15
worker-0.ocp4.redhat.ren
192.168.7.16
worker-1.ocp4.redhat.ren
192.168.7.17
worker-2.ocp4.redhat.ren
192.168.7.18
2.網絡
我手頭的機器是4臺NUC,每臺4CPU,32G內存，而4.2OCP集群最少需要3臺master, 1個bootstrap,1臺作為負載均衡，dns解析等工作，再配上幾個worker節點，因此需要的機器在6+以上，采用虛擬機后,OpenShift節點啟動以后的跨主機網絡連接就是一個問題。
經過嘗試，采用的是KVM的Bridge模式，具體設置如下。
在每臺機器上設置
添加一個br0
[root@base ocp4]# cat /etc/sysconfig/network-scripts/ifcfg-br0
TYPE=Bridge
BOOTPROTO=staticIPADDR=192.168.7.1NETMASK=255.255.255.0GATEWAY=192.168.7.1ONBOOT=yes
DEFROUTE=yes
NAME=br0
DEVICE=br0
PREFIX=25
修改現有的網卡加入br0
[root@base ocp4]# cat /etc/sysconfig/network-scripts/ifcfg-eno1
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
#IPADDR=192.168.7.1#NETMASK=255.255.255.0#GATEWAY=192.168.7.1DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=eno1
UUID=4e9504c6-a5c4-4093-88b8-89a153dd66de
DEVICE=eno1
ONBOOT=yes
BRIDGE=br0
重啟網絡
systemctl restart network
啟動以后驗證筆記本還能繼續連接
[root@base ocp4]# ip a1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet127.0.0.1/8scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128scope host
valid_lft forever preferred_lft forever2: eno1: mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000link/ether 00:1f:c6:9c:56:60brd ff:ff:ff:ff:ff:ff3: wlp3s0: mtu 1500 qdisc noop state DOWN group default qlen 1000link/ether 00:c2:c6:f0:c8:78brd ff:ff:ff:ff:ff:ff4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000link/ether 00:1f:c6:9c:56:60brd ff:ff:ff:ff:ff:ff
inet192.168.7.1/25 brd 192.168.7.127 scope globalnoprefixroute br0
valid_lft forever preferred_lft forever
inet6 fe80::e458:f6ff:fea8:b655/64scope link
valid_lft forever preferred_lft forever5: virbr0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000link/ether 52:54:00:6d:9d:9f brd ff:ff:ff:ff:ff:ff
inet192.168.122.1/24 brd 192.168.122.255 scope globalvirbr0
valid_lft forever preferred_lft forever6: virbr0-nic: mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000link/ether 52:54:00:6d:9d:9f brd ff:ff:ff:ff:ff:ff12: vnet0: mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000link/ether fe:54:00:9c:66:29brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe9c:6629/64scope link
valid_lft forever preferred_lft forever20: vnet1: mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000link/ether fe:54:00:88:62:de brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe88:62de/64scope link
valid_lft forever preferred_lft forever
網絡生效后，應該生成的虛擬機可以訪問主機網絡。
建立虛擬機采用的網絡
[root@base data]# cat virt-net.xml
br0
virsh net-define --file virt-net.xml
virsh net-autostart br0
virsh net-start br0
查看一下
[root@base data]# virsh net-list
Name State Autostart Persistent----------------------------------------------------------br0 active yes yesdefault active yes yes
3. Yum源設置
參照3.11來設置yum源，但有一點要注意，盡量用3.11的高版本，之前用3.11.16來設置，結果導致podman build鏡像到本地有問題，后來替換成3.11.146版本的yum.
[root@base ocp4]# cat /etc/yum.repos.d/base.repo
[base]
name=basebaseurl=http://192.168.7.1:8080/repo/rhel-7-server-rpms/
enabled=1gpgcheck=0[ansible]
name=ansible
baseurl=http://192.168.7.1:8080/repo/rhel-7-server-ansible-2.6-rpms/
enabled=1gpgcheck=0[extra]
name=extra
baseurl=http://192.168.7.1:8080/repo/rhel-7-server-extras-rpms/
enabled=1gpgcheck=0[ose]
name=ose
baseurl=http://192.168.7.1:8080/repo/rhel-7-server-ose-3.11-rpms/
enabled=1gpgcheck=0
4.啟動虛擬機和安裝過程
指定bridge網絡啟動，調整了網絡和ram的大小
virt-install --name=ocp4-bootstrap --vcpus=4 --ram=8192\--disk path=/data/kvm/ocp4-bootstrap.qcow2,bus=virtio,size=120\--os-variant rhel8.0 --network bridge=br0,model=virtio \--boot menu=on --cdrom /data/ocp4/bootstrap-static.iso
virt-install --name=ocp4-master0 --vcpus=4 --ram=16384\--disk path=/data/kvm/ocp4-master0.qcow2,bus=virtio,size=120\--os-variant rhel8.0 --network bridge=br0,model=virtio \--boot menu=on --cdrom /data/ocp4/master-0.iso
virt-install --name=ocp4-master1 --vcpus=4 --ram=16384\--disk path=/data/kvm/ocp4-master1.qcow2,bus=virtio,size=120\--os-variant rhel8.0 --network bridge=br0,model=virtio \--boot menu=on --cdrom /data/ocp4/master-1.iso
virt-install --name=ocp4-master2 --vcpus=4 --ram=16384\--disk path=/data/kvm/ocp4-master2.qcow2,bus=virtio,size=120\--os-variant rhel8.0 --network bridge=br0,model=virtio \--boot menu=on --cdrom /data/ocp4/master-2.iso
virt-install --name=ocp4-worker0 --vcpus=4 --ram=8192\--disk path=/data/kvm/ocp4-worker0.qcow2,bus=virtio,size=120\--os-variant rhel8.0 --network bridge=br0,model=virtio \--boot menu=on --cdrom /data/ocp4/worker-0.iso
virt-install --name=ocp4-worker1 --vcpus=4 --ram=8192\--disk path=/data/kvm/ocp4-worker1.qcow2,bus=virtio,size=120\--os-variant rhel8.0 --network bridge=br0,model=virtio \--boot menu=on --cdrom /data/ocp4/worker-1.iso
virt-install --name=ocp4-worker2 --vcpus=4 --ram=8192\--disk path=/data/kvm/ocp4-worker2.qcow2,bus=virtio,size=120\--os-variant rhel8.0 --network bridge=br0,model=virtio \--boot menu=on --cdrom /data/ocp4/worker-2.iso
等大概5分鐘時間bootstrap會ready, 可以ready以后在建立其他虛擬機
等待一段時間后
在helper節點上通過命令查看安裝進度
openshift-install wait-for bootstrap-complete --log-level debug
處理完存儲后，還是在helper節點
[root@helper ocp4]# openshift-install wait-for install-complete
INFO Waiting up to 30m0sfor the cluster at https://api.ocp4.redhat.ren:6443 to initialize...
INFO Waiting up to 10m0s for the openshift-console route to be created...
INFO Install complete!INFO To access the clusteras the system:admin user when using 'oc', run 'export KUBECONFIG=/root/ocp4/auth/kubeconfig'INFO Access the OpenShift web-console here: https://console-openshift-console.apps.ocp4.redhat.ren
INFO Login to the console with user: kubeadmin, password: WRTp9-avPVu-IMWLX-KiIQ2
5. 關于bootstrap節點不ready問題
剛開始的時候，haproxy界面中bootstrap一直不ready,登錄到helper上去 sudo -i, podman images看到鏡像為空。
查看192.168.7.1的registry服務，發現shake hand error.
需要更新install-config.yaml中的additionalTrustBundle,和/etc/crts/redhat.ren.crt 一致
install-config.yaml中需要修改的部分用粗體標出
apiVersion: v1
baseDomain: redhat.ren
compute:-hyperthreading: Enabled
name: worker
replicas:3controlPlane:
hyperthreading: Enabled
name: master
replicas:3metadata:
name: ocp4
networking:
clusterNetworks:- cidr: 10.254.0.0/16hostPrefix:24networkType: OpenShiftSDN
serviceNetwork:- 172.30.0.0/16platform:
none: {}
pullSecret:'{"auths":{"registry.redhat.ren": {"auth": "ZHVtbXk6ZHVtbXk=","email": "noemail@localhost"}}}'sshKey:'ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCnejC+QkKXqEOj7lSKxpHnnIxPli2iwNveE9apd0QUFgc3xTyaQWyOqbFEsUzR2MnXV36a89DiOVnecVgXZqVDFrDZDRkMLKJTm2U85AExWE0Lmtkxpmyg5OdpFmTBCutpNy2LigG8LTkMPXIgDrfNF+37/BvKzvWdrhR6/dQwqfMGqfRi+PYscD6nUJG5kAzVugalyw8+Sv9CzS+4BMRCZ4EVKu5bB2wl1bw7KCJc+D0nhnc87qGswJquleT7CGi7N2k6/Q1iK80l1KymmwWcwvh+Yf4Nhdk4cxbeSZmPGBQIQMmOUzK0Q4xs3XZd2WvZd/NYj0D83sSCQGXEUkGL root@helper'additionalTrustBundle:|
-----BEGIN CERTIFICATE-----MIIDszCCApugAwIBAgIJAPRFC4yzZOpxMA0GCSqGSIb3DQEBCwUAMHAxCzAJBgNV
BAYTAkNOMQswCQYDVQQIDAJHRDELMAkGA1UEBwwCU1oxGDAWBgNVBAoMD0dsb2Jh
bCBTZWN1cml0eTEWMBQGA1UECwwNSVQgRGVwYXJ0bWVudDEVMBMGA1UEAwwMKi5y
ZWRoYXQucmVuMB4XDTE5MTAxODEwMTAzMFoXDTI5MTAxNTEwMTAzMFowcDELMAkG
A1UEBhMCQ04xCzAJBgNVBAgMAkdEMQswCQYDVQQHDAJTWjEYMBYGA1UECgwPR2xv
YmFsIFNlY3VyaXR5MRYwFAYDVQQLDA1JVCBEZXBhcnRtZW50MRUwEwYDVQQDDAwq
LnJlZGhhdC5yZW4wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDA1Mgq
hGebtpCx93KtaaRw5jDRbxrTdJkZvV6Wyq1BYFRQDKZ3QOcFFOMrLbN7g8Nrw1dl
zgvKLLc1l4god12RgOiM1fOVODoLIk2Z0x2VFbQ7ZIx0jKdKmaNex/fGd/MoLhij
dYtAmZokjs7sw0VNkZLlHzPgR9AXYtJp07zUUL1eRWNTOhO8LxDUviOg2eVy31yW
TrYla1ze7+meTvZs3edr5/dLncZ2PCiyaF6hOEf/t7ev4vA33p6SUY6prgaPaKlb
PiB8+7ZKsucgXd/ikKoCP/0rMcqRSIrpYuudM8Dff8OGxhfL0ChUx3VkKd2t5T3l
N3717qj+siuUb7OLAgMBAAGjUDBOMB0GA1UdDgQWBBTwuyzX5stt+Pyrs7VIr508
1VMR8zAfBgNVHSMEGDAWgBTwuyzX5stt+Pyrs7VIr5081VMR8zAMBgNVHRMEBTAD
AQH/MA0GCSqGSIb3DQEBCwUAA4IBAQBhhicfn9fY+PAxnVNn7R0PscxbYof4DVv3
lqkkO6BCLkHUivljxjU7OYpxkva34vSuK1WVZf74Mbif7NkzVS3EG0+b0h+8EcQ+Fnv4qyKBfs8LG/V/A0ukAD5AYP098jsj5tmREbnFbMy7UojVEK54w6262iefvg0b
uT5I0Y3jLljIlsxSbX4tTXjX0X/KHXK4PJ7hqdRLXnD4CgWKHjU6yNQS+sZg83VC
jsZpKl5eSBqOdXB1CFteZm571/AXlagcyGf9hvK4fV2ybQoOxgkZt9zyUvtm3myb
S5FAo4B5IvEhkge+jvolj31AWnB4v6GX0TgWotJd52GUpWDJDr5T-----END CERTIFICATE-----imageContentSources:-mirrors:- registry.redhat.ren/ocp4/openshift4
source: quay.io/openshift-release-dev/ocp-release-mirrors:- registry.redhat.ren/ocp4/openshift4
source: quay.io/openshift-release-dev/ocp-v4.0-art-dev
6.證書過期問題
登錄helper通過命令行去查安裝進度
需要重新刪除openshift-install?create ignition-configs 生成的部分。從下面這段重新開始
/bin/rm -rf *.ign .openshift_install_state.json auth bootstrap master0 master1 master2 worker0 worker1 worker2
openshift-install create ignition-configs --dir=/root/ocp4
當然我的問題是各機器的時間不同步，設置完時間同步后問題重新做問題解決。
7.image-registry-storage問題
在安裝過程中，需要執行
bash ocp4-upi-helpernode-master/files/nfs-provisioner-setup.sh
去創建nfs-provisioner的project同時部署一個pod,用于創建pvc
等待pod啟動完成后(注意查看他的狀態)
oc edit configs.imageregistry.operator.openshift.io
# 修改 storage 部分
# storage:
# pvc:
# claim:
把claim置空，之前是指向image-registry-storage的pvc的。修改完成后應該會促使pod創建一個pvc:image-registry-storage
可以通過
oc get pvc --all-namespaces
來查看是否成功。pvc會申請100G的空間，如果磁盤上沒有這么多空間的化，pvc就會在pending狀態。
oc get clusteroperator image-registry
狀態也會是False, image-registry的pod會是Pending狀態，導致集群創建無法繼續。
如果狀態不對，可以先刪除pvc,然后再修改configs.imageregistry.operator.openshift.io,會觸發創建。
只有當image-registry的co狀態為True后，然后再運行
openshift-install wait-for install-complete
等待集群繼續往下執行。
8.DNS配置
除了生成的zonefile.db不變外，為了解析registry.redhat.ren,加入registry.zonefile.db
/etc/named.conf
########### Add what's between these comments ###########
zone "ocp4.redhat.ren"IN {
type master;
file"zonefile.db";
};
zone"7.168.192.in-addr.arpa"IN {
type master;
file"reverse.db";
};
########################################################
zone"redhat.ren"IN {
type master;
file"registry.zonefile.db";
};
[root@helper named]# cat registry.zonefile.db
$TTL 1W
@ IN SOA ns1.redhat.ren. root (2019120205; serial
3H ; refresh (3hours)
30M ; retry (30minutes)
2W ; expiry (2weeks)
1W ) ; minimum (1week)
IN NS ns1.redhat.ren.
IN MX10smtp.redhat.ren.
;
;
ns1 IN A192.168.7.11smtp IN A192.168.7.11;
registry IN A192.168.7.1registry IN A192.168.7.1;
;EOF
[root@helper named]# cat reverse.db
$TTL 1W
@ IN SOA ns1.ocp4.redhat.ren. root (2019120205; serial
3H ; refresh (3hours)
30M ; retry (30minutes)
2W ; expiry (2weeks)
1W ) ; minimum (1week)
IN NS ns1.ocp4.redhat.ren.
;
; syntaxis "last octet"and the host must have fqdn with trailing dot13 IN PTR master-0.ocp4.redhat.ren.14 IN PTR master-1.ocp4.redhat.ren.15 IN PTR master-2.ocp4.redhat.ren.
;12IN PTR bootstrap.ocp4.redhat.ren.
;11IN PTR api.ocp4.redhat.ren.11 IN PTR api-int.ocp4.redhat.ren.
;16 IN PTR worker-0.ocp4.redhat.ren.17 IN PTR worker-1.ocp4.redhat.ren.18 IN PTR worker-2.ocp4.redhat.ren.
;1IN PTR registry.redhat.ren.
;EOF
安裝完后訪問
美中不足是Operatorhub沒有內容，也需要離線安裝
在Helper機器上
cd ~/ocp4
export KUBECONFIG=auth/kubeconfig
[root@helper ocp4]# ocgetnodes
NAME STATUS ROLES AGE VERSION
master-0.ocp4.redhat.ren Ready master 71m v1.14.6+c07e432da
master-1.ocp4.redhat.ren Ready master 71m v1.14.6+c07e432da
master-2.ocp4.redhat.ren Ready master 71m v1.14.6+c07e432da
worker-0.ocp4.redhat.ren Ready worker 71m v1.14.6+c07e432da
worker-1.ocp4.redhat.ren Ready worker 71m v1.14.6+c07e432da
worker-2.ocp4.redhat.ren Ready worker 71m v1.14.6+c07e432da
裝機現場
總結
以上是生活随笔為你收集整理的openshift4离线部署_OpenShift 4.2 离线安装补充记录的全部內容，希望文章能夠幫你解決所遇到的問題。
- 上一篇： Netflix 在加拿大、新西兰、西班牙
- 下一篇： 最大似然估计_状态估计的基本概念（2）最