搭建Longhorn

Longhorn

Longhorn 是一个针对基于微服务的分布式块存储的开放源码项目。

yum install -y git
git clone https://github.com/longhorn/longhorn && cd longorn
helm upgrade --install longhorn ./chart --namespace longhorn-system -f values.yaml

编写values.yaml

image:
  longhorn:
    engine: harbor.xxx/common/longhorn-engine
    engineTag: v0.8.1-rc2
    manager: harbor.saas.xxx/common/longhorn-manager
    managerTag: v0.8.1-rc2
    ui: harbor.saas.xxx/common/longhorn-ui
    uiTag: v0.8.1-rc2
    instanceManager: nexus-docker.xxx/longhornio/longhorn-instance-manager
    instanceManagerTag: v1_20200301
  pullPolicy: IfNotPresent

service:
  ui:
    type: ClusterIP
    nodePort: null
  manager:
    type: ClusterIP
    nodePort: ""

persistence:
  defaultClass: false
  defaultClassReplicaCount: 3

csi:
  attacherImage:
  provisionerImage:
  driverRegistrarImage:
  kubeletRootDir:
  attacherReplicaCount:
  provisionerReplicaCount:

defaultSettings:
  backupTarget:
  backupTargetCredentialSecret:
  createDefaultDiskLabeledNodes:
  defaultDataPath:
  replicaSoftAntiAffinity:
  storageOverProvisioningPercentage:
  storageMinimalAvailablePercentage:
  upgradeChecker:
  defaultReplicaCount:
  guaranteedEngineCPU:
  defaultLonghornStaticStorageClass:
  backupstorePollInterval:
  taintToleration:

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
  #

ingress:
  ## Set to true to enable ingress record generation
  enabled: true
  host: longhorn.saas.xxx-ift.com

  ## Set this to true in order to enable TLS on the ingress record
  ## A side effect of this will be that the backend service will be connected at port 443
  tls: false

  ## If TLS is set to true, you must declare what secret will store the key/certificate for TLS
  tlsSecret: longhorn.local-tls

  ## Ingress annotations done as key:value pairs
  ## If you're using kube-lego, you will want to add:
  ## kubernetes.io/tls-acme: true
  ##
  ## For a full list of possible ingress annotations, please see
  ## ref: https://github.com/kubernetes/ingress-nginx/blob/master/docs/annotations.md
  ##
  ## If tls is set to true, annotation ingress.kubernetes.io/secure-backends: "true" will automatically be set
  annotations:
  #  kubernetes.io/ingress.class: nginx
  #  kubernetes.io/tls-acme: true

  secrets:
  ## If you're providing your own certificates, please use this to add the certificates as secrets
  ## key and certificate should start with -----BEGIN CERTIFICATE----- or
  ## -----BEGIN RSA PRIVATE KEY-----
  ##
  ## name should line up with a tlsSecret set further up
  ## If you're using kube-lego, this is unneeded, as it will create the secret for you if it is not set
  ##
  ## It is also possible to create and manage the certificates outside of this helm chart
  ## Please see README.md for more information
  # - name: longhorn.local-tls
  #   key:
  #   certificate: