k8s部署MinIO Operator

最新推荐文章于 2024-02-27 17:30:27 发布
最新推荐文章于 2024-02-27 17:30:27 发布
阅读量980 收藏 1
点赞数
文章标签： linux 运维 java
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_55154296/article/details/125440826
版权

Minio Operator

环境

[root@master-10 minio]# kubectl get no -o wide
NAME        STATUS   ROLES    AGE     VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION           CONTAINER-RUNTIME
master-10   Ready    master   104d    v1.19.3   192.168.91.10   <none>        CentOS Linux 7 (Core)   3.10.0-1160.el7.x86_64   docker://19.3.15
node-11     Ready    node     44m     v1.19.3   192.168.91.11   <none>        CentOS Linux 7 (Core)   3.10.0-1160.el7.x86_64   docker://19.3.15
node-12     Ready    node     104d    v1.19.3   192.168.91.12   <none>        CentOS Linux 7 (Core)   3.10.0-1160.el7.x86_64   docker://19.3.15
node-13     Ready    node     3d16h   v1.19.3   192.168.91.13   <none>        CentOS Linux 7 (Core)   3.10.0-1160.el7.x86_64   docker://19.3.15
node-14     Ready    node     3d16h   v1.19.3   192.168.91.14   <none>        CentOS Linux 7 (Core)   3.10.0-1160.el7.x86_64   docker://19.3.15
[root@master-10 minio]# kubectl top no 
NAME        CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%   
master-10   183m         2%     2148Mi          27%       
node-11     74m          1%     807Mi           22%       
node-12     76m          1%     876Mi           23%       
node-13     86m          2%     874Mi           23%       
node-14     88m          2%     779Mi           21%

前期准备

创建目录

#db001
mkdir -p /home/data/local-volume/minio/v1/node-pv0
#master1
mkdir -p /home/data/local-volume/minio/v1/node-pv1
#node001
mkdir -p /home/data/local-volume/minio/v1/node-pv2
#node002
mkdir -p /home/data/local-volume/minio/v1/node-pv3

创建PV和SC

#v1-node-pv-sc.yaml
#静态存储
apiVersion: v1
kind: PersistentVolume
metadata:
   name: minio-node-v1-pv0
spec:
   capacity:
      storage: 10Gi  
   volumeMode: Filesystem
   accessModes:
   - ReadWriteOnce
   persistentVolumeReclaimPolicy: Retain
   storageClassName: node-local-storage
   local:
      path: /home/data/local-volume/minio/v1/node-pv0 
   nodeAffinity:
      required:
         nodeSelectorTerms:
         - matchExpressions:
            - key: kubernetes.io/hostname
              operator: In
              values:
              - db001
---
apiVersion: v1
kind: PersistentVolume
metadata:
   name: minio-node-v1-pv1
spec:
   capacity:
      storage: 10Gi
   volumeMode: Filesystem
   accessModes:
   - ReadWriteOnce
   persistentVolumeReclaimPolicy: Retain
   storageClassName: node-local-storage
   local:
      path: /home/data/local-volume/minio/v1/node-pv1
   nodeAffinity:
      required:
         nodeSelectorTerms:
         - matchExpressions:
            - key: kubernetes.io/hostname
              operator: In
              values:
              - master1

---
apiVersion: v1
kind: PersistentVolume
metadata:
   name: minio-node-v1-pv2
spec:
   capacity:
      storage: 10Gi
   volumeMode: Filesystem
   accessModes:
   - ReadWriteOnce
   persistentVolumeReclaimPolicy: Retain
   storageClassName: node-local-storage
   local:
      path: /home/data/local-volume/minio/v1/node-pv2
   nodeAffinity:
      required:
         nodeSelectorTerms:
         - matchExpressions:
            - key: kubernetes.io/hostname
              operator: In
              values:
              - node001
