sealos4.3.5安装手册（二）追加节点

已于 2023-10-17 15:04:26 修改
阅读量350 收藏
点赞数
文章标签： k8s 运维开发 运维
于 2023-10-17 13:39:11 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/westlifeml/article/details/133822698
版权

接上一篇sealos4.3.5安装手册（一）部署集群中我们讲解了集群的部署，这篇中我们将继续完善集群，追加 2个主节点和1个子节点

1. 查看sealos帮助，找到添加命令和参数

查看命令

[root@k8s-master1 ~]# sealos -h
sealos is a Kubernetes distribution, a unified OS to manage cloud native applications.

Cluster Management Commands:
  apply         Run cloud images within a kubernetes cluster with Clusterfile
  cert          update Kubernetes API server's cert
  run           Run cloud native applications with ease, with or without a existing cluster
  reset         Reset all, everything in the cluster
  status        state of sealos

Node Management Commands:
  add           Add nodes into cluster
  delete        Remove nodes from cluster

Remote Operation Commands:
  exec          Execute shell command or script on specified nodes
  scp           Copy file to remote on specified nodes

Experimental Commands:
  registry      registry related

Container and Image Commands:
  build         Build an image using instructions in a Containerfile or Kubefile
  create        Create a cluster without running the CMD, for inspecting image
  diff          Inspect changes to the object's file systems
  inspect       Inspect the configuration of a container or image
  images        List images in local storage
  load          Load image(s) from archive file
  login         Login to a container registry
  logout        Logout of a container registry
  manifest      Manipulate manifest lists and image indexes
  merge         merge multiple images into one
  pull          Pull images from the specified location
  push          Push an image to a specified destination
  rmi           Remove one or more images from local storage
  save          Save image into archive file
  tag           Add an additional name to a local image

Other Commands:
  completion    Generate the autocompletion script for the specified shell
  docs          generate API reference
  env           prints out all the environment information in use by sealos
  gen           generate a Clusterfile with all default settings
  version       Print version info

Use "sealos <command> --help" for more information about a given command.

查看添加命令的参数

[root@k8s-master1 ~]# sealos add -h
Add nodes into cluster

Examples:

add to nodes :
	sealos add --nodes x.x.x.x

add to default cluster:
	sealos add --masters x.x.x.x --nodes x.x.x.x
	sealos add --masters x.x.x.x-x.x.x.y --nodes x.x.x.x-x.x.x.y

add with different ssh setting:
	sealos add --masters x.x.x.x --nodes x.x.x.x --passwd your_diff_passwd
Please note that the masters and nodes added in one command should have the save password.

Options:
    --cluster='default':
	name of cluster to applied join action

    --masters='':
	masters to be joined

    --nodes='':
	nodes to be joined

    -p, --passwd='':
	use given password to authenticate with

    -i, --pk='/root/.ssh/id_rsa':
	selects a file from which the identity (private key) for public key authentication is read

    --pk-passwd='':
	passphrase for decrypting a PEM encoded private key

    --port=22:
	port to connect to on the remote host

    -u, --user='':
	username to authenticate as

Usage:
  sealos add [flags] [options]

Use "sealos options" for a list of global command-line options (applies to all commands).

2. 添加节点

根据帮忙提示，添加42和43主节点，47子节点
有密码的需要添加 --passwd

