安装kubernetes报错以及解决

原创 已于 2023-12-12 08:50:39 修改 · 1.8w 阅读 · 29 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#kubernetes

于 2021-08-05 11:43:07 首次发布
本文档记录了在初始化Kubernetes集群时遇到的三个主要错误：1) 主机名无法解析；2) 组件配置验证失败；3) kubelet启动超时。针对这些问题，提供了相应的解决方法，包括删除manifests文件夹、忽略预飞检查错误、关闭swap、重置kubeadm、重启kubelet服务以及清空iptables规则。通过这些步骤，成功初始化了Kubernetes集群。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

一、初始化集群报错
1、报错：
[WARNING Hostname]: hostname “master1” could not be reached
[WARNING Hostname]: hostname “master1”: lookup master1 on 114.114.114.114:53: no such host,

详细如下：

[root@k8smaster ~]# kubeadm init --config kubeadm.yaml
W1124 09:40:03.139811   68129 strict.go:54] error unmarshaling configuration schema.GroupVersionKind{Group:"kubeadm.k8s.io", Version:"v1beta2", Kind:"ClusterConfiguration"}: error unmarshaling JSON: while decoding JSON: json: unknown field "scheduler"
W1124 09:40:03.333487   68129 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[init] Using Kubernetes version: v1.19.3
[preflight] Running pre-flight checks
        [WARNING Hostname]: hostname "master1" could not be reached
        [WARNING Hostname]: hostname "master1": lookup master1 on 114.114.114.114:53: no such host
