devbox
Monodyee
这个屌丝很懒，什么也没留下！
关注作者
热门标签
热门文章
当前位置:   article > 正文

ubuntu离线安装kubesphere(包括docker、harbor)_kubesphere 镜像 下载

作者：Monodyee | 2024-06-17 09:49:55

赞

踩

kubesphere 镜像 下载

        这边使用虚拟机下载依赖配置环境以及模拟服务器各个节点，使用两个虚拟机模拟离线不联网环境的服务器，使用一个虚拟机联网下载依赖包，然后传入两个不能联网的虚拟机安装所有环境（我这边偷懒就用两个虚拟机中的一个联网下载安装包。再安装到两个虚拟机内了）。

        文档参照：离线安装 (kubesphere.io)

一、虚拟机安装

         VMware下载地址：vm17pro 下载

        也可以根据你的情况来换不同版本，但是下载需要注册，后续可以去网上找免费版本或破解方法。

        下载后点击安装可能提示重启，按照要求重启即可。

        这一步更改安装位置。

        其他配置可以全部默认，一直点击下一步直到安装成功。       

         打开之后这个样子就是安装完成了，许可可以搜到然后输入

二、镜像下载安装

1、镜像下载

        这边使用ubuntu2020.04并安装图形化界面来进行配置

        大约4.1G，下载地址：

2、虚拟机安装 

        这边分别安装名为ubuntuNode01和ubuntuNode02的两个虚拟机模拟服务器两个节点来安装k8s集群和kubesphere服务。

        点击创建新的虚拟机

        选择经典，点击下一步

        iso选择刚才下载的镜像并点击下一步

 输入全名和用户名，密码可设置12345678，点击下一步

输入虚拟机名称并选择安装目录，点击下一步

磁盘设置大小50G就可以了，但我虚拟机还有别的用处就设置了200G（磁盘选单个文件或者多个文件都可以，而且它也解释清楚了区别），点击下一步

点击自定义硬件

内存可以根据主机实际情况设置4-16G，网络选桥接，处理器选4*2就是八个，如下

点击关闭后再点完成即可等待创建虚拟机

大约等一会就会出现（如果虚拟机平台报错可能是电脑不支持虚拟化或者未开启，若是虚拟化未开启不同的主板可能开启方式不同，可以搜一搜自己的主板如何开启），点击Continue

再次点击Continue

点击Install Now

弹出窗口后点击Continue

等待一会出现地图，点一下自己的大体位置，然后点Continue

输入信息，密码依旧是12345678，然后点击Continue

等待一段（很长）时间出现弹窗，点击Restart Now

等待重启成功，点击用户输入12345678密码

安装成功，按照此步骤安装另一个虚拟机ubuntuNode2，名称是node1的地方也换成node2（方便区分）。

三、配置虚拟机

        分为root用户开放登录、ssh配置、ip固定【记得两台虚拟机都要配置】

1、root用户登录

（1）重新设置密码，终端输入以下命令

sudo passwd root

然后输入12345678按回车，大约要重复三次

（2）修改50-ubuntu.conf配置文件，终端输入以下命令

sudo gedit /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf

在原有文件内容的基础上添加以下内容并保存

  1. greeter-show-manual-login=true 
  2. allow-guest=false

（3）修改gdm-autologin配置文件，终端输入以下命令

sudo gedit /etc/pam.d/gdm-autologin

 注释掉第三行的内容并保存，也就是auth    required    pam_succeed_if.so user != root quiet_success

（3）修改gdm-password配置文件，终端输入以下命令

sudo gedit /etc/pam.d/gdm-password

注释掉第三行内容并保存，也就是auth    required    pam_succeed_if.so user != root quiet_success

（4） 修改.profile配置文件，终端输入以下命令

sudo gedit /root/.profile

将最后一行替换为以下内容并保存

tty -s&&mesg n || true

 然后终端输入reboot重启虚拟机

