Kubesphere中安装apisix的问题

已于 2024-08-12 14:55:02 修改
阅读量1.4k 收藏 26
点赞数 29
文章标签： kubernetes 容器 云原生
于 2024-08-12 14:41:39 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/abc2675811870/article/details/141130377
版权

Apache APISIX 介绍

Apache APISIX 是一款开源的高性能、动态云原生网关，由深圳支流科技有限公司于 2019 年捐赠给 Apache 基金会，当前已经成为 Apache 基金会的顶级开源项目，也是 GitHub 上最活跃的网关项目。Apache APISIX 当前已经覆盖了 API 网关，LB，Kubernetes Ingress，Service Mesh 等多种场景。

在kubesphere中安装自制应用遇到的bug

在项目空间下，点击应用，根据模版创建自制应用，点击安装的时候一直返回上一步

发现是前端抛的错。

解决方法

看官网论坛也有类似的，但是没人解答：https://ask.kubesphere.io/forum/d/9624

可能升级版本能解决这个问题，我目前的版本如下：

-----

Kubernetes版本信息
V1.24.9

容器运行时
containerd 1.6.20

KubeSphere版本信息
v3.3.2 kubekey全套安装

-----

不想升级重新搞一套，只能去k8s集群中敲helm命令安装apisix应用

#现在github下载安装包：
wget https://github.com/apache/apisix-helm-chart/releases/download/apisix-0.11.2/apisix-0.11.2.tgz

根据自己的需要调整配置，覆盖values.yaml的默认参数，我的配置如下，可根据自己需要修改：

vim apisix-config.yaml

#
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

global:
  # e.g.
  # imagePullSecrets:
  #   - my-registry-secrets
  #   - other-registry-secrets
  #
  imagePullSecrets: []

apisix:
  # Enable or disable Apache APISIX itself
  # Set it to false and ingress-controller.enabled=true will deploy only ingress-controller
  enabled: true

  # Enable nginx IPv6 resolver
  enableIPv6: true

  # Whether the APISIX version number should be shown in Server header
  enableServerTokens: true

  # Use Pod metadata.uid as the APISIX id.
  setIDFromPodUID: false

  customLuaSharedDicts: []
    # - name: foo
    #   size: 10k
    # - name: bar
    #   size: 1m
  luaModuleHook:
    enabled: false
    # extend lua_package_path to load third party code
    luaPath: ""
    # the hook module which will be used to inject third party code into APISIX
    # use the lua require style like: "module.say_hello"
    hookPoint: ""
    # configmap that stores the codes
    configMapRef:
      name: ""
      # mounts decides how to mount the codes to the container.
      mounts:
        - key: ""
          path: ""

  # Defines how apisix handles routing:
  # - radixtree_uri: match route by uri(base on radixtree)
  # - radixtree_host_uri: match route by host + uri(base on radixtree)
  # - radixtree_uri_with_parameter: match route by uri with parameters
  httpRouter: radixtree_uri

  enableCustomizedConfig: false
  customizedConfig: {}

  image:
    repository: apache/apisix
    pullPolicy: IfNotPresent
    # Overrides the image tag whose default is the chart appVersion.
    tag: 2.15.0-alpine

  # Use a `DaemonSet` or `Deployment`
  kind: Deployment
  # kind is DaemonSet, replicaCount not become effective
  replicaCount: 1

  priorityClassName: ""
  podAnnotations: {}
  podSecurityContext: {}
    # fsGroup: 2000
  securityContext: {}
    # capabilities:
    #   drop:
    #   - ALL
    # readOnlyRootFilesystem: true
    # runAsNonRoot: true
    # runAsUser: 1000

  # See https://kubernetes.io/docs/tasks/run-application/configure-pdb/ for more details
  podDisruptionBudget:
    enabled: false
    minAvailable: 90%
    maxUnavailable: 1

  resources: {}
    # We usually recommend not to specify default resources and to leave this as a conscious
    # choice for the user. This also increases chances charts run on environments with little
    # resources, such as Minikube. If you do want to specify resources, uncomment the following
    # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
    # limits:
    #   cpu: 100m
    #   memory: 128Mi
    # requests:
    #   cpu: 100m
    #   memory: 128Mi
  hostNetwork: false

  nodeSelector: {}
  tolerations: []
  affinity: {}

  # timezone is the timezone where apisix uses.
  # For example: "UTC" or "Asia/Shanghai"
  # This value will be set on apisix container's environment variable TZ.
  # You may need to set the timezone to be consistent with your local time zone,
  # otherwise the apisix's logs may used to retrieve event maybe in wrong timezone.
  timezone: "Asia/Shanghai"

  # extraEnvVars An array to add extra env vars
  # e.g:
  # extraEnvVars:
  #   - name: FOO
  #     value: "bar"
  #   - name: FOO2
  #     valueFrom:
  #       secretKeyRef:
  #         name: SECRET_NAME
  #         key: KEY
  extraEnvVars: []