---
apiVersion: v1
kind: PersistentVolume
metadata:
   name: minio-node-v1-pv3
spec:
   capacity:
      storage: 10Gi
   volumeMode: Filesystem
   accessModes:
   - ReadWriteOnce
   persistentVolumeReclaimPolicy: Retain
   storageClassName: node-local-storage
   local:
      path: /home/data/local-volume/minio/v1/node-pv3 
   nodeAffinity:
      required:
         nodeSelectorTerms:
         - matchExpressions:
            - key: kubernetes.io/hostname
              operator: In
              values:
              - node002
---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
    name: node-local-storage
provisioner: kubernetes.io/no-provisioner
volumeBindingMode: WaitForFirstConsumer

创建namespace

[root@master1 minio]# kubectl create namespace minio-node
namespace/minio-node created

检查

[root@master1 minio]# kubectl get sc
NAME                 PROVISIONER                    RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
node-local-storage   kubernetes.io/no-provisioner   Delete          WaitForFirstConsumer   false                  40s

[root@master1 minio]# kubectl get pv,ns -A | grep minio
persistentvolume/minio-node-v1-pv0   10Gi       RWO            Retain           Available                         node-local-storage            10s
persistentvolume/minio-node-v1-pv1   10Gi       RWO            Retain           Available                         node-local-storage            10s
persistentvolume/minio-node-v1-pv2   10Gi       RWO            Retain           Available                         node-local-storage            10s
persistentvolume/minio-node-v1-pv3   10Gi       RWO            Retain           Available                         node-local-storage            10s
namespace/minio-node                Active   26s
namespace/minio-operator            Active   4d23h

安装MinIO Operator

kubecrew

  1. Make sure that git is installed.

  2. Run this command to download and install krew:

    项目地址：https://github.com/kubernetes-sigs/krew/releases

wget https://github.com/kubernetes-sigs/krew/releases/download/v0.4.1/krew.tar.gz
wget https://github.com/kubernetes-sigs/krew/releases/download/v0.4.1/krew.yaml
tar -zxvf krew.tar.gz
./krew-linux_amd64 install --manifest=krew.yaml --archive=krew.tar.gz

  3. Add the $HOME/.krew/bin directory to your PATH environment variable. To do this, update your .bashrc or .zshrc file and append the following line:

    export PATH="${KREW_ROOT:-$HOME/.krew}/bin:$PATH"
echo 'export PATH="${KREW_ROOT:-$HOME/.krew}/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

    and restart your shell.

  4. Run kubectl krew to check the installation.

    kubectl krew

#krew会依赖git，注意git是否正确安装且写入环境变量
[root@master-10 minio]# kubectl krew update
Updated the local copy of plugin index.
#被墙容易失败,多试几次
[root@master-10 minio]# kubectl krew install minio
F0310 11:03:25.508814   73405 root.go:58] failed to update the local index: fetch index at "/root/.krew/index" failed: command execution failure, output="fatal: unable to access 'https://github.com/kubernetes-sigs/krew-index.git/': TCP connection reset by peer\n": exit status 128
[root@master-10 minio]# kubectl krew install minio
Updated the local copy of plugin index.
Installing plugin: minio
Installed plugin: minio
\
 | Use this plugin:
 | 	kubectl minio
 | Documentation:
 | 	https://github.com/minio/operator/tree/master/kubectl-minio
 | Caveats:
 | \
 |  | * For resources that are not in default namespace, currently you must
 |  |   specify -n/--namespace explicitly (the current namespace setting is not
 |  |   yet used).
 | /
/
WARNING: You installed a plugin from the krew-index plugin repository.
   These plugins are not audited for security by the Krew maintainers.
   Run them at your own risk.
   
   
#######离线
https://github.com/minio/operator/releases
wget https://github.com/minio/operator/releases/download/v4.4.11/kubectl-minio_4.4.11_linux_amd64 -O kubectl-minio
chmod +x kubectl-minio
mv kubectl-minio /usr/local/bin/