点击Not listed，然后输入用户名root，再输入密码12345678，再按回车

打开终端，发现左侧用户为root，即为配置成功

注意两台虚拟机都要配置 

 2、ssh配置

这里需要apt下载ssh服务，apt源感觉ubuntu的就很快，所以这边就没换

（1）输入以下命令更新apt

sudo apt-get update

终端输入以下命令关闭防火墙

sudo ufw disable

（2）终端分别输入以下两个命令下载ssh的客户端和服务端

  1. sudo apt-get install openssh-server
  2. sudo apt-get install openssh-client

 （3）修改配置文件，终端输入以下命令

sudo gedit /etc/ssh/ssh_config

 删除第25行的#号并保存，也就是PasswordAuthentication yes

（4）修改配置文件，终端输入以下命令

sudo gedit /etc/ssh/sshd_config

修改33行为以下内容，并保存

PermitRootLogin yes

（5）链接测试

首先终端输入reboot重启一下机器

reboot

机器重启成功后输入ssh root@127.0.0.1，连接本机测试。第一次链接可能要输入yes，输入yes回车后需要输入密码，密码就是机器密码12345678

ssh root@127.0.0.1

出现以下信息即为链接成功 

注意两台虚拟机都要配置 

3、IP固定

这里要注意两台机器要固定不同的IP，可别一点不改的复制

（1）使用ifconfig查看自动分配的ip，在终端中输入

sudo apt-get install net-tools

输入以下命令查看虚拟机IP，记住你的网段名称，我这里是ens33

ifconfig

（2）修改配置文件，终端输入以下命令

sudo gedit /etc/netplan/01-network-manager-all.yaml

讲以下内容代替此文件内容，下面ens33换成自己ifconfig看到的网段名。ip选一个自己局域网内没被占用的就行。然后保存【两个虚拟机都要设置，我这边一个ip设置211，另一个设置212】

  1. # This is the network config written by 'subiquity'
  2. network:
  3.   ethernets:
  4.     ens33:
  5.       dhcp4: false
  6.       addresses: [192.168.1.211/24]
  7.       gateway4: 192.168.1.1
  8.       nameservers:
  9.         addresses: [114.114.114.114]
  10.     enp2s0:
  11.       dhcp4: true
  12.   version: 2

 终端输入以下命令让配置生效

sudo netplan apply

互相ping一下看看是否可以ping通

四、整体环境安装

1、下载四个插件

  1. apt-get install socat
  2. apt-get install conntrack
  3. apt-get install ebtables
  4. apt-get install ipset
  5. apt-get install curl

两个机器都要下载 

然后基本就是kubesphere官网的离线安装教程了，网址在这里（有些内容下载很慢，可以找个梯子）：离线安装 (kubesphere.io)也可以选一个更低版本的装。

这边也跟着官网来一遍：

2、制品制作

制品只需要一个虚拟机制作就可以了

先在ubuntu内找个位置建一个文件夹，所有操作文件都放在里面：

  1. cd /
  2. mkdir kk
  3. cd /kk

 然后下载kubeky，输入命令等待下载：

  1. export KKZONE=cn
  2. curl -sfL https://get-kk.kubesphere.io | VERSION=v3.0.7 sh -

 下载完成会自动解压然后是这样的 

如果下载不下来可以下载我这里的kk，版本就是v3.0.7:v3.3的v3.0.7的kk资源

 然后继续按照官网上说的

创建配置文件

vim manifest.yaml