nameOverride: ""
fullnameOverride: ""

serviceAccount:
  create: false
  annotations: {}
  name: ""

rbac:
  create: false

gateway:
  # type: NodePort
  # If you want to keep the client source IP, you can set this to Local.
  # ref: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
  externalTrafficPolicy: Cluster
  type: LoadBalancer
  annotations:
    lb.kubesphere.io/v1alpha1: openelb
    protocol.openelb.kubesphere.io/v1alpha1: layer2
    eip.openelb.kubesphere.io/v1alpha2: layer2-eip
  externalIPs: []
  http:
    enabled: true
    servicePort: 80
    containerPort: 9080
  tls:
    enabled: false
    servicePort: 443
    containerPort: 9443
    existingCASecret: ""
    certCAFilename: ""
    http2:
      enabled: true
    sslProtocols: "TLSv1.2 TLSv1.3"
  # L4 proxy (TCP/UDP)
  stream:
    enabled: false
    only: false
    tcp: []
    udp: []
  ingress:
    enabled: false
    annotations: {}
      # kubernetes.io/ingress.class: nginx
      # kubernetes.io/tls-acme: "true"
    hosts:
      - host: apisix.local
        paths: []
    tls: []
  #  - secretName: apisix-tls
  #    hosts:
  #      - chart-example.local

admin:
  # Enable Admin API
  enabled: true
  # admin service type
  type: ClusterIP
  # loadBalancerIP: a.b.c.d
  # loadBalancerSourceRanges:
  #   - "143.231.0.0/16"
  externalIPs: []
  #
  port: 9180
  servicePort: 9180
  # Admin API support CORS response headers
  cors: true
  # Admin API credentials
  credentials:
    admin: edd1c9f034335f136f87ad84b625c8f1
    viewer: 4054f7cf07e344346cd3f287985e76a2

  allow:
    # The client IP CIDR allowed to access Apache APISIX Admin API service.
    ipList:
      - 0.0.0.0/0

nginx:
  workerRlimitNofile: "20480"
  workerConnections: "10620"
  workerProcesses: auto
  enableCPUAffinity: true
  envs: []

# APISIX plugins to be enabled
plugins:
  - api-breaker
  - authz-keycloak
  - basic-auth
  - batch-requests
  - consumer-restriction
  - cors
  - echo
  - fault-injection
  - file-logger
  - grpc-transcode
  - hmac-auth
  - http-logger
  - ip-restriction
  - ua-restriction
  - jwt-auth
  - kafka-logger
  - key-auth
  - limit-conn
  - limit-count
  - limit-req
  - node-status
  - openid-connect
  - authz-casbin
  - prometheus
  - proxy-cache
  - proxy-mirror
  - proxy-rewrite
  - redirect
  - referer-restriction
  - request-id
  - request-validation
  - response-rewrite
  - serverless-post-function
  - serverless-pre-function
  - sls-logger
  - syslog
  - tcp-logger
  - udp-logger
  - uri-blocker
  - wolf-rbac
  - zipkin
  - traffic-split
  - gzip
  - real-ip
  - ext-plugin-pre-req
  - ext-plugin-post-req
  - server-info
stream_plugins:
  - mqtt-proxy
  - ip-restriction
  - limit-conn

pluginAttrs: {}

