一键安装kubernetes 1.13.0 集群

最新推荐文章于 2024-05-20 22:23:45 发布
最新推荐文章于 2024-05-20 22:23:45 发布
阅读量206 收藏
点赞数
文章标签： 运维 json 操作系统
原文链接：https://my.oschina.net/polly/blog/3002264
版权

为什么80%的码农都做不了架构师？>>>   hot3.png

直奔主题

  • 操作系统：Centos 7.5
  • 首先看一下master节点IP，修改下面的脚本中的地址。
  • 复制的时候注意，使用纯文本，不要动空格，yaml就是这么烦人。
  • 重要的事情说三遍：不用翻墙，不用翻墙，不用翻墙。

首先创建安装脚本

文件名 ./install-k8s.sh，内容如下：

# 重要提示: 请修改主节点，即可本机IP
MASTER_IP=192.168.33.30

cat << EOF > /etc/yum.repos.d/CentOS-Base.repo
[base]
name=CentOS-\$releasever - Base
baseurl=https://mirrors.tuna.tsinghua.edu.cn/centos/\$releasever/os/\$basearch/
#mirrorlist=http://mirrorlist.centos.org/?release=\$releasever&arch=\$basearch&repo=os
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#released updates
[updates]
name=CentOS-\$releasever - Updates
baseurl=https://mirrors.tuna.tsinghua.edu.cn/centos/\$releasever/updates/\$basearch/
#mirrorlist=http://mirrorlist.centos.org/?release=\$releasever&arch=\$basearch&repo=updates
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#additional packages that may be useful
[extras]
name=CentOS-\$releasever - Extras
baseurl=https://mirrors.tuna.tsinghua.edu.cn/centos/\$releasever/extras/\$basearch/
#mirrorlist=http://mirrorlist.centos.org/?release=\$releasever&arch=\$basearch&repo=extras
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-\$releasever - Plus
baseurl=https://mirrors.tuna.tsinghua.edu.cn/centos/\$releasever/centosplus/\$basearch/
#mirrorlist=http://mirrorlist.centos.org/?release=\$releasever&arch=\$basearch&repo=centosplus
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

EOF

cat << EOF > /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg

EOF

cat << EOF > /etc/yum.repos.d/docker-ce.repo
[docker-ce-stable]
name=Docker CE Stable - \$basearch
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/\$basearch/stable
enabled=1
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-stable-debuginfo]
name=Docker CE Stable - Debuginfo \$basearch
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/debug-\$basearch/stable
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-stable-source]
name=Docker CE Stable - Sources
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/source/stable
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

[docker-ce-edge]
name=Docker CE Edge - \$basearch
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/\$basearch/edge
enabled=0
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg

EOF

cat << EOF | tee /etc/yum.repos.d/epel.repo
[epel]
name=Extra Packages for Enterprise Linux 7 - \$basearch
baseurl=https://mirrors.tuna.tsinghua.edu.cn/epel/7/\$basearch
#mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=\$basearch
failovermethod=priority
enabled=1
gpgcheck=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7

[epel-debuginfo]
name=Extra Packages for Enterprise Linux 7 - \$basearch - Debug
baseurl=https://mirrors.tuna.tsinghua.edu.cn/epel/7/\$basearch/debug
#mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-debug-7&arch=\$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
gpgcheck=1

[epel-source]
name=Extra Packages for Enterprise Linux 7 - \$basearch - Source
baseurl=https://mirrors.tuna.tsinghua.edu.cn/epel/7/SRPMS
#mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-source-7&arch=\$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
gpgcheck=1

EOF


yum install -y --setopt=obsoletes=0 docker-ce-18.06.1.ce-3.el7
systemctl enable docker
systemctl start docker

setenforce 0

sed -i s/^SELINUX=.*/SELINUX=disabled/ /etc/selinux/config

swapoff -a && sysctl -w vm.swappiness=0

sed -i -e "s/\(.*swap.*\)/#\1/" /etc/fstab

cat << EOF | tee /etc/sysctl.d/k8s.conf
net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sysctl -p /etc/sysctl.d/k8s.conf

yum install -y kubeadm-1.13.0 kubectl-1.13.0 kubelet-1.13.0
systemctl enable kubelet.service

if [ "$1"x = "node"x ]; then
  echo init node ok. please run join cmd.
  exit;
fi

cat << EOF > kubeadm-init.yaml
apiVersion: kubeadm.k8s.io/v1beta1
kind: ClusterConfiguration
kubernetesVersion: v1.13.0
imageRepository: pollyduan
apiServer:
  certSANs:
  - $MASTER_IP