内容为

  1. ---
  2. apiVersion: kubekey.kubesphere.io/v1alpha2
  3. kind: Manifest
  4. metadata:
  5.   name: sample
  6. spec:
  7.   arches:
  8.   - amd64
  9.   operatingSystems:
  10.   - arch: amd64
  11.     type: linux
  12.     id: centos
  13.     version: "7"
  14.     repository:
  15.       iso:
  16.         localPath:
  17.         url: https://github.com/kubesphere/kubekey/releases/download/v3.0.7/centos7-rpms-amd64.iso
  18.   - arch: amd64
  19.     type: linux
  20.     id: ubuntu
  21.     version: "20.04"
  22.     repository:
  23.       iso:
  24.         localPath:
  25.         url: https://github.com/kubesphere/kubekey/releases/download/v3.0.7/ubuntu-20.04-debs-amd64.iso
  26.   kubernetesDistributions:
  27.   - type: kubernetes
  28.     version: v1.22.12
  29.   components:
  30.     helm:
  31.       version: v3.9.0
  32.     cni:
  33.       version: v0.9.1
  34.     etcd:
  35.       version: v3.4.13
  36.    ## For now, if your cluster container runtime is containerd, KubeKey will add a docker 20.10.8 container runtime in the below list.
  37.    ## The reason is KubeKey creates a cluster with containerd by installing a docker first and making kubelet connect the socket file of containerd which docker contained.
  38.     containerRuntimes:
  39.     - type: docker
  40.       version: 20.10.8
  41.     crictl:
  42.       version: v1.24.0
  43.     docker-registry:
  44.       version: "2"
  45.     harbor:
  46.       version: v2.5.3
  47.     docker-compose:
  48.       version: v2.2.2
  49.   images:
  50.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-apiserver:v1.22.12
  51.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-controller-manager:v1.22.12
  52.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-proxy:v1.22.12
  53.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-scheduler:v1.22.12
  54.   - registry.cn-beijing.aliyuncs.com/kubesphereio/pause:3.5
  55.   - registry.cn-beijing.aliyuncs.com/kubesphereio/coredns:1.8.0
  56.   - registry.cn-beijing.aliyuncs.com/kubesphereio/cni:v3.23.2
  57.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-controllers:v3.23.2
  58.   - registry.cn-beijing.aliyuncs.com/kubesphereio/node:v3.23.2
  59.   - registry.cn-beijing.aliyuncs.com/kubesphereio/pod2daemon-flexvol:v3.23.2
  60.   - registry.cn-beijing.aliyuncs.com/kubesphereio/typha:v3.23.2
  61.   - registry.cn-beijing.aliyuncs.com/kubesphereio/flannel:v0.12.0
  62.   - registry.cn-beijing.aliyuncs.com/kubesphereio/provisioner-localpv:3.3.0
  63.   - registry.cn-beijing.aliyuncs.com/kubesphereio/linux-utils:3.3.0
  64.   - registry.cn-beijing.aliyuncs.com/kubesphereio/haproxy:2.3
  65.   - registry.cn-beijing.aliyuncs.com/kubesphereio/nfs-subdir-external-provisioner:v4.0.2
  66.   - registry.cn-beijing.aliyuncs.com/kubesphereio/k8s-dns-node-cache:1.15.12
  67.   - registry.cn-beijing.aliyuncs.com/kubesphereio/ks-installer:v3.3.2
  68.   - registry.cn-beijing.aliyuncs.com/kubesphereio/ks-apiserver:v3.3.2
  69.   - registry.cn-beijing.aliyuncs.com/kubesphereio/ks-console:v3.3.2
  70.   - registry.cn-beijing.aliyuncs.com/kubesphereio/ks-controller-manager:v3.3.2
  71.   - registry.cn-beijing.aliyuncs.com/kubesphereio/ks-upgrade:v3.3.2
  72.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kubectl:v1.22.0
  73.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kubectl:v1.21.0
  74.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kubectl:v1.20.0
  75.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kubefed:v0.8.1
  76.   - registry.cn-beijing.aliyuncs.com/kubesphereio/tower:v0.2.0
  77.   - registry.cn-beijing.aliyuncs.com/kubesphereio/minio:RELEASE.2019-08-07T01-59-21Z
  78.   - registry.cn-beijing.aliyuncs.com/kubesphereio/mc:RELEASE.2019-08-07T23-14-43Z
  79.   - registry.cn-beijing.aliyuncs.com/kubesphereio/snapshot-controller:v4.0.0
  80.   - registry.cn-beijing.aliyuncs.com/kubesphereio/nginx-ingress-controller:v1.1.0
  81.   - registry.cn-beijing.aliyuncs.com/kubesphereio/defaultbackend-amd64:1.4
  82.   - registry.cn-beijing.aliyuncs.com/kubesphereio/metrics-server:v0.4.2
  83.   - registry.cn-beijing.aliyuncs.com/kubesphereio/redis:5.0.14-alpine
  84.   - registry.cn-beijing.aliyuncs.com/kubesphereio/haproxy:2.0.25-alpine
  85.   - registry.cn-beijing.aliyuncs.com/kubesphereio/alpine:3.14
  86.   - registry.cn-beijing.aliyuncs.com/kubesphereio/openldap:1.3.0
  87.   - registry.cn-beijing.aliyuncs.com/kubesphereio/netshoot:v1.0
  88.   - registry.cn-beijing.aliyuncs.com/kubesphereio/cloudcore:v1.9.2
  89.   - registry.cn-beijing.aliyuncs.com/kubesphereio/iptables-manager:v1.9.2
  90.   - registry.cn-beijing.aliyuncs.com/kubesphereio/edgeservice:v0.2.0
  91.   - registry.cn-beijing.aliyuncs.com/kubesphereio/gatekeeper:v3.5.2
  92.   - registry.cn-beijing.aliyuncs.com/kubesphereio/openpitrix-jobs:v3.3.2
  93.   - registry.cn-beijing.aliyuncs.com/kubesphereio/devops-apiserver:ks-v3.3.2
  94.   - registry.cn-beijing.aliyuncs.com/kubesphereio/devops-controller:ks-v3.3.2
  95.   - registry.cn-beijing.aliyuncs.com/kubesphereio/devops-tools:ks-v3.3.2
  96.   - registry.cn-beijing.aliyuncs.com/kubesphereio/ks-jenkins:v3.3.0-2.319.1
  97.   - registry.cn-beijing.aliyuncs.com/kubesphereio/inbound-agent:4.10-2
  98.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-base:v3.2.2
  99.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-nodejs:v3.2.0
  100.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-maven:v3.2.0
  101.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-maven:v3.2.1-jdk11
  102.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-python:v3.2.0
  103.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-go:v3.2.0
  104.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-go:v3.2.2-1.16
  105.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-go:v3.2.2-1.17
  106.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-go:v3.2.2-1.18
  107.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-base:v3.2.2-podman
  108.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-nodejs:v3.2.0-podman
  109.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-maven:v3.2.0-podman
  110.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-maven:v3.2.1-jdk11-podman
  111.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-python:v3.2.0-podman
  112.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-go:v3.2.0-podman
  113.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-go:v3.2.2-1.16-podman
  114.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-go:v3.2.2-1.17-podman
  115.   - registry.cn-beijing.aliyuncs.com/kubesphereio/builder-go:v3.2.2-1.18-podman
  116.   - registry.cn-beijing.aliyuncs.com/kubesphereio/s2ioperator:v3.2.1
  117.   - registry.cn-beijing.aliyuncs.com/kubesphereio/s2irun:v3.2.0
  118.   - registry.cn-beijing.aliyuncs.com/kubesphereio/s2i-binary:v3.2.0
  119.   - registry.cn-beijing.aliyuncs.com/kubesphereio/tomcat85-java11-centos7:v3.2.0
  120.   - registry.cn-beijing.aliyuncs.com/kubesphereio/tomcat85-java11-runtime:v3.2.0
  121.   - registry.cn-beijing.aliyuncs.com/kubesphereio/tomcat85-java8-centos7:v3.2.0
  122.   - registry.cn-beijing.aliyuncs.com/kubesphereio/tomcat85-java8-runtime:v3.2.0
  123.   - registry.cn-beijing.aliyuncs.com/kubesphereio/java-11-centos7:v3.2.0
  124.   - registry.cn-beijing.aliyuncs.com/kubesphereio/java-8-centos7:v3.2.0
  125.   - registry.cn-beijing.aliyuncs.com/kubesphereio/java-8-runtime:v3.2.0
  126.   - registry.cn-beijing.aliyuncs.com/kubesphereio/java-11-runtime:v3.2.0
  127.   - registry.cn-beijing.aliyuncs.com/kubesphereio/nodejs-8-centos7:v3.2.0
  128.   - registry.cn-beijing.aliyuncs.com/kubesphereio/nodejs-6-centos7:v3.2.0
  129.   - registry.cn-beijing.aliyuncs.com/kubesphereio/nodejs-4-centos7:v3.2.0
  130.   - registry.cn-beijing.aliyuncs.com/kubesphereio/python-36-centos7:v3.2.0
  131.   - registry.cn-beijing.aliyuncs.com/kubesphereio/python-35-centos7:v3.2.0
  132.   - registry.cn-beijing.aliyuncs.com/kubesphereio/python-34-centos7:v3.2.0
  133.   - registry.cn-beijing.aliyuncs.com/kubesphereio/python-27-centos7:v3.2.0
  134.   - registry.cn-beijing.aliyuncs.com/kubesphereio/argocd:v2.3.3
  135.   - registry.cn-beijing.aliyuncs.com/kubesphereio/argocd-applicationset:v0.4.1
  136.   - registry.cn-beijing.aliyuncs.com/kubesphereio/dex:v2.30.2
  137.   - registry.cn-beijing.aliyuncs.com/kubesphereio/redis:6.2.6-alpine
  138.   - registry.cn-beijing.aliyuncs.com/kubesphereio/configmap-reload:v0.5.0
  139.   - registry.cn-beijing.aliyuncs.com/kubesphereio/prometheus:v2.34.0
  140.   - registry.cn-beijing.aliyuncs.com/kubesphereio/prometheus-config-reloader:v0.55.1
  141.   - registry.cn-beijing.aliyuncs.com/kubesphereio/prometheus-operator:v0.55.1
  142.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-rbac-proxy:v0.11.0
  143.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-state-metrics:v2.5.0
  144.   - registry.cn-beijing.aliyuncs.com/kubesphereio/node-exporter:v1.3.1
  145.   - registry.cn-beijing.aliyuncs.com/kubesphereio/alertmanager:v0.23.0
  146.   - registry.cn-beijing.aliyuncs.com/kubesphereio/thanos:v0.25.2
  147.   - registry.cn-beijing.aliyuncs.com/kubesphereio/grafana:8.3.3
  148.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-rbac-proxy:v0.8.0
  149.   - registry.cn-beijing.aliyuncs.com/kubesphereio/notification-manager-operator:v1.4.0
  150.   - registry.cn-beijing.aliyuncs.com/kubesphereio/notification-manager:v1.4.0
  151.   - registry.cn-beijing.aliyuncs.com/kubesphereio/notification-tenant-sidecar:v3.2.0
  152.   - registry.cn-beijing.aliyuncs.com/kubesphereio/elasticsearch-curator:v5.7.6
  153.   - registry.cn-beijing.aliyuncs.com/kubesphereio/elasticsearch-oss:6.8.22
  154.   - registry.cn-beijing.aliyuncs.com/kubesphereio/fluentbit-operator:v0.13.0
  155.   - registry.cn-beijing.aliyuncs.com/kubesphereio/docker:19.03
  156.   - registry.cn-beijing.aliyuncs.com/kubesphereio/fluent-bit:v1.8.11
  157.   - registry.cn-beijing.aliyuncs.com/kubesphereio/log-sidecar-injector:1.1
  158.   - registry.cn-beijing.aliyuncs.com/kubesphereio/filebeat:6.7.0
  159.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-events-operator:v0.4.0
  160.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-events-exporter:v0.4.0
  161.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-events-ruler:v0.4.0
  162.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-auditing-operator:v0.2.0
  163.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kube-auditing-webhook:v0.2.0
  164.   - registry.cn-beijing.aliyuncs.com/kubesphereio/pilot:1.11.1
  165.   - registry.cn-beijing.aliyuncs.com/kubesphereio/proxyv2:1.11.1
  166.   - registry.cn-beijing.aliyuncs.com/kubesphereio/jaeger-operator:1.27
  167.   - registry.cn-beijing.aliyuncs.com/kubesphereio/jaeger-agent:1.27
  168.   - registry.cn-beijing.aliyuncs.com/kubesphereio/jaeger-collector:1.27
  169.   - registry.cn-beijing.aliyuncs.com/kubesphereio/jaeger-query:1.27
  170.   - registry.cn-beijing.aliyuncs.com/kubesphereio/jaeger-es-index-cleaner:1.27
  171.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kiali-operator:v1.38.1
  172.   - registry.cn-beijing.aliyuncs.com/kubesphereio/kiali:v1.38
  173.   - registry.cn-beijing.aliyuncs.com/kubesphereio/busybox:1.31.1
  174.   - registry.cn-beijing.aliyuncs.com/kubesphereio/nginx:1.14-alpine
  175.   - registry.cn-beijing.aliyuncs.com/kubesphereio/wget:1.0
  176.   - registry.cn-beijing.aliyuncs.com/kubesphereio/hello:plain-text
  177.   - registry.cn-beijing.aliyuncs.com/kubesphereio/wordpress:4.8-apache
  178.   - registry.cn-beijing.aliyuncs.com/kubesphereio/hpa-example:latest
  179.   - registry.cn-beijing.aliyuncs.com/kubesphereio/fluentd:v1.4.2-2.0
  180.   - registry.cn-beijing.aliyuncs.com/kubesphereio/perl:latest
  181.   - registry.cn-beijing.aliyuncs.com/kubesphereio/examples-bookinfo-productpage-v1:1.16.2
  182.   - registry.cn-beijing.aliyuncs.com/kubesphereio/examples-bookinfo-reviews-v1:1.16.2
  183.   - registry.cn-beijing.aliyuncs.com/kubesphereio/examples-bookinfo-reviews-v2:1.16.2
  184.   - registry.cn-beijing.aliyuncs.com/kubesphereio/examples-bookinfo-details-v1:1.16.2
  185.   - registry.cn-beijing.aliyuncs.com/kubesphereio/examples-bookinfo-ratings-v1:1.16.3
  186.   - registry.cn-beijing.aliyuncs.com/kubesphereio/scope:1.13.0