extPlugin:
  enabled: false
  cmd: ["/path/to/apisix-plugin-runner/runner", "run"]

wasmPlugins:
  enabled: false
  plugins: []

# customPlugins allows you to mount your own HTTP plugins.
customPlugins:
  enabled: false
  # the lua_path that tells APISIX where it can find plugins,
  # note the last ';' is required.
  luaPath: "/opts/custom_plugins/?.lua"
  plugins:
    # plugin name.
    - name: "prometheus"
      # plugin attrs
      attrs:
        export_addr:
        ip: 0.0.0.0
        port: 9091
      # plugin codes can be saved inside configmap object.
      configMap:
        # name of configmap.
        name: "prometheus"
        # since keys in configmap is flat, mountPath allows to define the mount
        # path, so that plugin codes can be mounted hierarchically.
        mounts:
          - key: ""
            path: ""
          - key: ""
            path: ""

updateStrategy: {}
  # type: RollingUpdate

extraVolumes: []
# - name: extras
#   emptyDir: {}

extraVolumeMounts: []
# - name: extras
#   mountPath: /usr/share/extras
#   readOnly: true

extraInitContainers: []
# - name: init-myservice
#   image: busybox:1.28
#   command: ['sh', '-c', "until nslookup myservice.$(cat /var/run/secrets/kubernetes.io/serviceaccount/namespace).svc.cluster.local; do echo waiting for myservice; sleep 2; done"]

discovery:
  enabled: false
  registry: {}
    # Integration service discovery registry. E.g eureka\dns\nacos\consul_kv
    # reference:
    # https://apisix.apache.org/docs/apisix/discovery/#configuration-for-eureka
    # https://apisix.apache.org/docs/apisix/discovery/dns/#service-discovery-via-dns
    # https://apisix.apache.org/docs/apisix/discovery/consul_kv/#configuration-for-consul-kv
    # https://apisix.apache.org/docs/apisix/discovery/nacos/#configuration-for-nacos
    # https://apisix.apache.org/docs/apisix/discovery/kubernetes/#configuration
    #
    # an eureka example:
    # ```
    # eureka:
    #   host:
    #     - "http://${username}:${password}@${eureka_host1}:${eureka_port1}"
    #     - "http://${username}:${password}@${eureka_host2}:${eureka_port2}"
    #   prefix: "/eureka/"
    #   fetch_interval: 30
    #   weight: 100
    #   timeout:
    #     connect: 2000
    #     send: 2000
    #     read: 5000
    # ```
    #
    # the minimal Kubernetes example:
    # ```
    # kubernetes: {}
    # ```
    #
    # The prerequisites for the above minimal Kubernetes example:
    #  1. [Optional] Set `.serviceAccount.create` to `true` to create a dedicated ServiceAccount.
    #     It is recommended to do so, otherwise the default ServiceAccount "default" will be used.
    #  2. [Required] Set `.rbac.create` to `true` to create and bind the necessary RBAC resources.
    #     This grants the ServiceAccount in use to List-Watch Kubernetes Endpoints resources.
    #  3. [Required] Include the following environment variables in `.nginx.envs` to pass them into
    #     nginx worker processes (https://nginx.org/en/docs/ngx_core_module.html#env):
    #      - KUBERNETES_SERVICE_HOST
    #      - KUBERNETES_SERVICE_PORT
    #     This is for allowing the default `host` and `port` of `.discovery.registry.kubernetes.service`.

# access log and error log configuration
logs:
  enableAccessLog: true
  accessLog: "/dev/stdout"
  accessLogFormat: '$remote_addr - $remote_user [$time_local] $http_host \"$request\" $status $body_bytes_sent $request_time \"$http_referer\" \"$http_user_agent\" $upstream_addr $upstream_status $upstream_response_time \"$upstream_scheme://$upstream_host$upstream_uri\"'
  accessLogFormatEscape: default
  errorLog: "/dev/stderr"
  errorLogLevel: "warn"

dns:
  resolvers:
    - 127.0.0.1
    - 172.20.0.10
    - 114.114.114.114
    - 223.5.5.5
    - 1.1.1.1
    - 8.8.8.8
  validity: 30
  timeout: 5

