在k8s中部署jenkins

最新推荐文章于 2024-05-27 09:39:11 发布
最新推荐文章于 2024-05-27 09:39:11 发布
阅读量67 收藏
点赞数
文章标签： kubernetes jenkins 容器 云原生 运维
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/u013657581/article/details/132986131
版权

在k8s中部署jenkins

1.在k8s中部署jenkins

image

注释： https://github.com/jenkinsci/kubernetes-plugin/tree/fc40c869edfd9e3904a9a56b0f80c5a25e988fa1/src/main/kubernetes

2. Jenkins在Kubernetes中动态创建代理

image

​ Jenkins Master/Slave架构

3. 案例，在k8s安装部署jenkins

3.1安装nfs共享磁盘

  • 所有node和磁盘共享服务器都安装nfs

    [root@jenkins-master ~]# yum install nfs-utils -y
[root@k8s-node1 ~]# yum install nfs-utils -y
[root@k8s-node2 ~]# yum install nfs-utils -y
[root@k8s-node3 ~]# yum install nfs-utils -y

  • 配置共享磁盘

    [root@jenkins-master ~]# vim /etc/exports
[root@jenkins-master ~]# cat /etc/exports
/ifs/kubernetes *(rw,no_root_squash)

  • 创建共享磁盘目录

    [root@jenkins-master ~]# mkdir -p /ifs/kubernetes/

  • 每个node和磁盘共享都启动服务和设置开机启动

    # systemctl start nfs      #启动nfs
# systemctl enable nfs     # 设置开机启动
Created symlink from /etc/systemd/system/multi-user.target.wants/nfs-server.service to /usr/lib/systemd/system/nfs-server.service.
3.2 安装pvc动态扩容插件
3.2.1 下载插件

  • 克隆代码

    [root@k8s-master ~]# git clone https://github.com/kubernetes-incubator/external-storage

  • 我这里是先下在了安装包，通过sftp上传

    [root@k8s-master ~]# ll
总用量 212
-rw-------.  1 root root   1857 12月 15 09:32 anaconda-ks.cfg
-rw-r--r--   1 root root 187757 12月 15 12:54 calico.yaml
-rw-r--r--   1 root root   7591 12月 15 13:13 dashboard.yaml
-rw-r--r--   1 root root   6615 12月 16 20:17 ingress_controller.yaml
drwxr-xr-x   2 root root     64 12月 30 16:33 nfs-client
-rw-r--r--.  1 root root   7867 12月 15 10:22 open.sh
drw-r--r--  12 root root    144 12月 30 09:20 yaml
3.2.2 配置文件修改

  • 进入插件里

    [root@k8s-master ~]# cd nfs-client/
[root@k8s-master nfs-client]# ll
总用量 12
-rw-r--r-- 1 root root  225 12月 30 16:33 class.yaml  # 创建存储类
-rw-r--r-- 1 root root  994 12月 30 16:33 deployment.yaml  # 部署插件，需修改里面NFS服务器地址与共享目录
-rw-r--r-- 1 root root 1526 12月 30 16:33 rbac.yaml    # 授权访问apiserver

  • 修改deployment配置文件

    [root@k8s-master nfs-client]# vim deployment.yaml 
[root@k8s-master nfs-client]# cat deployment.yaml 
apiVersion: v1
kind: ServiceAccount
metadata:
  name: nfs-client-provisioner
---
kind: Deployment
apiVersion: apps/v1 
metadata:
  name: nfs-client-provisioner
spec:
  replicas: 1
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: nfs-client-provisioner
  template:
    metadata:
      labels:
        app: nfs-client-provisioner
    spec:
      serviceAccountName: nfs-client-provisioner
      containers:
        - name: nfs-client-provisioner
          # 把国外源修改为国内源
          #image: quay.io/external_storage/nfs-client-provisioner:latest
          image: shichao01/nfs-client-provisioner:latest
          volumeMounts:
            - name: nfs-client-root
              mountPath: /persistentvolumes
          env:
            - name: PROVISIONER_NAME
              value: fuseim.pri/ifs
            - name: NFS_SERVER
              # 修改nfs连接地址
              #value: 192.168.1.61
              value: 10.100.24.85 
            - name: NFS_PATH
              value: /ifs/kubernetes    #共享路径，根据情况修改
      volumes:
        - name: nfs-client-root
          nfs:
            server: 10.100.24.85 
            path: /ifs/kubernetes

  • 修改class文件

    [root@k8s-master nfs-client]# vim class.yaml 