#Run the following command to verify installation of the plugin:
[root@master-10 minio]# kubectl minio version
v4.4.11

#Run the following command to initialize the Operator:
[root@master-10 minio]# kubectl minio init --cluster-domain=cluster.saas
namespace/minio-operator created
serviceaccount/minio-operator created
clusterrole.rbac.authorization.k8s.io/minio-operator-role created
clusterrolebinding.rbac.authorization.k8s.io/minio-operator-binding created
customresourcedefinition.apiextensions.k8s.io/tenants.minio.min.io created
service/operator created
deployment.apps/minio-operator created
serviceaccount/console-sa created
clusterrole.rbac.authorization.k8s.io/console-sa-role created
clusterrolebinding.rbac.authorization.k8s.io/console-sa-binding created
configmap/console-env created
service/console created
deployment.apps/console created
-----------------

To open Operator UI, start a port forward using this command:

kubectl minio proxy -n minio-operator 
-----------------
[root@master-10 ~]# kubectl get pods -n minio-operator
NAME                              READY   STATUS    RESTARTS   AGE
console-58b7dc8856-xlcbf          1/1     Running   2          22h
minio-operator-849f8cf8b8-ldq9x   1/1     Running   2          21h
minio-operator-849f8cf8b8-wf4qw   1/1     Running   2          22h

进入控制台

#新建终端
[root@master-10 minio]# kubectl minio proxy -n minio-operator 
Starting port forward of the Console UI.

To connect open a browser and go to http://localhost:9090

Current JWT to login: eyJhbGciOiJSUzI1NiIsImtpZCI6InY4NkNBSHptSUZhbXIyS2VWMk4yc3Rua2M0bUQyc2tYZVVHVVVDWEE1Y3cifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJtaW5pby1vcGVyYXRvciIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJjb25zb2xlLXNhLXRva2VuLTkyODU3Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQubmFtZSI6ImNvbnNvbGUtc2EiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiI4OGI1MDhjMS01YmI0LTQ0MDAtOWIyZi05YTMxYzZmZWJiYmMiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6bWluaW8tb3BlcmF0b3I6Y29uc29sZS1zYSJ9.s0ycCfkyvGmhxKJULjTz56yipt0T_viP5GTiTfTS3yBawYpiL-d9usO-Ot9H-7gRTKT9euykENeQF3D4lhpSeVlATD0RjFwY4D-Ks7MT3v2UWJ5j5GItpY6qMHsS-cKuRVosSRhgyFf9Fc4He_CbY8e5GdbWTW-0P138FmEPcrogrTw37AjHySjKbXrLzGEL84rdGTL2lgRpmPwQWXYerchNaGNFO5ir3PJGf7PYkmKfDByq02P_yhT4U70JgLhNgPwT9i0MzHnSORUFKyuNRaIoSW6-tgh7Wk2eEUTZI79QgIsaJ6GH4-oDNZcSf6mHKNZbEkaUt6VgoBR0VYZhJg



Forwarding from 0.0.0.0:9090 -> 9090

#复制JWT进入控制台
http://192.168.91.10:9090/

创建租户

minio-operator

minio-node
UfrFvdv9Wturm5FO
A6UNtGUr3QESHLzkSTwqdaNUNiyNRpBt

命令行方式

[root@master-10 minio]# kubectl minio tenant create tenant1 --namespace minio-tenant-1 --storage-class local-storage --servers 4 --volumes 4 --capacity 40Gi

Tenant 'tenant1' created in 'minio-tenant-1' Namespace

  Username: admin 
  Password: 933c9ff5-3ff5-4331-b95c-477830cf8825 
  Note: Copy the credentials to a secure location. MinIO will not display these again.