initContainer:
  image: busybox
  tag: 1.28

autoscaling:
  enabled: false
  minReplicas: 1
  maxReplicas: 100
  targetCPUUtilizationPercentage: 80
  targetMemoryUtilizationPercentage: 80

# Custom configuration snippet.
configurationSnippet:
  main: |

  httpStart: |

  httpEnd: |

  httpSrv: |

  httpAdmin: |

  stream: |

# Observability configuration.
# ref: https://apisix.apache.org/docs/apisix/plugins/prometheus/
serviceMonitor:
  enabled: true
  # namespace where the serviceMonitor is deployed, by default, it is the same as the namespace of the apisix
  namespace: "apisix-system"
  # name of the serviceMonitor, by default, it is the same as the apisix fullname
  name: ""
  # interval at which metrics should be scraped
  interval: 15s
  # path of the metrics endpoint
  path: /apisix/prometheus/metrics
  # prefix of the metrics
  metricPrefix: apisix_
  # container port where the metrics are exposed
  containerPort: 9091
  # @param serviceMonitor.labels ServiceMonitor extra labels
  labels: {}
  # @param serviceMonitor.annotations ServiceMonitor annotations
  annotations: {}

# etcd configuration
# use the FQDN address or the IP of the etcd
etcd:
  # install etcd(v3) by default, set false if do not want to install etcd(v3) together
  enabled: true
  host:
    # host or ip e.g. http://172.20.128.89:2379
    - http://etcd.host:2379
  prefix: "/apisix"
  timeout: 30

  # if etcd.enabled is true, set more values of bitnami/etcd helm chart
  auth:
    rbac:
      # No authentication by default
      create: false
      user: ""
      password: ""
    tls:
      enabled: false
      existingSecret: ""
      certFilename: ""
      certKeyFilename: ""
      verify: true
      sni: ""

  service:
    port: 2379

  replicaCount: 1

dashboard:
  enabled: true
  service:
    type: NodePort

ingress-controller: 
  enabled: true
  config:
    apisix:
      serviceNamespace: apisix-system
  ServiceMonitor:
    enabled: true
    namespace: 'apisix-system'
    interval: 15s

vault:
  enabled: false
  host: ""
  timeout: 10
  token: ""
  prefix: ""

安装apisix

安装的命名空间在apisix-system下，配置文件为apisix-config.yaml，chart包为：apisix-0.11.2.tgz

helm install ingress-apisix ./apisix-0.11.2.tgz -f ./apisix-config.yaml --namespace apisix-system  --debug

查看apisix资源

# kubectl get all -n apisix-system

#kubectl get pod -n apisix-system， 如果有pending的状态
#kubectl get pvc -n apisix-system， 如果有pending的状态

如果有pod处于init状态和pvc一直处于pending状态，需要删除pvc，重新编辑pvc指定为动态存储即可 【添加storageClassName: 你的stroageClass】，或者创建静态pv资源

（由于我这里已改好，所以状态是准备就绪）

删除完之后，将下面的名字替换成你的pvc名称即可

#vim apisix-pvc.yaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: data-ingress-apisix-etcd-2
  namespace: apisix-system
  labels:
    app.kubernetes.io/component: etcd
    app.kubernetes.io/instance: ingress-apisix
    app.kubernetes.io/name: etcd
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 8Gi
  storageClassName: managed-nfs-storage
  volumeMode: Filesystem
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: data-ingress-apisix-etcd-1
  namespace: apisix-system
  labels:
    app.kubernetes.io/component: etcd
    app.kubernetes.io/instance: ingress-apisix
    app.kubernetes.io/name: etcd
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 8Gi
  storageClassName: managed-nfs-storage
  volumeMode: Filesystem   
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: data-ingress-apisix-etcd-0
  namespace: apisix-system
  labels:
    app.kubernetes.io/component: etcd
    app.kubernetes.io/instance: ingress-apisix
    app.kubernetes.io/name: etcd
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 8Gi
  storageClassName: managed-nfs-storage
  volumeMode: Filesystem

#kubectl apply -f apisix-pvc.yaml