[root@k8s-master nfs-client]# cat class.yaml 
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: managed-nfs-storage
provisioner: fuseim.pri/ifs # or choose another name, must match deployment's env PROVISIONER_NAME'
parameters:
  archiveOnDelete: "true"

  • 配置rbac.yaml文件

    [root@k8s-master nfs-client]# vim rbac.yaml 
[root@k8s-master nfs-client]# cat rbac.yaml 
kind: ServiceAccount
apiVersion: v1
metadata:
  name: nfs-client-provisioner
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: nfs-client-provisioner-runner
rules:
  - apiGroups: [""]
    resources: ["persistentvolumes"]
    verbs: ["get", "list", "watch", "create", "delete"]
  - apiGroups: [""]
    resources: ["persistentvolumeclaims"]
    verbs: ["get", "list", "watch", "update"]
  - apiGroups: ["storage.k8s.io"]
    resources: ["storageclasses"]
    verbs: ["get", "list", "watch"]
  - apiGroups: [""]
    resources: ["events"]
    verbs: ["create", "update", "patch"]
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: run-nfs-client-provisioner
subjects:
  - kind: ServiceAccount
    name: nfs-client-provisioner
    namespace: default
roleRef:
  kind: ClusterRole
  name: nfs-client-provisioner-runner
  apiGroup: rbac.authorization.k8s.io
---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: leader-locking-nfs-client-provisioner
rules:
  - apiGroups: [""]
    resources: ["endpoints"]
    verbs: ["get", "list", "watch", "create", "update", "patch"]
---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: leader-locking-nfs-client-provisioner
subjects:
  - kind: ServiceAccount
    name: nfs-client-provisioner
    # replace with namespace where provisioner is deployed
    namespace: default
roleRef:
  kind: Role
  name: leader-locking-nfs-client-provisioner
  apiGroup: rbac.authorization.k8s.io
3.2.3 启动所有服务
[root@k8s-master nfs-client]# kubectl apply -f .
storageclass.storage.k8s.io/managed-nfs-storage created
serviceaccount/nfs-client-provisioner created
deployment.apps/nfs-client-provisioner created
serviceaccount/nfs-client-provisioner unchanged
clusterrole.rbac.authorization.k8s.io/nfs-client-provisioner-runner created
clusterrolebinding.rbac.authorization.k8s.io/run-nfs-client-provisioner created
role.rbac.authorization.k8s.io/leader-locking-nfs-client-provisioner created
rolebinding.rbac.authorization.k8s.io/leader-locking-nfs-client-provisioner created
3.2.4 查看服务是否启动
[root@k8s-master nfs-client]# kubectl get pods
NAME                                   READY   STATUS    RESTARTS   AGE
configmap-demo-pod                     1/1     Running   0          4d1h
my-hostpath                            1/1     Running   4          2d1h
my-pod                                 1/1     Running   0          7h35m
nfs-client-provisioner-95c9579-m2f69   1/1     Running   0          52s
secret-demo-pod                        1/1     Running   0          3d18h
web-nfs-84f8d7bf8d-6mj75               1/1     Running   0          44h
web-nfs-84f8d7bf8d-n4tpk               1/1     Running   0          44h
web-nfs-84f8d7bf8d-qvd2z               1/1     Running   0          44h
3.2.5 验证服务
[root@k8s-master nfs-client]# kubectl get sc
NAME                  PROVISIONER      RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
managed-nfs-storage   fuseim.pri/ifs   Delete          Immediate           false                  3m46s
3.3 部署jenkins

  • 创建jenkins的yaml配置文件路径

    [root@k8s-master yaml]# mkdir -p jenkins-master
[root@k8s-master yaml]# cd jenkins-master/

  • 创建yaml的配置文件

    • 编写statefulSet的jenkins配置文件

      [root@k8s-master jenkins-master]# vim jenkins-statefulset.yaml 
[root@k8s-master jenkins-master]# cat jenkins-statefulset.yaml 
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: jenkins
  labels:
    name: jenkins
