Sealos Version
v5.1.2-rc4
How to reproduce the bug?
使用官方部署命令
curl -sfL https://raw.githubusercontent.com/labring/sealos/refs/heads/main/scripts/cloud/install-v2.sh -o install.sh && SEALOS_V2_CLOUD_VERSION=v5.1.2-rc4 SEALOS_V2_PROXY=false SEALOS_V2_CLOUD_DOMAIN=101.32.48.56.nip.io bash install.sh
INFO [2026-03-27 11:57:39] >> [Step] TLS certificate details:
🌐 DNS: kubernetes
🌐 DNS: kubernetes.default
🌐 DNS: kubernetes.default.svc
🌐 DNS: apiserver.cluster.local
🌐 DNS: 101.32.48.56.nip.io
🌐 DNS: kubernetes.default.svc.cluster.local
🌐 DNS: vm-0-12-ubuntu
📡 IP: 127.0.0.1
📡 IP: 10.96.0.1
📡 IP: 10.103.97.2
📡 IP: 172.19.0.12
INFO [2026-03-27 11:57:39] >> Installation complete!
INFO [2026-03-27 11:57:39] >> Kubernetes version: 1.28.15
INFO [2026-03-27 11:57:39] >> Sealos Cloud version:
INFO [2026-03-27 11:57:39] >> Access URL: https://101.32.48.56.nip.io:443
INFO [2026-03-27 11:57:39] >> Default admin credentials:
INFO [2026-03-27 11:57:39] >> Username: admin
INFO [2026-03-27 11:57:39] >> Password: sealos2023
INFO [2026-03-27 11:57:39] >> TLS certificate information (important - please review):
INFO [2026-03-27 11:57:39] >> No TLS certificate provided — a self-signed certificate will be used by Sealos Cloud.
INFO [2026-03-27 11:57:39] >> Browsers and clients will show a warning unless the self-signed certificate is trusted.
INFO [2026-03-27 11:57:39] >> To trust the certificate, follow the guide: https://sealos.run/docs/self-hosting/install#信任自签名证书
2026-03-27T11:57:39 info succeeded install app in this cluster
2026-03-27T11:57:39 info no nodes that need to be scaled
2026-03-27T11:57:39 info using v1beta3 kubeadm config
2026-03-27T11:57:39 info
___ ___ ___ ___ ___ ___
/\ \ /\ \ /\ \ /_\ /\ \ /\
/::\ \ /::\ \ /::\ \ /:/ / /::\ \ /::\
/:/\ \ \ /:/:\ \ /:/:\ \ /:/ / /:/:\ \ /:/\ \
:~\ \ \ /::~:\ \ /::~:\ \ /:/ / /:/ :\ \ :~\ \
/\ :\ \ _\ /:/:\ :_\ /:/:\ :_\ /:// /:// :_\ /\ :\ \ _
:\ :\ // :~:\ // /:/:/ / :\ \ :\ \ /:/ / :\ :\ //
:\ :_\ :\ :_\ ::/ / :\ \ :\ /:/ / :\ :_
:/:/ / :\ /__/ /:/ / :\ \ :/:/ / :/:/ /
::/ / :_\ /:/ / :__\ ::/ / ::/ /
// // // // // //
Website: https://www.sealos.io/
Address: github.com/labring/sealos
Version: 5.1.0-c71c8d766
What is the expected behavior?
No response
What do you see instead?
No response
Operating environment
- Sealos version: 5.1.0-c71c8d766
- Docker version: Not Installed
- Kubernetes version: Client Version: v1.28.15
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
- Operating system: Ubuntu 22.04.5 LTS
- Runtime environment:
- Cluster size: 1 Nodes
- Additional information: Kernel 5.15.0-171-generic, Arch x86_64
Additional information
No response
Sealos Version
v5.1.2-rc4
How to reproduce the bug?
使用官方部署命令
curl -sfL https://raw.githubusercontent.com/labring/sealos/refs/heads/main/scripts/cloud/install-v2.sh -o install.sh && SEALOS_V2_CLOUD_VERSION=v5.1.2-rc4 SEALOS_V2_PROXY=false SEALOS_V2_CLOUD_DOMAIN=101.32.48.56.nip.io bash install.sh
INFO [2026-03-27 11:57:39] >> [Step] TLS certificate details:
🌐 DNS: kubernetes
🌐 DNS: kubernetes.default
🌐 DNS: kubernetes.default.svc
🌐 DNS: apiserver.cluster.local
🌐 DNS: 101.32.48.56.nip.io
🌐 DNS: kubernetes.default.svc.cluster.local
🌐 DNS: vm-0-12-ubuntu
📡 IP: 127.0.0.1
📡 IP: 10.96.0.1
📡 IP: 10.103.97.2
📡 IP: 172.19.0.12
INFO [2026-03-27 11:57:39] >> Installation complete!
INFO [2026-03-27 11:57:39] >> Kubernetes version: 1.28.15
INFO [2026-03-27 11:57:39] >> Sealos Cloud version:
INFO [2026-03-27 11:57:39] >> Access URL: https://101.32.48.56.nip.io:443
INFO [2026-03-27 11:57:39] >> Default admin credentials:
INFO [2026-03-27 11:57:39] >> Username: admin
INFO [2026-03-27 11:57:39] >> Password: sealos2023
INFO [2026-03-27 11:57:39] >> TLS certificate information (important - please review):
INFO [2026-03-27 11:57:39] >> No TLS certificate provided — a self-signed certificate will be used by Sealos Cloud.
INFO [2026-03-27 11:57:39] >> Browsers and clients will show a warning unless the self-signed certificate is trusted.
INFO [2026-03-27 11:57:39] >> To trust the certificate, follow the guide: https://sealos.run/docs/self-hosting/install#信任自签名证书
2026-03-27T11:57:39 info succeeded install app in this cluster
2026-03-27T11:57:39 info no nodes that need to be scaled
2026-03-27T11:57:39 info using v1beta3 kubeadm config
2026-03-27T11:57:39 info
___ ___ ___ ___ ___ ___
/\ \ /\ \ /\ \ /_\ /\ \ /\
/::\ \ /::\ \ /::\ \ /:/ / /::\ \ /::\
/:/\ \ \ /:/:\ \ /:/:\ \ /:/ / /:/:\ \ /:/\ \
:~\ \ \ /::~:\ \ /::~:\ \ /:/ / /:/ :\ \ :~\ \
/\ :\ \ _\ /:/:\ :_\ /:/:\ :_\ /:// /:// :_\ /\ :\ \ _
:\ :\ // :~:\ // /:/:/ / :\ \ :\ \ /:/ / :\ :\ //
:\ :_\ :\ :_\ ::/ / :\ \ :\ /:/ / :\ :_
:/:/ / :\ /__/ /:/ / :\ \ :/:/ / :/:/ /
::/ / :_\ /:/ / :__\ ::/ / ::/ /
// // // // // //
What is the expected behavior?
No response
What do you see instead?
No response
Operating environment
Additional information
No response