执行完pvc的状态处于pending就是正常，后面的pod都会正常启动解决。

Java码农cqz
关注
9.云原生- Kubesphere3.3.0 安装 APISIX 网关的使用和配置
平塘大鱼儿
11-10 2749
Apache APISIX 是一个动态、实时、高性能的云原生 API 网关，提供了负载均衡、动态上游、灰度发布、服务熔断、身份认证、可观测性等丰富的流量管理功能。
2.云原生-安装OpenELB负载均衡器，启用KubeSphere3.3.0的集群网关
平塘大鱼儿
08-11 1626
KubeSphere3.3.0版本加入了OpenELB为私有环境对外暴露 LoadBalancer 服务。值得注意的是KubeSphere3.3.0以下的版本中并没有集成OpenELB作为网关的负载均衡器提供商，因此3.3.0以下的版本需要额外安装第三方网关例如 ：APISIX 等作为集群的网关。...
Apache APISIX 为 KubeSphere 提供更好用的网关及 K8S Ingress Controller
ApacheAPISIX的博客
09-02 896
KubeSphere 介绍KubeSphere 是在 Kubernetes 中构建的深度云原生应用的系统，完全开源，支持多云与多集群管理自动化，提供全栈的 IT 运维能力，简化企业的 DevOps 工作流。它的架构可以非常方便地使应用应用与云原生生态组件进行即插即用（即插即用）的集成。是全栈的多管道容器平台，KubeSphere 提供了运维友好的形状操作界面，帮助企业构建了一个强大的专门功能的容器。KubeSphere 为用户提供构建企业级Kubernetes 环境需求的报告功能，多云与多集群管理、Kube
KubeSphere中集成ApiSix
qq_37892401的博客
02-13 1147
KubeSphere中集成ApiSix
【kubernetes】k8s部署APISIX及在KubeSphere使用APISIX
记录开发学习笔记
09-01 2780
KubeSphere部署APISIX及使用APISIX暴露外网访问
6.19 成都站云原生 Meetup，KubeSphere 和 APISIX 等你来！
KubeSphere
06-11 259
以容器技术和容器编排为基础的云原生应用，被越来越多的企业用户接受和使用，并且在生产环境中使用容器技术的比例逐年增加。KubeSphere 作为一款面向应用的开源容器混合云，经过 3 年的发展和 10 个版本的迭代，收获了一百多位开源贡献者，超过十万次下载，并有数千名社区用户用 KubeSphere 作为企业容器云平台。 KubeSphere 之所以能够如此快速发展，得益于开源社区带来的天然优势，以及社区里长期活跃的用户、贡献者积极参与社区，帮助推动产品和社区快速成长，我们坚持认为 KubeSphere 开源
【业务功能119】微服务-springcloud-springboot-Kubernetes集群-k8s集群- KubeSphere中集成ApiSix-Prometheus
studyday1的博客
09-21 536
Apache APISIX 网关可用之后其实是缺少像原生集群或项目网关这样自带的状态监控能力的，但这个我们也可以通过 Apache APISIX 的 Prometheus 插件以及 KubeSphere 自带的自定义监控能力来弥补。下面我们在项目左侧菜单列表中找到「监控告警」中的「自定义监控」，开始「创建」自定义监控面板。在弹出窗口中填入「名称」，选择「自定义」监控模版，并进入「下一步」的监控面板创建。进入编辑页面后现在左侧点击。
K8S中部署apisix(非ingress)
xuhss_com的博客
02-10 3532
Python微信订餐小程序课程视频 https://edu.csdn.net/course/detail/36074 Python实战量化交易理财系统 https://edu.csdn.net/course/detail/35475 不使用pvc的方式在K8S中部署apisix-gateway 简介 因为公司项目准备重构，现在做技术储备，之前公司项目使用的ocelot做网关，ocelot是.net平台下的一个网关，也是很不错，但是在选型的时候需要考虑到性能问题，所以在这次重构中抛弃了ocelot，看了ap
想在 KubeSphere 中进行自定义监控？来瞧瞧这
ApacheAPISIX的博客
12-07 1891
本文详细介绍如何「将 Apache APISIX Ingress 网关接入 KubeSphere 并进行自定义监控」。
apisix-ingress-controller:K8的入口控制器
04-01
适用于Kubernetes的Apache APISIX 使用进行Kubernetes 。 apisix-ingress-controller中的所有配置都是使用Kubernetes CRD（自定义资源定义）定义的。 例如Apache APISIX中的configure ，针对上游的支持服务注册发现机制，负载平衡等。 apisix-ingress-controller是Apache APISIX控制平面组件。 目前，它适用于Kubernetes集群。 将来，我们计划将子模块分开以适应更多的部署模式，例如虚拟机集群。 apisix-ingress-controller的技术架构： 地位 该项目目前被认为是实验性的。 特征 使用具有最小学习曲线的k8s yaml结构，对具有自定义资源定义（CRD）的Apache APISIX进行声明式配置。 适用于Yaml期间的热重装。 本机Ku
云原生或K8S 安装 APISIX
guyougao的博客
04-19 1430
apisix
Kubernetes1.21部署apisix网关
青春不流名
06-26 1065
1、安装nfs-subdir-external-provisioner。
k8s ApiSix
qq_27164239的博客
01-11 517
k8s apisix
K8s 安装使用 apisix
偶是一只小小鸟~
08-23 7656
apisix Apache APISIX是一个动态的、实时的、高性能的 API 网关. 本文主要测试在k8s环境下使用apisix-ingress-controlle 使用Helm Chart安装 所有的pod,svc等都放到了default的namespace下 apisix $ helm repo add apisix https://charts.apiseven.com $ helm repo update $ helm install apisix apisix/apisix apisix-da
APISIX教程(一)：怎么在kubernetes中安装apisix-ingress-controller
专注于输出具有实用价值的软件运维经验及教程
06-16 396
一、apisix简介一款云原生声明式网关！以下简介摘自官方：Apache APISIX 是 Apache 软件基金会下的顶级项目，由 API7.ai 开发并捐赠。它是一个具有动态、实时、高性能等特点的云原生 API 网关。你可以使用 APISIX 网关作为所有业务的流量入口，它提供了动态路由、动态上游、动态证书、A/B 测试、灰度发布（金丝雀发布）、蓝绿部署、限速、防攻击、收集指标、监控报警、可观...
k8s中使用yaml文件方式部署apisix
最新发布
weixin_58146638的博客
07-30 596
本次安装etcd集群的命名空间为gv-public，副本数为3，使用的StorageClass存储为NFS类型，可根据自己的后端存储进行修改。创建路由测试：可以通过dashboard控制台创建一个测试路由然后使用刚才Nodeport类型的Service端口31684进行访问。可以通过k8s集群的任意一个节点IP加上32562端口进行访问。apisix-dashboard.yaml文件。yaml文件apisix.yaml。yaml文件etcd.yaml。创建apisix并查看运行状态。
k8s中apisix-3.8.0与etcd连接基于mtls认证
那达慕的博客
04-17 799
【代码】k8s中apisix-3.8.0与etcd连接基于mtls认证。
如何在kubesphere 中安装
05-19
KubeSphere 是一个开源的 Kubernetes 工具平台，可以帮助用户更加便捷地使用 Kubernetes。在 KubeSphere 中安装可以通过以下步骤完成： 1. 准备 Kubernetes 集群：KubeSphere 可以安装在任何符合 Kubernetes 集群规范的 Kubernetes 集群上。 2. 下载 KubeSphere 安装包：可以从 KubeSphere 的官方网站 https://kubesphere.io/downloads/ 下载最新版本的 KubeSphere 安装包。 3. 安装 KubeSphere：可以通过执行安装脚本进行安装，也可以使用 Helm Chart 进行安装。 4. 访问 KubeSphere：安装完成后，可以通过浏览器访问 KubeSphere 控制台，进行集群管理和应用部署等操作。 需要注意的是，在安装 KubeSphere 之前，需要确保 Kubernetes 集群已经正确地安装和配置。同时，还需要根据实际需求选择合适的 KubeSphere 版本和安装方式。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值