In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-30 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)05/31 Report--
This article mainly explains "how to deploy ARM64 offline Kubernetes and KubeSphere". The content of the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to deploy Kubernetes and KubeSphere offline in ARM64".
Environment preparation node
The operating systems supported by kubeSphere include:
Ubuntu 16.04, 18.04
Debian Buster, Stretch
CentOS/RHEL 7
SUSE Linux Enterprise Server 15
OpenEuler
Here, take an openEuler 20.0964bit as an example: | name | ip | role | |-| node1 | 172.169.102.249 | etcd, master, worker |
Ensure that the required dependent software (sudo curl openssl ebtables socat ipset conntrack docker) is installed on the machine
For specific environmental requirements, please see: https://github.com/kubesphere/kubekey/tree/release-1.0#requirements-and-recommendations
Please refer to the KubeSphere official documentation for multi-node installation.
Suggestion: the operating system with all dependent software installed can be used as a system image to avoid installing dependent software on each machine, which can improve the efficiency of delivery and deployment and avoid dependency problems.
Tip: if you use centos7.x or ubuntu18.04, you can choose to initialize the machine using the kk command. After decompressing the installation package and creating the configuration file (see below for the creation method), you can initialize the node by executing the following command:. / kk init os-s. / dependencies-f config-example.yaml if you encounter dependency problems with this command, you can install the relevant dependency software on your own.
Image warehouse
Use harbor or other third-party image repositories.
Tip: you can use the kk command to automatically create a self-signed image repository for testing. Note, make sure that registry:2 exists on the current machine. If not, you can import it from the decompressed package kubesphere-images-v3.0.0/registry.tar. Import command: docker load < registry.tar. Create a self-signed image repository for testing:. / kk init os-f config-example.yaml-- add-images-repo Note: the image repository started by kk is port 443. please make sure that all machines can access port 443 of the current machine. The mirrored data is stored locally / mnt/registry (it is recommended to mount the disk separately).
Download the installation package:
Tip: the installation package contains only Kubernetes + KubeSphere-core images. If you need more component arm64 images, you can compile and build them yourself.
# md5: 3ad57823faf2dfe945e2fe3dcfd4ace9curl-Ok https://kubesphere-installer.pek3b.qingstor.com/offline/v3.0.0/kubesphere-core-v3.0.0-offline-linux-arm64.tar.gz installation steps: 1. Create a cluster profile
After decompressing the installation package, enter kubesphere-core-v3.0.0-offline-linux-arm64.
. / kk create config
Modify the generated configuration file config-sample.yaml according to the actual environment information, or customize the profile path using the-f parameter. For more information on the usage of kk, please see: https://github.com/kubesphere/kubekey
Be sure to enter the correct private warehouse address privateRegistry (if you have prepared a private warehouse, you can set it to an existing warehouse address. If you use kk to create a private warehouse, this parameter is set to: dockerhub.kubekey.local)
ApiVersion: kubekey.kubesphere.io/v1alpha1kind: Clustermetadata: name: samplespec: hosts: # Note that the specified node arch is arm64-{name: node1, address: 172.169.102.249, internalAddress: 172.169.102.249, password: Qcloud@123 Arch: arm64} roleGroups: etcd:-node1 master:-node1 worker:-node1 controlPlaneEndpoint: domain: lb.kubesphere.local address: "" port: 6443 kubernetes: version: v1.17.9 imageRepo: kubesphere clusterName: cluster.local network: plugin: calico kubePodsCIDR: 10.233.64.0 18 kubeServiceCIDR: 10.233.0.0That 18 registry: registryMirrors: [] insecureRegistries: [] PrivateRegistry: dockerhub.kubekey.local addons: [] 2. Import Mirror
Enter kubesphere-all-v3.0.0-offline-linux-arm64/kubesphere-images-v3.0.0 and use offline-installation-tool.sh to import the image into the previously prepared repository:
# enter the address of the image warehouse after the script. / offline-installation-tool.sh-l images-list-v3.0.0.txt-d kubesphere-images-r dockerhub.kubekey.local3. After performing the above preparations for installation # and checking the configuration file again, perform the installation. . / kk create cluster-f config-sample.yaml-- with-kubesphere to view the results
Thank you for your reading, the above is the content of "how to deploy Kubernetes and KubeSphere offline in ARM64". After the study of this article, I believe you have a deeper understanding of how to deploy Kubernetes and KubeSphere offline in ARM64, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.