但要注意，这里有两个github网址，如果直接用ubuntu下载速度超级慢，可以在主机复制网址下载之后放入虚拟机中。

 下载好的文件在/kk目录中创建一个iso文件夹然后放入

manifest.yaml配置文件修改，将两个url的内容删除，localPath换为iso本地目录，然后保存

  1.     type: linux
  2.     id: centos
  3.     version: "7"
  4.     repository:
  5.       iso:
  6.         localPath: /kk/iso/centos7-rpms-amd64.iso
  7.         url: 
  8.   - arch: amd64
  9.     type: linux
  10.     id: ubuntu
  11.     version: "20.04"
  12.     repository:
  13.       iso:
  14.         localPath: /kk/iso/ubuntu-20.04-debs-amd64.iso
  15.         url: 
  16.   kubernetesDistributions:

 这里也提供一下两个iso:

kubesphere离线安装v3.3的centos7iso

kubesphere离线安装v3.3的ubuntu2020iso

然后就可以下载了，执行以下命令

  1. chmod +x ./manifest.yaml
  2. chmod +x ./kk
  3. export KKZONE=cn
  4. ./kk artifact export -m manifest.yaml -o kubesphere.tar.gz

等待好长时间后就可以看到打包完成了

        可以将kk文件和刚下载打包好的kubesphere.tar.gz移动到需要离线安装的集群机器上。然后进行kubesphere安装了。我这边就继续在下载机器上安装了。