+-------------+-----------------+----------------+--------------+--------------+
| APPLICATION | SERVICE NAME    | NAMESPACE      | SERVICE TYPE | SERVICE PORT |
+-------------+-----------------+----------------+--------------+--------------+
| MinIO       | minio           | minio-tenant-1 | ClusterIP    | 443          |
| Console     | tenant1-console | minio-tenant-1 | ClusterIP    | 9443         |
+-------------+-----------------+----------------+--------------+--------------+

检查

[root@master1 minio]# kubectl get all -n minio-node 
NAME                      READY   STATUS    RESTARTS   AGE
pod/minio-node-pool-0-0   1/1     Running   0          57s
pod/minio-node-pool-0-1   1/1     Running   0          56s
pod/minio-node-pool-0-2   1/1     Running   0          56s
pod/minio-node-pool-0-3   1/1     Running   0          56s

NAME                         TYPE           CLUSTER-IP     EXTERNAL-IP   PORT(S)          AGE
service/minio                LoadBalancer   10.233.31.36   <pending>     80:31819/TCP     59s
service/minio-node-console   LoadBalancer   10.233.38.9    <pending>     9090:30786/TCP   58s
service/minio-node-hl        ClusterIP      None           <none>        9000/TCP         57s

NAME                                 READY   AGE
statefulset.apps/minio-node-pool-0   4/4     57s

#######
The minio service corresponds to the MinIO Tenant service. Applications should use this service for performing operations against the MinIO Tenant.
The minio-tenant-1-console service corresponds to the MinIO Console. Administrators should use this service for accessing the MinIO Console and performing administrative operations on the MinIO Tenant.
The minio-tenant-1-hl corresponds to a headless service used to facilitate communication between Pods in the Tenant.

删掉重建

[root@master1 minio]# kubectl delete pvc --all -n minio-node
[root@master1 minio]# kubectl delete -f v1-node-pv-sc.yaml 

[root@master1 minio]# kubectl delete secrets -n minio-node  minio-node-secret
secret "minio-node-secret" deleted

#新
lmfmRBFopIQS0Pmn
ZP823zRd7cz85rkcHfhyEQDIaq2OOAav

创建ingress

openssl genrsa -out tls.key 2048

#创建密钥    域名为www.minio.com
openssl req -new -x509 -key tls.key -out tls.crt -subj /C=CN/ST=Guangdong/L=Guangzhou/O=devops/CN=www.minio.com
#创建secret
kubectl create secret tls minio-secret --cert=tls.crt --key=tls.key  -n minio-node

[root@master1 minio]# kubectl create secret tls minio-secret --cert=tls.crt --key=tls.key  -n minio-node
secret/minio-secret created

ingress.yaml

[root@master1 minio]# cat minio-node-ingress.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    nginx.ingress.kubernetes.io/use-regex: "true"
  name: minio-ingress
  namespace: minio-node
spec:
#  tls:
#  - hosts: 
#    - www.minio.com
#    secretName: minio-secret
  rules:
  - host: www.minio.com
    http:
      paths:
      - path: /
        backend:
          serviceName: minio
          servicePort: 80

创建ingress

[root@master1 minio]# kubectl create -f minio-node-ingress.yaml 
Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
ingress.extensions/minio-ingress created

访问tenant

在windows端设置域名解析

192.168.0.84 www.minio.com

浏览器访问

Python SDK

Download using pip

pip3 install minio

Download source

git clone https://github.com/minio/minio-py.git
cd minio-py
python3 setup.py install  #linux

file_uploader.py

from minio import Minio
from minio.error import S3Error