controlPlaneEndpoint: $MASTER_IP:6443
networking:
  podSubnet: "10.244.0.0/16"
EOF

cat << EOF > kube-flannel.yml
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: flannel
rules:
  - apiGroups:
      - ""
    resources:
      - pods
    verbs:
      - get
  - apiGroups:
      - ""
    resources:
      - nodes
    verbs:
      - list
      - watch
  - apiGroups:
      - ""
    resources:
      - nodes/status
    verbs:
      - patch
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: flannel
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: flannel
subjects:
- kind: ServiceAccount
  name: flannel
  namespace: kube-system
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: flannel
  namespace: kube-system
---
kind: ConfigMap
apiVersion: v1
metadata:
  name: kube-flannel-cfg
  namespace: kube-system
  labels:
    tier: node
    app: flannel
data:
  cni-conf.json: |
    {
      "name": "cbr0",
      "plugins": [
        {
          "type": "flannel",
          "delegate": {
            "hairpinMode": true,
            "isDefaultGateway": true
          }
        },
        {
          "type": "portmap",
          "capabilities": {
            "portMappings": true
          }
        }
      ]
    }
  net-conf.json: |
    {
      "Network": "10.244.0.0/16",
      "Backend": {
        "Type": "vxlan"
      }
    }
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-amd64
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      hostNetwork: true
      nodeSelector:
        beta.kubernetes.io/arch: amd64
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: pollyduan/flannel:v0.10.0-amd64
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: pollyduan/flannel:v0.10.0-amd64
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        - --iface=eth1
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: true
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-arm64
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      hostNetwork: true
      nodeSelector:
        beta.kubernetes.io/arch: arm64
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.10.0-arm64
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.10.0-arm64
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: true
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-arm
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      hostNetwork: true
      nodeSelector:
        beta.kubernetes.io/arch: arm
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.10.0-arm
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.10.0-arm
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: true
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-ppc64le
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      hostNetwork: true
      nodeSelector:
        beta.kubernetes.io/arch: ppc64le
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.10.0-ppc64le
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.10.0-ppc64le
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: true
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-s390x
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      hostNetwork: true
      nodeSelector:
        beta.kubernetes.io/arch: s390x
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.10.0-s390x
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.10.0-s390x
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: true
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
EOF

kubeadm init --config kubeadm-init.yaml

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

kubectl apply -f kube-flannel.yml

rm -f kubeadm-init.yaml kube-flannel.yml

master 节点

./install-k8s.sh

node 节点

首先，执行如下命令，安装必要的docker和kubernetes：

./install-k8s.sh node

然后直接执行初始化集群打印的日志中的join命令即可，形如：

kubeadm join 192.168.33.30:6443 --token s9j0fe.gvvwvjz66gmuxqeg --discovery-token-ca-cert-hash sha256:e77769812743386d71de272aafec24d8e3406691925cc6e312dedc139a4d521b
  • 注意：以上命令不是你拿去直接用的，要从你master节点上初始化完成后打印的，复制你自己的再执行。

转载于:https://my.oschina.net/polly/blog/3002264