3、离线安装集群

        执行以下命令创建安装的配置文件

./kk create config --with-kubesphere v3.3.2 --with-kubernetes v1.22.12 -f config-sample.yaml

然后根据两个虚拟机集群的情况修改配置文件

gedit config-sample.yaml

  把圈起来的地方改成自己集群的配置

特别注意这一块

  1. network:
  2.     plugin: calico
  3.     kubePodsCIDR: 10.233.64.0/18
  4.     kubeServiceCIDR: 10.233.0.0/18
  5.     multusCNI:
  6.       enabled: false
  7.   registry:
  8.     # 这里加一个type然后写harbor
  9.     type: harbor
  10.     privateRegistry: ""
  11.     namespaceOverride: ""
  12.     registryMirrors: []
  13.     insecureRegistries: []
  14.   addons: []

保存文档后执行以下命令（确保要安装的机器都能ping通）：

./kk init registry -f config-sample.yaml -a kubesphere.tar.gz

有可能执行会报错，多执行几次，成功是这样的：

 然后用直接访问harbor安装IP查看是否安装成功，我这边就是直接访问192.168.1.211，可能会报不安全，点直接访问就可以了

之后需要用脚本来设置harbor

  1. mkdir /kk/harborSh
  2. cd /kk/harborSh
  3. vim create_project_harbor.sh

 然后给sh脚本添加以下内容并保存

  1. #!/usr/bin/env bash
  2.  
  3. # Copyright 2018 The KubeSphere Authors.
  4. #
  5. # Licensed under the Apache License, Version 2.0 (the "License");
  6. # you may not use this file except in compliance with the License.
  7. # You may obtain a copy of the License at
  8. #
  9. #     http://www.apache.org/licenses/LICENSE-2.0
  10. #
  11. # Unless required by applicable law or agreed to in writing, software
  12. # distributed under the License is distributed on an "AS IS" BASIS,
  13. # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  14. # See the License for the specific language governing permissions and
  15. # limitations under the License.
  16.  
  17. url="https://dockerhub.kubekey.local"  #修改url的值为https://dockerhub.kubekey.local
  18. user="admin"
  19. passwd="Harbor12345"
  20.  
  21. harbor_projects=(library
  22.     kubesphereio
  23.     kubesphere
  24.     argoproj
  25.     calico
  26.     coredns
  27.     openebs
  28.     csiplugin
  29.     minio
  30.     mirrorgooglecontainers
  31.     osixia
  32.     prom
  33.     thanosio
  34.     jimmidyson
  35.     grafana
  36.     elastic
  37.     istio
  38.     jaegertracing
  39.     jenkins
  40.     weaveworks
  41.     openpitrix
  42.     joosthofman
  43.     nginxdemos
  44.     fluent
  45.     kubeedge
  46.     openpolicyagent
  47. )
  48.  
  49. for project in "${harbor_projects[@]}"; do
  50.     echo "creating $project"
  51.     curl -u "${user}:${passwd}" -X POST -H "Content-Type: application/json" "${url}/api/v2.0/projects" -d "{ \"project_name\": \"${project}\", \"public\": true}" -k #curl命令末尾加上 -k
  52. done

 然后赋予权限并执行脚本

  1. chmod +x create_project_harbor.sh
  2. ./create_project_harbor.sh

 执行成功后可以看到