def main():
    # Create a client with the MinIO server playground, its access key
    # and secret key.
    client = Minio(
        "www.minio.com",
        access_key="UfrFvdv9Wturm5FO",
        secret_key="A6UNtGUr3QESHLzkSTwqdaNUNiyNRpBt",
        secure="false",
    )

    # Make 'test1' bucket if not exist.
    found = client.bucket_exists("test1")
    if not found:
        client.make_bucket("test1")
    else:
        print("Bucket 'test1' already exists")

    # Upload '/root/kube-yaml/minio/v1-node-pv-sc.yaml' as object name
    # 'v1-node-pv-sc.yaml' to bucket 'test1'.
    client.fput_object(
        "test1", "v1-node-pv-sc.yaml", "/root/kube-yaml/minio/v1-node-pv-sc.yaml",
    )
    print(
        "'/root/kube-yaml/minio/v1-node-pv-sc.yaml' is successfully uploaded as "
        "object 'v1-node-pv-sc.yaml' to bucket 'test1'."
    )


if __name__ == "__main__":
    try:
        main()
    except S3Error as exc:
        print("error occurred.", exc)

Run File Uploader

$ python3 file_uploader.py
'/home/user/Photos/asiaphotos.zip' is successfully uploaded as object 'asiaphotos-2015.zip' to bucket 'asiatrip'.