spec:
  serviceName: "jenkins"
  replicas: 1
  updateStrategy:
    type: RollingUpdate
  selector:
    matchLabels:
      name: jenkins
  template:
    metadata:  
      name: jenkins
      labels:
        name: jenkins
    spec:
      terminationGracePeriodSeconds: 10
      serviceAccountName: jenkins
      containers:
        - name: jenkins
          image: jenkins/jenkins:lts-alpine
          imagePullPolicy: Always
          ports:
            - containerPort: 8080
            - containerPort: 50000
          resources:
            limits:
              cpu: 1
              memory: 1Gi
            requests:
              cpu: 0.5
              memory: 500Mi
          env:
            - name: LIMITS_MEMORY
              valueFrom:
                resourceFieldRef:
                  resource: limits.memory
                  divisor: 1Mi
            - name: JAVA_OPTS
              value: -Xmx$(LIMITS_MEMORY)m -XshowSettings:vm -Dhudson.slaves.NodeProvisioner.initialDelay=0 -Dhudson.slaves.NodeProvisioner.MARGIN=50 -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
          volumeMounts:
            - name: jenkins-home
              mountPath: /var/jenkins_home
          livenessProbe:
            httpGet:
              path: /login
              port: 8080
            initialDelaySeconds: 60
            timeoutSeconds: 5
            failureThreshold: 12
          readinessProbe:
            httpGet:
              path: /login
              port: 8080
            initialDelaySeconds: 60
            timeoutSeconds: 5
            failureThreshold: 12
      securityContext:
        fsGroup: 1000
  volumeClaimTemplates:
  - metadata:
      name: jenkins-home
    spec:
      storageClassName: "managed-nfs-storage"
      accessModes: [ "ReadWriteOnce" ]
      resources:
        requests:
          storage: 1Gi

    • 编写service服务配置文件

      [root@k8s-master jenkins-master]# vim jenkins-service.yaml 
[root@k8s-master jenkins-master]# cat jenkins-service.yaml 
apiVersion: v1
kind: Service
metadata:
  name: jenkins
  namespace: default
spec:
  selector:
    name: jenkins
  type: NodePort
  ports:
    -
      name: http
      port: 80
      targetPort: 8080
      protocol: TCP
      nodePort: 30006
    -
      name: agent
      port: 50000
      protocol: TCP

    • 编写ingress对外服务提供配置文件

      [root@k8s-master jenkins-master]# vi jenkins-ingress.yaml
[root@k8s-master jenkins-master]# cat jenkins-ingress.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: jenkins
  annotations:
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    kubernetes.io/tls-acme: "true"
    # 如果上传插件超出默认会报"413 Request Entity Too Large", 增加 client_max_body_size
    nginx.ingress.kubernetes.io/proxy-body-size: 50m
    nginx.ingress.kubernetes.io/proxy-request-buffering: "off"
    # nginx-ingress controller版本小于 0.9.0.beta-18 的配置
    ingress.kubernetes.io/ssl-redirect: "true"
    ingress.kubernetes.io/proxy-body-size: 50m
    ingress.kubernetes.io/proxy-request-buffering: "off"
spec:
  rules:
  - host: jenkins.scajy.org
    http:
      paths:
      - path: /
        backend:
          serviceName: jenkins
          servicePort: 80

    • 配置jenkins的rbac可以访问api资源

      [root@k8s-master jenkins-master]# vim jenkins-rbac.yaml
[root@k8s-master jenkins-master]# cat jenkins-rbac.yaml
---
# 创建名为jenkins的ServiceAccount
apiVersion: v1
kind: ServiceAccount
metadata:
  name: jenkins

---
# 创建名为jenkins的Role，授予允许管理API组的资源Pod
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: jenkins
rules:
- apiGroups: [""]
  resources: ["pods"]
  verbs: ["create","delete","get","list","patch","update","watch"]
- apiGroups: [""]
  resources: ["pods/exec"]
  verbs: ["create","delete","get","list","patch","update","watch"]
- apiGroups: [""]
  resources: ["pods/log"]
  verbs: ["get","list","watch"]
- apiGroups: [""]
  resources: ["secrets"]
  verbs: ["get"]

---
# 将名为jenkins的Role绑定到名为jenkins的ServiceAccount
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: jenkins
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: jenkins
subjects:
- kind: ServiceAccount
  name: jenkins

    • 配置jenkins的account的rbac权限

      [root@k8s-master jenkins-master]# vim jenkins-account.yaml 
[root@k8s-master jenkins-master]# cat jenkins-account.yaml 
# In GKE need to get RBAC permissions first with
# kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin [--user=<user-name>|--group=<group-name>]

---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: jenkins

---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: jenkins
rules:
- apiGroups: [""]
  resources: ["pods"]
  verbs: ["create","delete","get","list","patch","update","watch"]
- apiGroups: [""]
  resources: ["pods/exec"]
  verbs: ["create","delete","get","list","patch","update","watch"]
- apiGroups: [""]
  resources: ["pods/log"]
  verbs: ["get","list","watch"]
- apiGroups: [""]
  resources: ["secrets"]
  verbs: ["get"]