也可以登录harbor去看一看成功没成功，账号admin，密码Harbor12345，可以看到很多镜像已经添加成功了

再次执行以下命令修改集群配置文件，给namespaceOverride增加值

  1. cd /kk
  2. gedit config-sample.yaml

其他不用改，registry下面要添加下面的内容 

  1. network:
  2.     plugin: calico
  3.     kubePodsCIDR: 10.233.64.0/18
  4.     kubeServiceCIDR: 10.233.0.0/18
  5.     ## multus support. https://github.com/k8snetworkplumbingwg/multus-cni
  6.     multusCNI:
  7.       enabled: false
  8.   registry:
  9.     type: harbor
  10.     auths:
  11.       "dockerhub.kubekey.local":
  12.         username: admin
  13.         password: Harbor12345
  14.     privateRegistry: "dockerhub.kubekey.local"
  15.     namespaceOverride: "kubesphereio"
  16.     registryMirrors: []
  17.     insecureRegistries: []
  18.   addons: []

 然后执行命令

./kk create cluster -f config-sample.yaml -a kubesphere.tar.gz --with-packages

中途需要输入yes同意安装。

如果安装中途出现下载或者对应依赖包版本不正确的情况，那就看看报错信息是缺少什么依赖，然后在manifest.yaml文件中写入，然后重新制作制品再来安装。