weixin_33883178
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
用kubeadm安装最新Kubernetes1.13.0【centos7.3 在线装docker，kubeadm，kubectl，kubelet，dashboard】kubernetesv1.13.0-附件资源
03-02
用kubeadm安装最新Kubernetes1.13.0【centos7.3 在线装docker，kubeadm，kubectl，kubelet，dashboard】kubernetesv1.13.0-附件资源
k8s-auto-kubernetes/k8s一键安装
12-15
kubernetes/k8s自动安装程序，版本对应:v1.18.2，linux环境 使用kubeadm安装，改程序若环境不符合要求，是不能一键安装的，需按照程序指示分布安装，该程序是为了搭建测试环境时，简化繁琐的配置时所用，不能用作生产使用，造成一切后果，本人不承担任何责任；此集成是为了让小伙伴们学习了解k8s运作机理时，可快速部署，省去多步手动配置所写； 程序逐渐完善中有疑问，欢迎私信我解决... 程序安装会进行环境检查，若不满足要求则会提示更改后方能继续执行（具体见文件说明）；
单机快速体验k8s集群的测试环境
putixiao的博客
12-13 1056
快速指南 以下为快速体验k8s集群的测试、开发环境–单节点部署(aio)，国内环境下比官方的minikube方便、简单很多。 1.基础系统配置 准备一台虚机配置内存2G/硬盘30G以上 最小化安装Ubuntu 16.04 server或者CentOS 7 Minimal 配置基础网络、更新源、SSH登录等 2.下载文件 # 下载工具脚本easzup，举例使用kubeasz版本2.0.2 exp...
k8s 一键安装Kubernetes集群
u014644574的博客
10-30 1228
Kubernetes - 一键安装Kubernetes集群
Kubeadm一键部署安装kubernetes
最新发布
qq_57093716的博客
05-20 841
Kubeadm一键部署安装kubernetes
一键安装k8s ！！！
FK_凡柯的博客
07-06 557
一键安装k8s ！！！ 傻瓜式安装
一键安装k8s脚本
清雨小竹
05-09 1928
4.安装完毕可以在master节点上查看状态：kubectl get nodes。1.master节点安装脚本：install_k8s_master.sh。2.node节点安装脚本：install_k8s_node.sh。3.安装完成master节点后会提示加入节点的命令类似这样。安装过程中会有根据提示要求键盘输入。在各个node节点上执行命令即可。
k8s-使用kube-install一键部署(亲测超详细)
program哲学
12-11 3542
详细介绍k8s部署环境介绍及一键安装脚本kube-install, 支持高度可用的多个kubernetes集群可以在二进制模式下一键离线安装，也可以计划安装、添加kubernets节点、删除kubernete节点、销毁kubernetesmaster、重建kubernetes-master和卸载集群
k8s学习-k8s初识、Centos下集群安装与一键离线安装
关注网络安全、云原生安全
04-30 2720
K8s概念 Namespace:命令空间，相当于把一个集群虚拟成多个集群，部分资源具有隔离性Pod:K8s最小单元，可以简单理解为一个、多个或一组容器的集合。 Deployment:无状态应用控制器，可以随意重启的服务等，例如，可放置HTML5文件 StatefulSet:有状态应用控制器，提供固定标识符，可放置redis集群等 DaemonSet:守护进程控制器 Service:逻辑上的一组Pod，用于集群服务通信 Ingress：集群服务入口，通过域名发布服务，代替经常变化的ip ConfigMap：K
一键部署k8s，十分钟搞定
qq_44872331的博客
06-13 1023
k8s集群快速安装。一键解决你的烦恼
Kubernetes - 一键安装部署 K8S（附：Kubernetes Dashboard）
牧码的博客
10-23 1800
Kubernetes - 一键安装部署 K8S（附：Kubernetes Dashboard）
KubeSphere一键安装部署K8S集群（单master节点）-亲测过
qq_759035366的博客
10-22 1044
【代码】KubeSphere一键安装部署K8S集群（单master节点）-亲测过。
【Kubernetes部署篇】一键安部署K8s单机版脚本(需要联网)
热门推荐
秦子腾
04-22 2万+
2、查看Pod状态：如果不是Running状态，请耐心等待。4、验证是否可调度 及 CoreDNS解析。
k8s 1.29 一键安装脚本, 丝滑致极
aifeier的博客
01-31 1940
高可用 k8s 1.29 安装, 一键安装脚本, 以及基于 keepalived 与 nginx 实现高可用 apiserver 用于高可用 k8s 集群
kubesphere一键部署k8s
weixin_44770684的博客
11-06 2415
一键部署k8s kubekey kubesphere 使用 kubekey一键部署k8s 国内源一键部署k8s Linux centos yum源
Kubernetes（k8s）超详细的安装步骤
wuds_158的博客
07-06 1万+
验证：kubectl get node。
kubeadm一键部署K8S流程
IT技术
07-31 662
kubeadm一键部署K8S流程
K8s 离线一键安装
weixin_44214515的博客
04-09 913
基于kubespray安装k8s的文章网上非常多，但是按照网上的帖子进行安装时多数人都会遇到各种各样的问题。比如github被墙、gcr被墙、docker启动失败、ansible连接时提示验证失败等等不一一赘述。这里我提供了一套我自己的安装脚本，可一键完成全部安装，下面来介绍一下安装过程
K8S 云集群安装纯享版 - 傻瓜式一键教程 全自动脚本文件
Enchanter06的博客
06-21 788
众所周知，K8S最难的部分是什么？——是安装。。。 如果你发现网络插件的默认 Pod 网络与主机网络之间冲突， 则应该用另外一个 CIDR 来代替。在执行 kubeadm init 时使用 --pod-network-cidr
vs2022安装pcl1.13.0
09-20
可以按照以下步骤在VS2022中安装PCL1.13.0: 1. 首先，确保你已经成功安装了VS2022社区版。你可以从Microsoft官方网站上下载并安装。 2. 下载PCL1.13.0库文件。你可以在点云侠的博客或其他可靠的资源网站上找到并...

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值