---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: jenkins
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: jenkins
subjects:
- kind: ServiceAccount
  name: jenkins

    • 启动所有配置文件

      [root@k8s-master jenkins]# kubectl apply -f .
Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
ingress.extensions/jenkins created
serviceaccount/jenkins created
Warning: rbac.authorization.k8s.io/v1beta1 Role is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 Role
role.rbac.authorization.k8s.io/jenkins created
Warning: rbac.authorization.k8s.io/v1beta1 RoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 RoleBinding
rolebinding.rbac.authorization.k8s.io/jenkins created
serviceaccount/jenkins unchanged
role.rbac.authorization.k8s.io/jenkins unchanged
rolebinding.rbac.authorization.k8s.io/jenkins unchanged
service/jenkins created
statefulset.apps/jenkins created
3.4 检查服务是否启动
[root@k8s-master jenkins-master]# kubectl get pods,service -o wide
NAME                                          READY   STATUS    RESTARTS   AGE    IP               NODE        NOMINATED NODE   READINESS GATES
pod/jenkins-0                                 1/1     Running   8          127m   10.244.36.72     k8s-node1   <none>           <none>
pod/nfs-client-provisioner-5d99f8d7b9-562ff   1/1     Running   1          12d    10.244.169.130   k8s-node2   <none>           <none>
pod/nginx-6799fc88d8-9fchc                    1/1     Running   0          12d    10.244.169.131   k8s-node2   <none>           <none>

NAME                 TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                        AGE    SELECTOR
service/jenkins      NodePort    10.107.141.118   <none>        80:30006/TCP,50000:32291/TCP   163m   name=jenkins
service/kubernetes   ClusterIP   10.96.0.1        <none>        443/TCP                        13d    <none>
service/nginx        NodePort    10.99.236.10     <none>        80:30939/TCP                   12d    app=nginx
[root@k8s-master jenkins-master]# kubectl get ep
NAME             ENDPOINTS                              AGE
fuseim.pri-ifs   <none>                                 12d
jenkins          10.244.36.72:8080,10.244.36.72:50000   164m
kubernetes       10.100.24.81:6443                      13d
nginx            10.244.169.131:80                      12d
3.5 使用浏览器访问测试

  • 这里先绑定ingress的hosts地址image

  • 使用域名访问测试image

  • 使用IP访问测试image

  • 注释：

    • 到这里，我们发现都可以访问
3.6 浏览器访问进行jenkins安装

image

  • 使用命令查看密码

    [root@k8s-master jenkins-master]# kubectl exec -it jenkins-0 cat /var/jenkins_home/secrets/initialAdminPassword
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
8848ef969b454f849121e5790ea7dd52

imageimage

  • 跳过插件安装image

imageimageimage