等待很长时间后

然后访问地址192.168.1.211:30880，出现网页，就是安装成功了。

账号admin，密码P@88w0rd，登录成功后是这样的

 

五、安装完成后配置调整

1、kubesphere链接harbor

将 nodelocaldns 解析都转发给 coredns

点击kubesphere平台的平台管理，然后点击集群管理

然后依次点击配置-配置字典-搜索kube-system-点击进入nodelocaldns 

 点击更多操作-编辑设置

 点击修改图标

滚动到最下面，然后修改内容如下，将forward后面的内容修改为 . 10.233.0.3【注意空格】，然后点击确认

在 coredns 中添加主机记录

在你的安装harbor的机器中输入以下命令，我这边就是211下操作

kubectl edit cm coredns -n kube-system

在这个位置加入红框中的内容并保存，ip地址就是harbor的地址，记得保存

  1. hosts  {
  2.     192.168.1.211  dockerhub.kubekey.local
  3.     fallthrough
  4. }

添加证书

在你的安装harbor的机器中输入以下命令，我这边就是211下操作

  1. cd /etc/docker/certs.d/dockerhub.kubekey.local
  2. cat ca.crt

然后将文本中的内容全部复制

然后创建配置字典，点击配置-配置字典，搜索kubesphere-system-点击创建

 然后输入对应信息点击下一步

  1. harbor4shl-ca
  2. kubesphere-system

 然后名称设置为ca.crt，内容为刚才终端中复制的证书，点击创建对号然后点击创建