error execution phase preflight: [preflight] Some fatal errors occurred:
        [ERROR Port-6443]: Port 6443 is in use
        [ERROR Port-10259]: Port 10259 is in use
        [ERROR Port-10257]: Port 10257 is in use
        [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists
        [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists
        [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists
        [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists
        [ERROR Port-10250]: Port 10250 is in use
        [ERROR Port-2379]: Port 2379 is in use
        [ERROR Port-2380]: Port 2380 is in use
        [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher

解决方法：
删除/etc/kubernetes/manifests
修改kubeadm.yaml。把name修改为主机的hostname
再执行初始化即可。

[root@k8smaster ~]# ls /etc/kubernetes/
admin.conf  controller-manager.conf  kubelet.conf  manifests  pki  scheduler.conf
[root@k8smaster ~]# ls
anaconda-ks.cfg  kubeadm.yaml
[root@k8smaster ~]# rm -rf  /etc/kubernetes/manifests
[root@k8smaster ~]# ls /etc/kubernetes/
admin.conf  controller-manager.conf  kubelet.conf  pki  scheduler.conf

2、报错：
WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]

详细如下：

[root@k8smaster ~]# kubeadm init --config kubeadm.yaml
W1124 09:47:13.677697   70122 strict.go:54] error unmarshaling configuration schema.GroupVersionKind{Group:"kubeadm.k8s.io", Version:"v1beta2", Kind:"ClusterConfiguration"}: error unmarshaling JSON: while decoding JSON: json: unknown field "scheduler"
W1124 09:47:13.876821   70122 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[init] Using Kubernetes version: v1.19.3
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
        [ERROR Port-10250]: Port 10250 is in use
        [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher

解决方法：
初始化时增加：–ignore-preflight-errors=all
即：

kubeadm init --config kubeadm.yaml --ignore-preflight-errors=all

3、报错：
[kubelet-check] Initial timeout of 40s passed.
error execution phase upload-config/kubelet: Error writing Crisocket information for the control-plane node: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher

详细如下：

[root@k8smaster ~]# kubeadm init --config kubeadm.yaml --ignore-preflight-errors=all
W1124 09:54:07.361765   71406 strict.go:54] error unmarshaling configuration schema.GroupVersionKind{Group:"kubeadm.k8s.io", Version:"v1beta2", Kind:"ClusterConfiguration"}: error unmarshaling JSON: while decoding JSON: json: unknown field "scheduler"
W1124 09:54:07.480565   71406 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[init] Using Kubernetes version: v1.19.3
[preflight] Running pre-flight checks
        [WARNING Port-10250]: Port 10250 is in use
        [WARNING DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/admin.conf"
[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/kubelet.conf"
[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/controller-manager.conf"
[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/scheduler.conf"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 13.510116 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.19" in namespace kube-system with the configuration for the kubelets in the cluster
[kubelet-check] Initial timeout of 40s passed.
error execution phase upload-config/kubelet: Error writing Crisocket information for the control-plane node: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher

解决方法：
执行：

swapoff -a && kubeadm reset  && systemctl daemon-reload && systemctl restart kubelet  && iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X

执行完后，再初始化就OK了。

[root@k8smaster ~]# kubeadm init --config kubeadm.yaml --ignore-preflight-errors=all                                                                                                  
W1124 10:00:18.648091   74450 strict.go:54] error unmarshaling configuration schema.GroupVersionKind{Group:"kubeadm.k8s.io", Version:"v1beta2", Kind:"ClusterConfiguration"}: error unmarshaling JSON: while decoding JSON: json: unknown field "scheduler"
W1124 10:00:18.760000   74450 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[init] Using Kubernetes version: v1.19.3
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [k8smaster kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.68.127]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [k8smaster localhost] and IPs [192.168.68.127 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [k8smaster localhost] and IPs [192.168.68.127 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 10.517451 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.19" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --upload-certs
[mark-control-plane] Marking the node k8smaster as control-plane by adding the label "node-role.kubernetes.io/master=''"
[mark-control-plane] Marking the node k8smaster as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: abcdef.0123456789abcdef
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to get nodes
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy

Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join 192.168.68.127:6443 --token abcdef.0123456789abcdef \
    --discovery-token-ca-cert-hash sha256:31020d84f523a2af6fc4fea38e514af8e5e1943a26312f0515e65075da314b29
k8s kubelet日志报...“ err=“failed to parse kubelet flag: unknown flag: --network-plugin“问题解决梳理
z19861216的博客
10-23 2399
k8s kubelet日志报..." err="failed to parse kubelet flag: unknown flag: --network-plugin"问题解决梳理
Kubernetes报错CrashLoopBackOff的Pod健康检查配置
shejizuopin的博客
05-27 685
Kubernetes中的CrashLoopBackOff错误表示Pod中的容器在启动后频繁崩溃，导致Kubernetes不断重启容器。该错误通常由应用程序错误、配置问题、资源限制或健康检查配置不当引起。本文详细分析了CrashLoopBackOff的成因，并提供了健康检查配置的实用技巧，包括Liveness、Readiness和Startup探针的配置方法。此外，文章还介绍了通过查看Pod日志、事件日志、检查配置文件和依赖服务等方式排查和解决该错误的步骤。最后，提出了合理设置探针参数、选择合适的探针类型以及
安装 Kubeadm报错失败
merlon学习笔记
03-28 353
ubuntu22.04安装kubeadm失败
K8s集群新增etcd节点
最新发布
喝醉酒的小白
07-09 1021
Kubernetes 版本：v1.18已有：3个 master 节点（均含 etcd）+ 3个 node 节点（纯工作节点）你已经用把 node 节点加入了集群（worker 角色）你现在想在某个 node 节点上新增 etcd 服务问题能否操作推荐做法节点已加入，能否再次 join？❌ 不能直接需手动执行或先移除再加想让该 node 成为 etcd 成员✅ 可以先用 etcdctl 添加成员，再部署 etcd.yaml想完全升为 control-plane 节点✅ 推荐。
KubeSphere应用【笔记三】添加节点报错
Matrix
12-13 2316
因为担心之前部署时生成的config-sample.yaml文件有问题，所以根据官方文档的命令生产了新的sample.yaml文件.1.生成的文件【etcd】节点如下图所示，需要进行修改。2.生成的文件需要完善节点配置，添加账户、密码。根据官方文档添加节点。
kubernetes初始化失败
qq_57646643的博客
02-23 963
初始化命令（添加 --ignore-preflight-errors 跳过残留文件检查）containerd 的 cgroup 驱动或镜像仓库配置错误会导致控制平面组件无法启动。sudo kill -9 <PID> # 根据输出结果替换 <PID>端口被占用通常由未完全退出的 kubelet 或残留容器引起。kubeadm init --v=5 # 输出级别调至最高。# 强制删除可能残留的静态 Pod 清单（关键！# 如果输出不是 `systemd`，修复配置。# 检查 kubelet 配置。
【已解决】k8s部署遇到的问题记录(1)---kubeadm init 失败
weixin_49064876的博客
01-10 6672
而且[ERROR FileAvailable–etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists提示了相关的yaml文件已存在。2.删除相关配置文件（终端提示有kubeadm reset 执行后不会删除$HOME/.kube文件，需要手动删除）说明了已有kubeadm在运行中，需要关闭当前已运行的kubeadm。1.重启kubeadm。
Kubernetes报错CrashLoopBackOff的Pod启动失败排查
shejizuopin的博客
05-20 688
当Kubernetes中的Pod处于CrashLoopBackOff状态时，通常是由于容器启动后立即崩溃并不断重启。排查步骤包括：首先通过kubectl get pods查看Pod状态，使用kubectl describe pod和kubectl logs获取事件和容器日志。常见故障场景包括应用程序错误、启动命令配置错误、环境变量缺失、依赖服务不可用、资源限制不合理以及存储挂载失败。高级排查技巧包括进入临时调试容器、检查容器文件系统和网络抓包分析。解决方案涉及修复应用程序代码、修正启动命令、补充环境变量、确
Kubernetes报错「CrashLoopBackOff」：Pod状态诊断与资源限制的动态调整策略
shejizuopin的博客
05-12 810
通过本文的深度诊断流程与动态资源调整策略，可系统性解决诊断阶段优先分析日志与事件链，定位崩溃原因。校验启动命令与环境变量配置。资源优化合理配置requests和limits，避免资源争抢。利用QoS等级实现资源隔离。动态调整在Kubernetes 1.27+中启用，实现资源无损调整。预防性措施配置健康检查与资源监控，提前发现潜在问题。使用ResourceQuota和LimitRange限制资源滥用。
安装kubelet报错的解决方法
06-03
[root@xxx yum.repos.d]# yum install -y kubelet kubeadm ...kubernetes | 1.4 kB 00:00:00 No package kubelet available. No package kubeadm available. No package kubectl available. Error: Nothing to do
安装kubelet、kubeadm、kubectl出现的问题
qq_43670385的博客
03-12 346
Error downloading packages: libnetfilter_queue-1.0.2-2.el7_2.x86_64: [Errno 5] [Errno 12] Cannot allocate memory kubelet-1.20.9-0.x86_64: [Errno 5] [Errno 12] Cannot allocate memory libnetfilter_cthelper-1.0.0-11.el7.x86_64: [Errno 5] [Errno 12] Cann
kubeadm init初始化报错
Didier__的博客
06-10 5874
kubeadm init 初始化异常报错处理
Nginx http 500错误分析及解决方法
wangchaoqi1985的博客
11-17 1522
Nginx http 500错误分析及解决方法
kubeadm init时出错
weixin_54225397的博客
05-24 551
提示拉取 registry.aliyuncs.com/google_containers/coredns:v1.8.0 镜像失败。然后执行 Kubernetes init。在执行init之前先执行。
kubeadm init 报错 [ERROR CRI]: container runtime is not running: 的可能解决方案之一
热门推荐
weixin_51546928的博客
06-12 1万+
(好吧似乎我安装的 docker 镜像标签和它需要的没对上)，不过这个问题算是解决了。其实删除文件也算是将。但他后面也提到了其实核心关键不是删除这个文件，他说“按照官网的教程很有用”，然后我在。我的 k8s 是修改源然后 apt-get 下载的，现在来看看这个。文件，后来通过在那篇博客的。中移除了，本质还是一样的。开始网上搜到的是删除。
linux手札--(三）--linux(centos)升级内核
weixin_44911287的博客
07-01 250
# rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org # rpm -Uvh http://www.elrepo.org/elrepo-release-7.0-2.el7.elrepo.noarch.rpm # yum --disablerepo="*" --enablerepo="elrepo-kernel" list avai...
使用代理*** and kubeadm init错误
weixin_30338497的博客
03-21 725
没有代理 可申请AWS免费账户，创建EC2实例，搭建***服务器。 配置代理客户端 参考链接：https://www.zybuluo.com/ncepuwanghui/note/954160 配置Docker代理 ① 创建docker服务配置文件 mkdir -p /etc/systemd/system/dock...
kubeadm init报错 [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/
weixin_57401160的博客
06-04 780
【代码】kubeadm init报错 [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/
kubeadm init 报错[ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kuberne解决办法
qq_63735384的博客
08-15 900
执行kubeadm reset命令后再重新执行初始化命令。
W0225 17:09:39.827262 43878 manifests.go:214] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC" [control-plane] Creating static Pod manifest for "kube-scheduler" W0225 17:09:39.827977 43878 manifests.go:214] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC" [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests" [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s [kubelet-check] Initial timeout of 40s passed. [kubelet-check] It seems like the kubelet isn't running or healthy. [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
07-13
根据您提供的信息，kubeadm正在创建kube-scheduler的静态Pod清单，并在"/etc/kubernetes/manifests"目录下创建本地etcd的静态Pod清单。 然后，kubeadm等待kubelet以静态Pod的形式从"/etc/kubernetes/manifests"目录启动控制平面。这个过程可能需要最多4分钟。 但是，在等待过程中，出现了一些问题。警告信息"W0225 17:09:39.827262 43878 manifests.go:214] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC""和"W0225 17:09:39.827977 43878 manifests.go:214] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC""表示默认的kube-apiserver授权模式为"Node,RBAC"，并且将使用此模式。 警告信息"[kubelet-check] Initial timeout of 40s passed."和"[kubelet-check] It seems like the kubelet isn't running or healthy."表示在初始超时时间内无法连接到kubelet，可能是kubelet未运行或出现了健康问题。 警告信息"[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused."表示尝试通过HTTP请求检查kubelet的健康状态失败，连接被拒绝。 这些警告表明kubelet可能在启动过程中遇到了问题。您可以检查kubelet的日志以获取更多详细信息，可能需要查看kubelet的日志文件以确定具体的问题所在。 如果您需要进一步的帮助，请提供更多信息或具体的错误日志，以便我们能够更好地帮助您解决问题。
评论 4
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

阿蔡BLOG

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值