七月流星雨
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
jenkins k8s环境部署
weixin_46684804的博客
04-02 7443
前端部署 准备工作： 跟前端开发确认好git地址，代码分支，打出的包名。 1.打开jenkins,选择前端分组环境 2.在部署新应用时，需要创建新的jenkins job,我们可以基于已有的前端项目创建新的项目（简单说就是copy） 选中一个前端项目打开 复制名字 新建任务 3.创建新jenkins job成功后，修改git地址以及变量。 修改git地址 节点限制选择slave1 修改变量，修改完成后点击保存。自此新应用job创建完成。 4.登录172.16.
在K8S上部署Jenkins，用于测试
04-26
在Kubernetes(K8S)平台上部署Jenkins是一个常见的实践，特别是在持续集成/持续部署(CI/CD)场景中。Jenkins作为一个开源自动化服务器，能够帮助我们自动化各种软件开发任务，如构建、测试和部署。接下来，我们将深入...
k8s 部署jenkins
热门推荐
qq_34285557的博客
05-14 1万+
k8s 部署jenkins 本篇主要讲解一下 jenkins 在 k8s 下面是如何部署的，主要对jenkins_home、maven 的一些挂载 和 docker 程序的挂载 ，使其让 pod中的 jenkins 支持 maven docker 等功能，并且当pod删除时不丢失 jenkins_home 1.根据官网 安装 简易版Jenkins 在Jenkins的官网的 安装教程部分其实就有 k8s的安装教程 我们选择使用 YAML文件的方式安装 也可以选择 Helm 安装 、 在其中可
K8S部署jenkins
qq_41296573的博客
10-26 2609
K8S部署jenkins
最详细的k8s中部署Jenkins教程+基于jenkins+k8s(container)实现CI/CD
最新发布
虫虫的博客
05-27 3527
最详细的k8s中部署Jenkins教程+基于jenkins+k8s(container)实现CI/CD
Jenkins使用k8s部署应用
江宁山人的专栏
05-17 5860
3.3.3、宿主机一般都是被K8S控制的Node，因此一般都装有kubernets，因此可以把kubectl命令关在到POD中，使得POD具备执行kubectl命令能力，以控制K8S。在POD容器列表中放了2个Docker镜像，一个是Maven负责java的build，一个是jnlp创建一个jenkins的slave。3.3.2、宿主机上安装了docker，把docker命令挂载到K8S的POD内，使得POD具备了。目的是在jenkins构建的时候，可以自动在K8S内创建一个POD服务于本次构建。
基于jenkins+k8s(container)实现CI/CD
qq_33816243的博客
05-15 488
本文以企业生产环境CICD流程为背景，利用 Jenkins、SonarQube、Harbor、Container、Kubernetes技术，搭建一个完整的 CI/CD 管道，模拟实际生产环境项目开发部署流程，实现持续集成、持续交付和持续部署。
k8s部署jenkins服务.pdf
12-23
k8s部署jenkins服务 本文档主要介绍了如何在k8s平台上部署jenkins服务，并配置jenkins邮件通知功能，以便在构建项目时自动发送构建结果通知邮件。 第一个知识点：k8s平台简介 k8s是一种容器化的自动化部署平台，...
k8s中Jenkins流水线配置自动化部署java+vue等服务.rar
06-10
通过Jenkins流水线发布Java服务到k8s集群上，主要是通过在Jenkins slave上集成宿主机docker，helm，kubectl工具来打包镜像部署服务到k8s集群上。
k8s1.16的jenkins部署java项目ci(cd手动)笔记文档详细总结
06-29
在这篇笔记文档中，我们将详细介绍如何使用Jenkins部署Java项目到k8s集群，实现CI/CD手动部署。该文档将涵盖k8s1.16、Jenkins、Java项目的部署、CI/CD手动部署等方面的知识点。 一、规划 在开始部署Java项目之前，...
在K8s上成功部署jenkins相关scripts
05-25
在Kubernetes（K8s）平台上部署Jenkins是现代DevOps实践中常见的场景。Jenkins作为一个流行的持续集成/持续部署（CI/CD）工具，能够帮助自动化软件开发流程，包括构建、测试和部署。本篇文章将深入探讨如何在...
k8s部署jenkins
crontab_e的博客
11-28 1422
【代码】k8s部署jenkins。
基于K8s构建Jenkins持续集成平台（部署流程）（转了一点）
LuckyTHP
12-02 2047
jenkins
【kubernetes部署jenkins】
Vergil的博客
08-19 473
使用确保运行状态为正常。
Jenkins流水线整合k8s实现代码自动集成和部署
zhangshenglu1的博客
05-19 4151
这里先要搭建好一个K8s集群，笔者这边就采用使用了一个一主一丛的k8s集群，k8s集群的版本使用1.19.5版本，服务器的配置：2核4G，操作系统: CentOS Linux release 7.9.2009 (Core)# 您也可以使用下面的指令，唯一的区别是，该指令使用华为云的镜像仓库替代 docker hub 分发 Kuboard 所需要的镜像。C:\Windows\System32\drivers\etc\hosts文件。6、在k8s的master和worker节点上配置docker的私服地址。
基于K8s平台部署Jenkins环境
redrose2100的博客
05-25 482
本文详细描述了基于k8s平台部署jenkins的操作步骤
基于jenkins+k8s实现devops
Timmy的博客
09-20 1194
由于jenkins运行在k8s上能够更好的利用动态slave进行构建。所以写了个部署教程，亲测无坑
k8s 部署Jenkins项目
weixin_69654831的博客
01-13 791
要求：当前集群配置了storageClass，并已指定默认的storageClass，一般情况下，创建的storageClass即为默认类 指定默认storageClass的方式。将准备好的插件包，替换掉对应的pv数据卷中的plugins目录。在系统管理的下方有未归类的插件。
【k8s实战一】Jenkins 部署应用到 Kubernetes
nerdsu的博客
03-18 2254
阅读目录 01 本文主旨 02 CI/CD流程 03 准备虚拟机 04 部署registry 05 配置maven 06 Tomcat部署Jenkins 07 部署Kubernetes集群 08 准备Demo 09 创建Jenkins流水线项目 部署与验证 总结 参考 【k8s实战一】Jenkins 部署应用到 Kubernetes 01 本文主旨 目标是演示整个Jenkins从源码构建镜像到部署镜像到Kubernetes集群过程。 为了简化流程与容易重现文中效果，做出如下操作

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值