点击应用负载-工作负载-搜索kubesphere-system-点击ks-apiserver

 点击更多操作-编辑设置

点击存储-挂载配置字典或保密字典

 然后输入以下配置和选项

/etc/ssl/certs/ca.crt

点击对号，并点击确认

修改完后平台可能会掉线，然后等待平台重启再进入就行了

也可以去测试一下

随便建一个保密字典，信息随便填然后点下一步

类型选择镜像服务信息，镜像服务地址选择https://，输入harbor地址，输入登录harbor的用户名和密码，然后点击验证。出现镜像服务验证通过即为成功。

2、解除kubesphere端口号限制

kubesphere端口号默认限制了30000-32767，只要稍微配置就能解除了

在kubesphere部署的机器终端上输入命令

vim /etc/kubernetes/manifests/kube-apiserver.yaml

在目标行插入以下字段并保存退出

- --service-node-port-range=1-65535

然后在终端重启一下服务让配置生效

systemctl restart kubelet.service

到此kubesphere整体安装并配置就完成了，出错可以留言。

本文内容由网友自发贡献，转载请注明出处：https://www.wpsshop.cn/w/Monodyee/article/detail/730618
推荐阅读
相关标签

Copyright © 2003-2013 www.wpsshop.cn 版权所有，并保留所有权利。

  

闽ICP备14008679号