[root@k8s-master1 ~]# sealos add --masters 192.168.1.42-192.168.1.43 --nodes 192.168.1.47 --passwd 'kgb007'
2023-10-14T10:51:14 info start to scale this cluster
2023-10-14T10:51:14 info Executing pipeline JoinCheck in ScaleProcessor.
2023-10-14T10:51:14 info checker:hostname [192.168.1.41:22 192.168.1.42:22 192.168.1.43:22 192.168.1.47:22]
2023-10-14T10:51:14 info checker:timeSync [192.168.1.41:22 192.168.1.42:22 192.168.1.43:22 192.168.1.47:22]
2023-10-14T10:51:15 info Executing pipeline PreProcess in ScaleProcessor.
2023-10-14T10:51:15 info Executing pipeline PreProcessImage in ScaleProcessor.
2023-10-14T10:51:15 info Executing pipeline RunConfig in ScaleProcessor.
2023-10-14T10:51:15 info Executing pipeline MountRootfs in ScaleProcessor.
2023-10-14T10:51:51 info Executing pipeline Bootstrap in ScaleProcessorit/s)          
192.168.1.42:22	 INFO [2023-10-14 10:51:51] >> Check port kubelet port 10249..10259, reserved port 5050..5054 inuse. Please wait... 
192.168.1.47:22	 INFO [2023-10-14 10:51:51] >> Check port kubelet port 10249..10259, reserved port 5050..5054 inuse. Please wait... 
192.168.1.43:22	 INFO [2023-10-14 10:51:51] >> Check port kubelet port 10249..10259, reserved port 5050..5054 inuse. Please wait... 
192.168.1.42:22	which: no docker in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin)
192.168.1.42:22	 WARN [2023-10-14 10:51:52] >> Replace disable_apparmor = false to disable_apparmor = true 
192.168.1.42:22	 INFO [2023-10-14 10:51:52] >> check root,port,cri success 
192.168.1.47:22	which: no docker in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin)
192.168.1.47:22	 WARN [2023-10-14 10:51:52] >> Replace disable_apparmor = false to disable_apparmor = true 
192.168.1.47:22	 INFO [2023-10-14 10:51:52] >> check root,port,cri success 
192.168.1.43:22	which: no docker in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin)
192.168.1.43:22	 WARN [2023-10-14 10:51:52] >> Replace disable_apparmor = false to disable_apparmor = true 
192.168.1.43:22	 INFO [2023-10-14 10:51:52] >> check root,port,cri success 
192.168.1.47:22	2023-10-14T10:51:52 info domain sealos.hub:192.168.1.41 append success
192.168.1.42:22	2023-10-14T10:51:52 info domain sealos.hub:192.168.1.41 append success
192.168.1.43:22	2023-10-14T10:51:52 info domain sealos.hub:192.168.1.41 append success
192.168.1.42:22	Created symlink from /etc/systemd/system/multi-user.target.wants/containerd.service to /etc/systemd/system/containerd.service.
192.168.1.43:22	Created symlink from /etc/systemd/system/multi-user.target.wants/containerd.service to /etc/systemd/system/containerd.service.
192.168.1.47:22	Created symlink from /etc/systemd/system/multi-user.target.wants/containerd.service to /etc/systemd/system/containerd.service.
192.168.1.47:22	 INFO [2023-10-14 10:51:57] >> Health check containerd! 
192.168.1.47:22	 INFO [2023-10-14 10:51:57] >> containerd is running 
192.168.1.47:22	 INFO [2023-10-14 10:51:57] >> init containerd success 
192.168.1.42:22	 INFO [2023-10-14 10:51:57] >> Health check containerd! 
192.168.1.42:22	 INFO [2023-10-14 10:51:57] >> containerd is running 
192.168.1.42:22	 INFO [2023-10-14 10:51:57] >> init containerd success 
192.168.1.43:22	 INFO [2023-10-14 10:51:57] >> Health check containerd! 
192.168.1.43:22	 INFO [2023-10-14 10:51:57] >> containerd is running 
192.168.1.43:22	 INFO [2023-10-14 10:51:57] >> init containerd success 
192.168.1.47:22	Created symlink from /etc/systemd/system/multi-user.target.wants/image-cri-shim.service to /etc/systemd/system/image-cri-shim.service.
192.168.1.42:22	Created symlink from /etc/systemd/system/multi-user.target.wants/image-cri-shim.service to /etc/systemd/system/image-cri-shim.service.
192.168.1.47:22	 INFO [2023-10-14 10:51:58] >> Health check image-cri-shim! 
192.168.1.47:22	 INFO [2023-10-14 10:51:58] >> image-cri-shim is running 
192.168.1.47:22	 INFO [2023-10-14 10:51:58] >> init shim success 
192.168.1.43:22	Created symlink from /etc/systemd/system/multi-user.target.wants/image-cri-shim.service to /etc/systemd/system/image-cri-shim.service.
192.168.1.47:22	127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
192.168.1.47:22	::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.42:22	 INFO [2023-10-14 10:51:58] >> Health check image-cri-shim! 
192.168.1.42:22	 INFO [2023-10-14 10:51:58] >> image-cri-shim is running 
192.168.1.42:22	 INFO [2023-10-14 10:51:58] >> init shim success 
192.168.1.42:22	127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
192.168.1.42:22	::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.43:22	 INFO [2023-10-14 10:51:58] >> Health check image-cri-shim! 
192.168.1.43:22	 INFO [2023-10-14 10:51:58] >> image-cri-shim is running 
192.168.1.43:22	 INFO [2023-10-14 10:51:58] >> init shim success 
192.168.1.43:22	127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
192.168.1.43:22	::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.42:22	Removed symlink /etc/systemd/system/multi-user.target.wants/firewalld.service.
192.168.1.42:22	Removed symlink /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.
192.168.1.47:22	Removed symlink /etc/systemd/system/multi-user.target.wants/firewalld.service.
192.168.1.47:22	Removed symlink /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.
192.168.1.42:22	* Applying /usr/lib/sysctl.d/00-system.conf ...
192.168.1.42:22	net.bridge.bridge-nf-call-ip6tables = 0
192.168.1.42:22	net.bridge.bridge-nf-call-iptables = 0
192.168.1.42:22	net.bridge.bridge-nf-call-arptables = 0
192.168.1.42:22	* Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
192.168.1.42:22	kernel.yama.ptrace_scope = 0
192.168.1.42:22	* Applying /usr/lib/sysctl.d/50-default.conf ...
192.168.1.42:22	kernel.sysrq = 16
192.168.1.42:22	kernel.core_uses_pid = 1
192.168.1.42:22	kernel.kptr_restrict = 1
192.168.1.42:22	net.ipv4.conf.default.rp_filter = 1
192.168.1.42:22	net.ipv4.conf.all.rp_filter = 1
192.168.1.42:22	net.ipv4.conf.default.accept_source_route = 0
192.168.1.42:22	net.ipv4.conf.all.accept_source_route = 0
192.168.1.42:22	net.ipv4.conf.default.promote_secondaries = 1
192.168.1.42:22	net.ipv4.conf.all.promote_secondaries = 1
192.168.1.42:22	fs.protected_hardlinks = 1
192.168.1.42:22	fs.protected_symlinks = 1
192.168.1.42:22	* Applying /etc/sysctl.d/99-sysctl.conf ...
192.168.1.42:22	fs.file-max = 1048576 # sealos
192.168.1.42:22	net.bridge.bridge-nf-call-ip6tables = 1 # sealos
192.168.1.42:22	net.bridge.bridge-nf-call-iptables = 1 # sealos
192.168.1.42:22	net.core.somaxconn = 65535 # sealos
192.168.1.42:22	net.ipv4.conf.all.rp_filter = 0 # sealos
192.168.1.42:22	net.ipv4.ip_forward = 1 # sealos
192.168.1.42:22	net.ipv4.ip_local_port_range = 1024 65535 # sealos
192.168.1.42:22	net.ipv4.tcp_keepalive_intvl = 30 # sealos
192.168.1.42:22	net.ipv4.tcp_keepalive_time = 600 # sealos
192.168.1.42:22	net.ipv4.vs.conn_reuse_mode = 0 # sealos
192.168.1.42:22	net.ipv4.vs.conntrack = 1 # sealos
192.168.1.42:22	net.ipv6.conf.all.forwarding = 1 # sealos
192.168.1.42:22	* Applying /etc/sysctl.conf ...
192.168.1.42:22	fs.file-max = 1048576 # sealos
192.168.1.42:22	net.bridge.bridge-nf-call-ip6tables = 1 # sealos
192.168.1.42:22	net.bridge.bridge-nf-call-iptables = 1 # sealos
192.168.1.42:22	net.core.somaxconn = 65535 # sealos
192.168.1.42:22	net.ipv4.conf.all.rp_filter = 0 # sealos
192.168.1.42:22	net.ipv4.ip_forward = 1 # sealos
192.168.1.42:22	net.ipv4.ip_local_port_range = 1024 65535 # sealos
192.168.1.42:22	net.ipv4.tcp_keepalive_intvl = 30 # sealos
192.168.1.42:22	net.ipv4.tcp_keepalive_time = 600 # sealos
192.168.1.42:22	net.ipv4.vs.conn_reuse_mode = 0 # sealos
192.168.1.42:22	net.ipv4.vs.conntrack = 1 # sealos
192.168.1.42:22	net.ipv6.conf.all.forwarding = 1 # sealos
192.168.1.47:22	* Applying /usr/lib/sysctl.d/00-system.conf ...
192.168.1.47:22	net.bridge.bridge-nf-call-ip6tables = 0
192.168.1.47:22	net.bridge.bridge-nf-call-iptables = 0
192.168.1.47:22	net.bridge.bridge-nf-call-arptables = 0
192.168.1.47:22	* Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
192.168.1.47:22	kernel.yama.ptrace_scope = 0
192.168.1.47:22	* Applying /usr/lib/sysctl.d/50-default.conf ...
192.168.1.47:22	kernel.sysrq = 16
192.168.1.47:22	kernel.core_uses_pid = 1
192.168.1.47:22	kernel.kptr_restrict = 1
192.168.1.47:22	net.ipv4.conf.default.rp_filter = 1
192.168.1.47:22	net.ipv4.conf.all.rp_filter = 1
192.168.1.47:22	net.ipv4.conf.default.accept_source_route = 0
192.168.1.47:22	net.ipv4.conf.all.accept_source_route = 0
192.168.1.47:22	net.ipv4.conf.default.promote_secondaries = 1
192.168.1.47:22	net.ipv4.conf.all.promote_secondaries = 1
192.168.1.47:22	fs.protected_hardlinks = 1
192.168.1.47:22	fs.protected_symlinks = 1
192.168.1.47:22	* Applying /etc/sysctl.d/99-sysctl.conf ...
192.168.1.47:22	fs.file-max = 1048576 # sealos
192.168.1.47:22	net.bridge.bridge-nf-call-ip6tables = 1 # sealos
192.168.1.47:22	net.bridge.bridge-nf-call-iptables = 1 # sealos
192.168.1.47:22	net.core.somaxconn = 65535 # sealos
192.168.1.47:22	net.ipv4.conf.all.rp_filter = 0 # sealos
192.168.1.47:22	net.ipv4.ip_forward = 1 # sealos
192.168.1.47:22	net.ipv4.ip_local_port_range = 1024 65535 # sealos
192.168.1.47:22	net.ipv4.tcp_keepalive_intvl = 30 # sealos
192.168.1.47:22	net.ipv4.tcp_keepalive_time = 600 # sealos
192.168.1.47:22	net.ipv4.vs.conn_reuse_mode = 0 # sealos
192.168.1.47:22	net.ipv4.vs.conntrack = 1 # sealos
192.168.1.47:22	net.ipv6.conf.all.forwarding = 1 # sealos
192.168.1.47:22	* Applying /etc/sysctl.conf ...
192.168.1.47:22	fs.file-max = 1048576 # sealos
192.168.1.47:22	net.bridge.bridge-nf-call-ip6tables = 1 # sealos
192.168.1.47:22	net.bridge.bridge-nf-call-iptables = 1 # sealos
192.168.1.47:22	net.core.somaxconn = 65535 # sealos
192.168.1.47:22	net.ipv4.conf.all.rp_filter = 0 # sealos
192.168.1.47:22	net.ipv4.ip_forward = 1 # sealos
192.168.1.47:22	net.ipv4.ip_local_port_range = 1024 65535 # sealos
192.168.1.47:22	net.ipv4.tcp_keepalive_intvl = 30 # sealos
192.168.1.47:22	net.ipv4.tcp_keepalive_time = 600 # sealos
192.168.1.47:22	net.ipv4.vs.conn_reuse_mode = 0 # sealos
192.168.1.47:22	net.ipv4.vs.conntrack = 1 # sealos
192.168.1.47:22	net.ipv6.conf.all.forwarding = 1 # sealos
192.168.1.43:22	Removed symlink /etc/systemd/system/multi-user.target.wants/firewalld.service.
192.168.1.43:22	Removed symlink /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.
192.168.1.43:22	* Applying /usr/lib/sysctl.d/00-system.conf ...
192.168.1.43:22	net.bridge.bridge-nf-call-ip6tables = 0
192.168.1.43:22	net.bridge.bridge-nf-call-iptables = 0
192.168.1.43:22	net.bridge.bridge-nf-call-arptables = 0
192.168.1.43:22	* Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
192.168.1.43:22	kernel.yama.ptrace_scope = 0
192.168.1.43:22	* Applying /usr/lib/sysctl.d/50-default.conf ...
192.168.1.43:22	kernel.sysrq = 16
192.168.1.43:22	kernel.core_uses_pid = 1
192.168.1.43:22	kernel.kptr_restrict = 1
192.168.1.43:22	net.ipv4.conf.default.rp_filter = 1
192.168.1.43:22	net.ipv4.conf.all.rp_filter = 1
192.168.1.43:22	net.ipv4.conf.default.accept_source_route = 0
192.168.1.43:22	net.ipv4.conf.all.accept_source_route = 0
192.168.1.43:22	net.ipv4.conf.default.promote_secondaries = 1
192.168.1.43:22	net.ipv4.conf.all.promote_secondaries = 1
192.168.1.43:22	fs.protected_hardlinks = 1
192.168.1.43:22	fs.protected_symlinks = 1
192.168.1.43:22	* Applying /etc/sysctl.d/99-sysctl.conf ...
192.168.1.43:22	fs.file-max = 1048576 # sealos
192.168.1.43:22	net.bridge.bridge-nf-call-ip6tables = 1 # sealos
192.168.1.43:22	net.bridge.bridge-nf-call-iptables = 1 # sealos
192.168.1.43:22	net.core.somaxconn = 65535 # sealos
192.168.1.43:22	net.ipv4.conf.all.rp_filter = 0 # sealos
192.168.1.43:22	net.ipv4.ip_forward = 1 # sealos
192.168.1.43:22	net.ipv4.ip_local_port_range = 1024 65535 # sealos
192.168.1.43:22	net.ipv4.tcp_keepalive_intvl = 30 # sealos
192.168.1.43:22	net.ipv4.tcp_keepalive_time = 600 # sealos
192.168.1.43:22	net.ipv4.vs.conn_reuse_mode = 0 # sealos
192.168.1.43:22	net.ipv4.vs.conntrack = 1 # sealos
192.168.1.43:22	net.ipv6.conf.all.forwarding = 1 # sealos
192.168.1.43:22	* Applying /etc/sysctl.conf ...
192.168.1.43:22	fs.file-max = 1048576 # sealos
192.168.1.43:22	net.bridge.bridge-nf-call-ip6tables = 1 # sealos
192.168.1.43:22	net.bridge.bridge-nf-call-iptables = 1 # sealos
192.168.1.43:22	net.core.somaxconn = 65535 # sealos
192.168.1.43:22	net.ipv4.conf.all.rp_filter = 0 # sealos
192.168.1.43:22	net.ipv4.ip_forward = 1 # sealos
192.168.1.43:22	net.ipv4.ip_local_port_range = 1024 65535 # sealos
192.168.1.43:22	net.ipv4.tcp_keepalive_intvl = 30 # sealos
192.168.1.43:22	net.ipv4.tcp_keepalive_time = 600 # sealos
192.168.1.43:22	net.ipv4.vs.conn_reuse_mode = 0 # sealos
192.168.1.43:22	net.ipv4.vs.conntrack = 1 # sealos
192.168.1.43:22	net.ipv6.conf.all.forwarding = 1 # sealos
192.168.1.42:22	 INFO [2023-10-14 10:52:02] >> pull pause image sealos.hub:5000/pause:3.9 
192.168.1.47:22	 INFO [2023-10-14 10:52:02] >> pull pause image sealos.hub:5000/pause:3.9 
192.168.1.43:22	 INFO [2023-10-14 10:52:02] >> pull pause image sealos.hub:5000/pause:3.9 
192.168.1.42:22	Image is up to date for sha256:e6f1816883972d4be47bd48879a08919b96afcd344132622e4d444987919323c
192.168.1.42:22	Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /etc/systemd/system/kubelet.service.
192.168.1.47:22	Image is up to date for sha256:e6f1816883972d4be47bd48879a08919b96afcd344132622e4d444987919323c
192.168.1.42:22	 INFO [2023-10-14 10:52:03] >> init kubelet success 
192.168.1.42:22	 INFO [2023-10-14 10:52:03] >> init rootfs success 
192.168.1.47:22	Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /etc/systemd/system/kubelet.service.
192.168.1.47:22	 INFO [2023-10-14 10:52:03] >> init kubelet success 
192.168.1.47:22	 INFO [2023-10-14 10:52:03] >> init rootfs success 
192.168.1.43:22	Image is up to date for sha256:e6f1816883972d4be47bd48879a08919b96afcd344132622e4d444987919323c
192.168.1.43:22	Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /etc/systemd/system/kubelet.service.
192.168.1.43:22	 INFO [2023-10-14 10:52:03] >> init kubelet success 
192.168.1.43:22	 INFO [2023-10-14 10:52:03] >> init rootfs success 
2023-10-14T10:52:03 info Executing pipeline Join in ScaleProcessor.
2023-10-14T10:52:03 info [192.168.1.42:22 192.168.1.43:22] will be added as master
2023-10-14T10:52:03 info start to init filesystem join masters...
2023-10-14T10:52:03 info start to copy static files to masters
2023-10-14T10:52:03 info start to copy kubeconfig files to masters
2023-10-14T10:52:03 info start to copy etc pki files to masters/1, 64 it/s)
2023-10-14T10:52:04 info start to get kubernetes token...                             
2023-10-14T10:52:04 info start to copy kubeadm join config to master: 192.168.1.43:22
2023-10-14T10:52:05 info start to copy kubeadm join config to master: 192.168.1.42:22
2023-10-14T10:52:05 info fetch certSANs from kubeadm configmap1/1, 261 it/s)
2023-10-14T10:52:05 info start to join 192.168.1.42:22 as master
2023-10-14T10:52:05 info start to generator cert 192.168.1.42:22 as master
192.168.1.42:22	2023-10-14T10:52:06 info apiserver altNames : {map[apiserver.cluster.local:apiserver.cluster.local k8s-master2:k8s-master2 kubernetes:kubernetes kubernetes.default:kubernetes.default kubernetes.default.svc:kubernetes.default.svc kubernetes.default.svc.cluster.local:kubernetes.default.svc.cluster.local localhost:localhost] map[10.103.97.2:10.103.97.2 10.96.0.1:10.96.0.1 127.0.0.1:127.0.0.1 192.168.1.41:192.168.1.41 192.168.1.42:192.168.1.42]}
192.168.1.42:22	2023-10-14T10:52:06 info Etcd altnames : {map[k8s-master2:k8s-master2 localhost:localhost] map[127.0.0.1:127.0.0.1 192.168.1.42:192.168.1.42 ::1:::1]}, commonName : k8s-master2
192.168.1.42:22	2023-10-14T10:52:06 info sa.key sa.pub already exist
192.168.1.42:22	2023-10-14T10:52:07 info domain apiserver.cluster.local:192.168.1.41 append success
192.168.1.42:22	W1014 10:52:08.052850    2005 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
192.168.1.42:22	[preflight] Running pre-flight checks
192.168.1.42:22		[WARNING FileExisting-socat]: socat not found in system path
192.168.1.42:22	[preflight] Reading configuration from the cluster...
192.168.1.42:22	[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
192.168.1.42:22	W1014 10:52:08.552033    2005 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: 127.0.0.1; the provided value is: 0.0.0.0
192.168.1.42:22	[preflight] Running pre-flight checks before initializing the new control plane instance
192.168.1.42:22	[preflight] Pulling images required for setting up a Kubernetes cluster
192.168.1.42:22	[preflight] This might take a minute or two, depending on the speed of your internet connection
192.168.1.42:22	[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
192.168.1.42:22	W1014 10:52:22.294658    2005 checks.go:835] detected that the sandbox image "sealos.hub:5000/pause:3.9" of the container runtime is inconsistent with that used by kubeadm. It is recommended that using "registry.k8s.io/pause:3.9" as the CRI sandbox image.
192.168.1.42:22	[download-certs] Downloading the certificates in Secret "kubeadm-certs" in the "kube-system" Namespace
192.168.1.42:22	[download-certs] Saving the certificates to the folder: "/etc/kubernetes/pki"
192.168.1.42:22	[certs] Using certificateDir folder "/etc/kubernetes/pki"
192.168.1.42:22	[certs] Using the existing "etcd/peer" certificate and key
192.168.1.42:22	[certs] Using the existing "etcd/healthcheck-client" certificate and key
192.168.1.42:22	[certs] Using the existing "apiserver-etcd-client" certificate and key
192.168.1.42:22	[certs] Using the existing "etcd/server" certificate and key
192.168.1.42:22	[certs] Using the existing "apiserver-kubelet-client" certificate and key
192.168.1.42:22	[certs] Using the existing "apiserver" certificate and key
192.168.1.42:22	[certs] Using the existing "front-proxy-client" certificate and key
192.168.1.42:22	[certs] Valid certificates and keys now exist in "/etc/kubernetes/pki"
192.168.1.42:22	[certs] Using the existing "sa" key
192.168.1.42:22	[kubeconfig] Generating kubeconfig files
192.168.1.42:22	[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
192.168.1.42:22	[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/admin.conf"
192.168.1.42:22	W1014 10:52:36.935920    2005 kubeconfig.go:264] a kubeconfig file "/etc/kubernetes/controller-manager.conf" exists already but has an unexpected API Server URL: expected: https://192.168.1.42:6443, got: https://apiserver.cluster.local:6443
192.168.1.42:22	[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/controller-manager.conf"
192.168.1.42:22	W1014 10:52:37.167706    2005 kubeconfig.go:264] a kubeconfig file "/etc/kubernetes/scheduler.conf" exists already but has an unexpected API Server URL: expected: https://192.168.1.42:6443, got: https://apiserver.cluster.local:6443
192.168.1.42:22	[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/scheduler.conf"
192.168.1.42:22	[control-plane] Using manifest folder "/etc/kubernetes/manifests"
192.168.1.42:22	[control-plane] Creating static Pod manifest for "kube-apiserver"
192.168.1.42:22	[control-plane] Creating static Pod manifest for "kube-controller-manager"
192.168.1.42:22	[control-plane] Creating static Pod manifest for "kube-scheduler"
192.168.1.42:22	[check-etcd] Checking that the etcd cluster is healthy
192.168.1.42:22	[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
192.168.1.42:22	[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
192.168.1.42:22	[kubelet-start] Starting the kubelet
192.168.1.42:22	[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
192.168.1.42:22	[etcd] Announced new etcd member joining to the existing etcd cluster
192.168.1.42:22	[etcd] Creating static Pod manifest for "etcd"
192.168.1.42:22	[etcd] Waiting for the new etcd member to join the cluster. This can take up to 40s
192.168.1.42:22	The 'update-status' phase is deprecated and will be removed in a future release. Currently it performs no operation
192.168.1.42:22	[mark-control-plane] Marking the node k8s-master2 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
192.168.1.42:22	[mark-control-plane] Marking the node k8s-master2 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]
192.168.1.42:22	
192.168.1.42:22	This node has joined the cluster and a new control plane instance was created:
192.168.1.42:22	
192.168.1.42:22	* Certificate signing request was sent to apiserver and approval was received.
192.168.1.42:22	* The Kubelet was informed of the new secure connection details.
192.168.1.42:22	* Control plane label and taint were applied to the new node.
192.168.1.42:22	* The Kubernetes control plane instances scaled up.
192.168.1.42:22	* A new etcd member was added to the local/stacked etcd cluster.
192.168.1.42:22	
192.168.1.42:22	To start administering your cluster from this node, you need to run the following as a regular user:
192.168.1.42:22	
192.168.1.42:22		mkdir -p $HOME/.kube
192.168.1.42:22		sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
192.168.1.42:22		sudo chown $(id -u):$(id -g) $HOME/.kube/config
192.168.1.42:22	
192.168.1.42:22	Run 'kubectl get nodes' to see this node join the cluster.
192.168.1.42:22	
192.168.1.42:22	2023-10-14T10:52:59 info domain apiserver.cluster.local delete success
192.168.1.42:22	2023-10-14T10:52:59 info domain apiserver.cluster.local:192.168.1.42 append success
2023-10-14T10:52:59 info succeeded in joining 192.168.1.42:22 as master
2023-10-14T10:52:59 info start to join 192.168.1.43:22 as master
2023-10-14T10:52:59 info start to generator cert 192.168.1.43:22 as master
192.168.1.43:22	2023-10-14T10:53:00 info apiserver altNames : {map[apiserver.cluster.local:apiserver.cluster.local k8s-master3:k8s-master3 kubernetes:kubernetes kubernetes.default:kubernetes.default kubernetes.default.svc:kubernetes.default.svc kubernetes.default.svc.cluster.local:kubernetes.default.svc.cluster.local localhost:localhost] map[10.103.97.2:10.103.97.2 10.96.0.1:10.96.0.1 127.0.0.1:127.0.0.1 192.168.1.41:192.168.1.41 192.168.1.43:192.168.1.43]}
192.168.1.43:22	2023-10-14T10:53:00 info Etcd altnames : {map[k8s-master3:k8s-master3 localhost:localhost] map[127.0.0.1:127.0.0.1 192.168.1.43:192.168.1.43 ::1:::1]}, commonName : k8s-master3
192.168.1.43:22	2023-10-14T10:53:00 info sa.key sa.pub already exist
192.168.1.43:22	2023-10-14T10:53:02 info domain apiserver.cluster.local:192.168.1.41 append success
192.168.1.43:22	W1014 10:53:02.242175    1986 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
192.168.1.43:22	[preflight] Running pre-flight checks
192.168.1.43:22		[WARNING FileExisting-socat]: socat not found in system path
192.168.1.43:22	[preflight] Reading configuration from the cluster...
192.168.1.43:22	[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
192.168.1.43:22	W1014 10:53:02.598221    1986 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: 127.0.0.1; the provided value is: 0.0.0.0
192.168.1.43:22	[preflight] Running pre-flight checks before initializing the new control plane instance
192.168.1.43:22	[preflight] Pulling images required for setting up a Kubernetes cluster
192.168.1.43:22	[preflight] This might take a minute or two, depending on the speed of your internet connection
192.168.1.43:22	[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
192.168.1.43:22	W1014 10:53:16.884534    1986 checks.go:835] detected that the sandbox image "sealos.hub:5000/pause:3.9" of the container runtime is inconsistent with that used by kubeadm. It is recommended that using "registry.k8s.io/pause:3.9" as the CRI sandbox image.
192.168.1.43:22	[download-certs] Downloading the certificates in Secret "kubeadm-certs" in the "kube-system" Namespace
192.168.1.43:22	[download-certs] Saving the certificates to the folder: "/etc/kubernetes/pki"
192.168.1.43:22	[certs] Using certificateDir folder "/etc/kubernetes/pki"
192.168.1.43:22	[certs] Using the existing "apiserver-kubelet-client" certificate and key
192.168.1.43:22	[certs] Using the existing "apiserver" certificate and key
192.168.1.43:22	[certs] Using the existing "etcd/server" certificate and key
192.168.1.43:22	[certs] Using the existing "etcd/peer" certificate and key
192.168.1.43:22	[certs] Using the existing "etcd/healthcheck-client" certificate and key
192.168.1.43:22	[certs] Using the existing "apiserver-etcd-client" certificate and key
192.168.1.43:22	[certs] Using the existing "front-proxy-client" certificate and key
192.168.1.43:22	[certs] Valid certificates and keys now exist in "/etc/kubernetes/pki"
192.168.1.43:22	[certs] Using the existing "sa" key
192.168.1.43:22	[kubeconfig] Generating kubeconfig files
192.168.1.43:22	[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
192.168.1.43:22	[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/admin.conf"
192.168.1.43:22	W1014 10:53:31.994728    1986 kubeconfig.go:264] a kubeconfig file "/etc/kubernetes/controller-manager.conf" exists already but has an unexpected API Server URL: expected: https://192.168.1.43:6443, got: https://apiserver.cluster.local:6443
192.168.1.43:22	[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/controller-manager.conf"
192.168.1.43:22	W1014 10:53:32.241906    1986 kubeconfig.go:264] a kubeconfig file "/etc/kubernetes/scheduler.conf" exists already but has an unexpected API Server URL: expected: https://192.168.1.43:6443, got: https://apiserver.cluster.local:6443
192.168.1.43:22	[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/scheduler.conf"
192.168.1.43:22	[control-plane] Using manifest folder "/etc/kubernetes/manifests"
192.168.1.43:22	[control-plane] Creating static Pod manifest for "kube-apiserver"
192.168.1.43:22	[control-plane] Creating static Pod manifest for "kube-controller-manager"
192.168.1.43:22	[control-plane] Creating static Pod manifest for "kube-scheduler"
192.168.1.43:22	[check-etcd] Checking that the etcd cluster is healthy
192.168.1.43:22	[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
192.168.1.43:22	[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
192.168.1.43:22	[kubelet-start] Starting the kubelet
192.168.1.43:22	[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
192.168.1.43:22	[etcd] Announced new etcd member joining to the existing etcd cluster
192.168.1.43:22	[etcd] Creating static Pod manifest for "etcd"
192.168.1.43:22	[etcd] Waiting for the new etcd member to join the cluster. This can take up to 40s
192.168.1.43:22	The 'update-status' phase is deprecated and will be removed in a future release. Currently it performs no operation
192.168.1.43:22	[mark-control-plane] Marking the node k8s-master3 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
192.168.1.43:22	[mark-control-plane] Marking the node k8s-master3 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]
192.168.1.43:22	
192.168.1.43:22	This node has joined the cluster and a new control plane instance was created:
192.168.1.43:22	
192.168.1.43:22	* Certificate signing request was sent to apiserver and approval was received.
192.168.1.43:22	* The Kubelet was informed of the new secure connection details.
192.168.1.43:22	* Control plane label and taint were applied to the new node.
192.168.1.43:22	* The Kubernetes control plane instances scaled up.
192.168.1.43:22	* A new etcd member was added to the local/stacked etcd cluster.
192.168.1.43:22	
192.168.1.43:22	To start administering your cluster from this node, you need to run the following as a regular user:
192.168.1.43:22	
192.168.1.43:22		mkdir -p $HOME/.kube
192.168.1.43:22		sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
192.168.1.43:22		sudo chown $(id -u):$(id -g) $HOME/.kube/config
192.168.1.43:22	
192.168.1.43:22	Run 'kubectl get nodes' to see this node join the cluster.
192.168.1.43:22	
192.168.1.43:22	2023-10-14T10:53:49 info domain apiserver.cluster.local delete success
192.168.1.43:22	2023-10-14T10:53:49 info domain apiserver.cluster.local:192.168.1.43 append success
2023-10-14T10:53:49 info succeeded in joining 192.168.1.43:22 as master
2023-10-14T10:53:49 info [192.168.1.47:22] will be added as worker
2023-10-14T10:53:49 info fetch certSANs from kubeadm configmap
2023-10-14T10:53:49 info start to join 192.168.1.47:22 as worker
2023-10-14T10:53:49 info start to copy kubeadm join config to node: 192.168.1.47:22
192.168.1.47:22l2023-10-14T10:53:50 info domain apiserver.cluster.local:10.103.97.2 append success
192.168.1.47:22	2023-10-14T10:53:50 info domain lvscare.node.ip:192.168.1.47 append success
2023-10-14T10:53:50 info run ipvs once module: 192.168.1.47:22
192.168.1.47:22	2023-10-14T10:53:50 info Trying to add route
192.168.1.47:22	2023-10-14T10:53:50 info success to set route.(host:10.103.97.2, gateway:192.168.1.47)
2023-10-14T10:53:50 info start join node: 192.168.1.47:22
192.168.1.47:22	W1014 10:53:51.106974    1990 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
192.168.1.47:22	[preflight] Running pre-flight checks
192.168.1.47:22		[WARNING FileExisting-socat]: socat not found in system path
192.168.1.47:22	[preflight] Reading configuration from the cluster...
192.168.1.47:22	[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
192.168.1.47:22	W1014 10:54:01.476623    1990 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: 127.0.0.1; the provided value is: 0.0.0.0
192.168.1.47:22	[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
192.168.1.47:22	[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
192.168.1.47:22	[kubelet-start] Starting the kubelet
192.168.1.47:22	[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
192.168.1.47:22	
192.168.1.47:22	This node has joined the cluster:
192.168.1.47:22	* Certificate signing request was sent to apiserver and a response was received.
192.168.1.47:22	* The Kubelet was informed of the new secure connection details.
192.168.1.47:22	
192.168.1.47:22	Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
192.168.1.47:22	
2023-10-14T10:54:04 info succeeded in joining 192.168.1.47:22 as worker
2023-10-14T10:54:04 info start to sync lvscare static pod to node: 192.168.1.47:22 master: [192.168.1.41:6443 192.168.1.42:6443 192.168.1.43:6443]
2023-10-14T10:54:04 info start to sync lvscare static pod to node: 192.168.1.46:22 master: [192.168.1.41:6443 192.168.1.42:6443 192.168.1.43:6443]
192.168.1.47:22	2023-10-14T10:54:04 info generator lvscare static pod is success
192.168.1.46:22	2023-10-14T10:54:05 info generator lvscare static pod is success
2023-10-14T10:54:05 info Executing pipeline RunGuest in ScaleProcessor.
2023-10-14T10:54:05 info succeeded in scaling this cluster
2023-10-14T10:54:05 info 
      ___           ___           ___           ___       ___           ___
     /\  \         /\  \         /\  \         /\__\     /\  \         /\  \
    /::\  \       /::\  \       /::\  \       /:/  /    /::\  \       /::\  \
   /:/\ \  \     /:/\:\  \     /:/\:\  \     /:/  /    /:/\:\  \     /:/\ \  \
  _\:\~\ \  \   /::\~\:\  \   /::\~\:\  \   /:/  /    /:/  \:\  \   _\:\~\ \  \
 /\ \:\ \ \__\ /:/\:\ \:\__\ /:/\:\ \:\__\ /:/__/    /:/__/ \:\__\ /\ \:\ \ \__\
 \:\ \:\ \/__/ \:\~\:\ \/__/ \/__\:\/:/  / \:\  \    \:\  \ /:/  / \:\ \:\ \/__/
  \:\ \:\__\    \:\ \:\__\        \::/  /   \:\  \    \:\  /:/  /   \:\ \:\__\
   \:\/:/  /     \:\ \/__/        /:/  /     \:\  \    \:\/:/  /     \:\/:/  /
    \::/  /       \:\__\         /:/  /       \:\__\    \::/  /       \::/  /
     \/__/         \/__/         \/__/         \/__/     \/__/         \/__/

                  Website: https://www.sealos.io/
                  Address: github.com/labring/sealos
                  Version: 4.3.5-881c10cb

3. 查看新增的节点

添加完成，查看节点状态

[root@k8s-master1 ~]# kubectl get node
NAME          STATUS   ROLES           AGE   VERSION
k8s-master1   Ready    control-plane   17h   v1.27.6
k8s-master2   Ready    control-plane   28m   v1.27.6
k8s-master3   Ready    control-plane   27m   v1.27.6
k8s-node1     Ready    <none>          17h   v1.27.6
k8s-node2     Ready    <none>          27m   v1.27.6

之后一篇sealos4.3.5安装手册（三）管理界面将讲解k8s如何添加看板，方便界面化操作。

下面这个图可以增加博主分享知识的动力，来助力一下吧

学习的动力

westlifeml
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
迅睿CMS免费开源系统 v4.3.5
09-29
迅睿CMS内容管理框架是基于PHP7语言采用最新CodeIgniter4作为开发框架生产的网站内容管理框架，提供“电脑网站 + 手机网站 + APP 接口”一体化网站技术解决方案。她拥有强大稳定底层框
柚子黑卡4.3.5.zip
09-06
柚子黑卡4.3.5
spring-framework-4.3.5.RELEASE 源码
12-29
spring-framework-4.3.5.RELEASE 源码及jar包全 关联源代码学习spring 事半功倍
[Fabric]执行./byfn.sh generate时报Failed to generate certificates…
weixin_41946008的博客
10-06 1431
[Fabric]执行./byfn.sh generate时报Failed to generate certificates… 我的解决方案： docker-compose -f docker-compose-cli.yaml down sudo ./byfn.sh down 那么问题就可以解决了
Redhat7 安装Docker
neu_xiaolu的博客
06-10 2682
ssh登录服务器： [root@okqvd ~]# which docker /usr/bin/which: no docker in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) [root@okqvd ~]# yum install docker Loaded plugins: langpacks, produc...
sealos安装k8s
卷心菜投手
08-11 2279
kubeadm2、安装k8s的方式有很多3、关于sealos来安装 k8s ，也是非常建议大家去官方文档看看，，说的很非常清楚，一看就知道。
QT4.3.5 源码+编绎
06-05
QTDIR= /Qt-4.3.5 //Qt安装目录 LD_LIBRARY_PATH= /Qt-4.3.5/lib//Qt库文件目录 PATH=$PATH:(QT命令所在目录) ———————————————— 版权声明：本文为CSDN博主「asmfox」的原创文章，遵循CC 4.0 BY-SA...
ThinkSNS v4.3.5
12-04
ThinkSNS基于许多优秀的开源软件开发，提供全方位的社交网络(SNS)解决方案。 ThinkSNS源于办公圈项目，WEB端基于国内技术领先的ThinkPHP框架开发，另外还有IM客户端软件。 ThinkSNS是国内最大的开源社群系
最简单的kubernetes HA安装方式-sealos详解支持kubernetes1.14.1安装
github_35614077的博客
04-15 2034
kubernetes集群三步安装 概述 本文教你如何用一条命令构建k8s高可用集群且不依赖haproxy和keepalived，也无需ansible。通过内核ipvs对apiserver进行负载均衡，并且带apiserver健康检测。 快速入门 sealos项目地址 准备条件 装好docker并启动docker 把离线安装包 下载好拷贝到所有节点的/root目录下, 不需要解压，如果有文件服...
sealos单机安装记录
sunican的专栏
03-01 629
记录用sealos安装单机版本的输出
基于 Sealos 的镜像构建能力，快速部署自定义 k8s 集群
gumc123的博客
11-17 1268
Sealos 是一个快速构建高可用 k8s 集群的命令行工具，该工具部署时会在第一个 k8s master 节点部署 registry 服务(sealos.hub)，该域名通过 hosts 解析到第一个 k8s master 节点 ip；基于内核 ipvs 对 apiserver 进行负载均衡，其默认虚拟 ip 地址为 10.103.97.2(apiserver.cluster.local)，所有 k8s Worker 节点通过该虚拟 ip 访问 kube-apiserver
ubuntu 20.04 sealos 私有化部署整个日志流程
qq_24768591的博客
10-03 371
【代码】ubuntu 20.04 sealos 私有化部署。
常见的ssh功能
活到老学到老
04-28 329
远程登录：SSH可以通过加密的方式，安全地远程登录到远程服务器或设备上，从而可以在远程设备上执行命令和管理系统。远程桌面：通过SSH可以使用X11转发功能，在远程服务器上运行图形化应用程序，并将其显示在本地主机上。端口转发：SSH可以进行本地端口转发和远程端口转发，使得可以安全地在本地和远程主机之间进行端口通信。总之，SSH是一种功能强大的网络协议，提供了安全、灵活和可靠的远程访问和控制功能。远程执行命令：SSH可以在远程主机上执行命令，这使得可以远程管理和控制服务器。
nginx + rtmp 搭建rtmp服务器
Leagues的博客
04-26 122
1、nginx.conf 的配置文件如下events {} http {server {listen 80;root html;root html;record off;} } }2、推流代码ffmpeg3、测试方式，采用VLC拉取视频流。
基于SSH的任务调度系统的设计与实现（论文 + 源码）
最新发布
JW_559的博客
04-29 938
本系统采用了B/S体系结构，主要实现语言是JAVA，后台数据库使用的是MySql。整个系统实现角色将分为组长和组员，实现功能包括帐号注册、修改信息、项目管理、任务管理、消息管理、团队管理等功能。本任务调度系统的设计实现可以远程实现任务的调度与科学分配，并通过评估各项任务与参与人员，来使项目更好的进行任务调度。
【A-024】基于SSH的房屋租赁管理系统（含论文）
exodus3的博客
04-25 173
随着我国市场经济的快速发展和人们生活水平的不断提高，简单的租凭服务已经不能满足人们的需求。如何利用先进的管理手段，提高房屋租凭管理水平，是当今社会所面临的一个重要课题。本系统是一个独立的系统，用来解决房屋出租信息的管理问题。采用JSP技术构建了一个有效而且实用的房屋出租信息管理平台，目的是为高效地完成对房屋出租信息的管理。开发目的是为了使客户可以随时随地自由地查询他想要的房屋信息，客户无需亲临，一一选择，只要坐在电脑前，开机上网即可查询到自己想要的房屋信息。课程设计，毕业设计，学习等等。
Nginx入门-01
m0_62569064的博客
04-26 626
简单介绍一下学习Nginx的一些必备知识，基本认识一下Nginx的有什么用
【工具】SSH常用功能
weixin_43366051的博客
04-28 245
随着开发语言及人工智能工具的普及，使得越来越多的人会主动学习使用一些运维工具，本文主要介绍了SSH常用功能。
Apache和Nginx的区别以及如何选择
ZhujiServer的博客
04-28 192
除了是因为竞争对手Nginx的崛起，也有一部分原因是其他一些新的Web服务器技术的涌现。目前市面上有许多Web服务器软件，常见的有Apache、Nginx、Microsoft Internet Information Services (IIS)、LiteSpeed Web Server、Tomcat、Node.js等等，其中Apache和Nginx是最常见的两款，算是占据了市场的主导地位，这两款Web服务器在不同的应用场景下都表现出色，并且拥有强大的社区支持和持续的开发更新。
使用yum命令安装FFmpeg 4.3.5.bz2详细步骤
04-04
1. 下载FFmpeg 4.3.5.bz2压缩包 在终端输入以下命令下载FFmpeg 4.3.5.bz2压缩包： ``` wget https://ffmpeg.org/releases/ffmpeg-4.3.5.tar.bz2 ``` 2. 解压缩压缩包 在终端输入以下命令解压缩下载的压缩包： `...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值