$ mc ls play/test1/
[2016-06-02 18:10:29 PDT]  82KiB asiaphotos-2015.zip
BingChat
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
运算符：kubernetes（k8s）的MinIO运算符https：kubernetes.io
02-18
MinIO运算符 MinIO是Kubernetes原生的高性能对象存储，具有与S3兼容的API。 MinIO Kubernetes Operator支持将MinIO租户部署到私有和公共云基础架构（“混合”云）上。 重要说明：本文档反映了MinIO Operator的最新前沿版本。 API和语法可能与以前的版本不同。 有关以前版本的文档，请访问该版本标签中的文档： 目录 建筑学 每个MinIO租户代表Kubernetes集群内的一个独立的MinIO对象存储。 下图描述了部署到Kubernetes中的MinIO租户的架构： MinIO提供了多种访问和管理MinIO租户的方法： MinIO控制台 MinIO控制台提供了用于与MinIO租户交互的图形用户界面（GUI）。 MinIO租户的管理员可以通过控制台执行各种任务，包括用户创建，策略配置和存储桶复制。 控制台还提供了有关租户健康状
通过minio operator在k8s中部署minio tenant集群
小单的博客专栏
02-22 3067
MinIO是kubernetes原生的高性能对象存储，兼容Amazon的s3 API。MinIO Operator是一个工具，该工具扩展了k8s的api,可以通过minio operator在公有云和私有云上来部署MinIO Tenants本文就通过一步一步的操作，来演示如何在一个现存的k8s集群中部署一个minio集群。
通过operator的方式在k8s中部署minio
weixin_37573420的博客
04-24 794
MinIO 提供高性能、兼容 S3 的对象存储，原生于 Kubernetes文档URL：https://min.io/docs/minio/kubernetes/upstream/operations/installation.html版本说明 - 服务版本说明 - 测试工具。
506. 【kubernetes】在-k8s-集群上部署-Minio-Operator-和-Minio-Plugin
七镜的博客
06-08 664
现在可以通过第三步里的“Create”按钮创建集群了。
minio-operator部署minio服务，并用Java客户端访问minio
ll535299的博客
06-27 2527
本文介绍如何用minio-operator来部署minio服务，并浏览器和Java客户端来访问minio上的数据 安装krew插件（可选） 脚本命令安装 安装minio-operator 安装minio-operator有两种方式第一种(不推荐)：可以用刚才安装的krew插件来安装kubectl minio命令插件，然后用插件来安装。 第二种（推荐）：下载指定版本脚本安装地址： https://github.com/minio/operator/tags.........
minio安装使用
weixin_42507440的博客
01-10 1428
minio单机部署和容器部署
minio分布式部署搭建文档及安装程序
02-16
1：包含minio分布式部署搭建文档.doxc文档 2：包含minio安装文件
Minio集群部署安装包
04-19
Minio集群部署安装包。Minio集群部署安装包。Minio集群部署安装包。Minio集群部署安装包。Minio集群部署安装包。Minio集群部署安装包。Minio集群部署安装包。Minio集群部署安装包。Minio集群部署安装包。Minio集群...
Minio技术知识点：Mac如何安装和部署Minio服务端
10-14
Minio技术知识点：Mac如何安装和部署Minio服务端
minio 安装部署包 + 部署文档
最新发布
03-21
minio 安装部署包 + 部署文档（单机+集群）
【Kubernetes】k8s使用minio作为对象存储
m0_58096123的博客
02-27 1563
（1）安装kubectl-minio插件自选minio-operaterd的版本下载包访问地址：http://ip:9090。
linux部署minio对象存储、docker部署minio象存储、k8s部署minio象存储
MssGuo的博客
10-16 2081
minio有两个端口，一个 minio servers的端口，也就是api端口，默认9000，一个是minio console端口，即控制台端口，控制台端口可以自定义，控制台端口用于外部浏览器访问，不同版本minio的默认控制台端口可能不同，如有的是9001，有的是9090，浏览器使用9000端口访问，默认会跳转到控制台端口。linux部署minio:1、使用linux部署minio，单台单磁盘部署minion，存在服务器宕机、磁盘损坏的情况;
kubernetes部署minio对象存储
热门推荐
IT
12-21 1万+
Kubernetes部署MinIO Kubernetes的部署和状态集提供了在独立，分布式模式下部署MinIO服务器的完美平台。 在Kubernetes上部署MinIO有多种选择，您可以选择最适合您的。 参考：https://github.com/minio/charts 部署前提条件: 1、需要准备k8s集群，并且包含足够多的节点，如4个节点的集群 [root@jenkins ~]# kubectl get nodes NAME STATUS ROLES AGE VERS
K8S部署Minio经验心得
pleong的博客
06-17 5874
[Minio](http://www.minio.org.cn/)是云原生友好的开源分布式对象存储解决方案。本文介绍了在K8S中部署Minio遇到的问题和处理经验。
k8s环境，linux环境部署chaosblade
weixin_44268873的博客
09-05 1910
混沌测试linux环境安装chaosblade，k8s集群环境安装chaosblade-operator
【Kubernetes】K8s集群operator模式安装minio
cnskylee的博客
09-01 1341
尝试过使用网上分享的minio.yaml安装minio集群，但是结果都失败了，主要原因是访问不了minio的管理页面。下面的yaml就是网上各类技术文章使用的最多的一个，有些yaml连nodePort都没有配置，执行了，然后还能通过nodePort访问到minio的管理页面。 apiVersion: v1 kind: Service metadata: name: minio labels: app: minio spec: clusterIP: None por...
Kubernetes部署Minio集群存储的选择，使用DirectPV CSI作为分布式存储的最佳实践
cosann的博客
11-05 6240
Kubernetes部署Minio集群存储的选择，使用DirectPV CSI作为分布式存储的最佳实践
来了解一下 k8s 的 Operator 模式
ChaITSimpleLove的博客
10-09 4891
在 `Kubernetes` 生态中还有一种更灵活、编程友好的解决方案 -- `Operator`， 它能让使用者根据自己应用的特性定义应用对象和管理对象的控制器。
k8s 部署 minio
Jerry00713的博客
07-27 1万+
6、按照次特性，可以修改deployment资源，增加Nodename固定在那个节点运行，修改svc资源设置nodeport，共享网络名称空间，让pod的9000端口映射宿主机的某一个端口，直接访问宿主机的端口，通过即可。5、总上所述，对比新版本minio特性，说明了32154是Console的端口，而且在kill掉这个pod，在启动一个新的，发现Console端口会变化，说明Console端口是随机的。2、service资源中代理9000端口、Console端口。新版本如何编写资源配置清单。.......
k8s 部署minio
08-23
- *1* [k8s部署minio](https://blog.csdn.net/qq_36200932/article/details/127314926)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_...

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值