apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: dashboard
  namespace: kube-system
  annotations:
    # use the shared ingress-nginx
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
    cert-manager.io/cluster-issuer: letsencrypt
spec:
  ingressClassName: public
  # https://kubernetes.io/docs/concepts/services-networking/ingress/
  # https://kubernetes.github.io/ingress-nginx/user-guide/tls/
  tls:
  - hosts:
    - k8s.yuhan.tech
    secretName: all-yuhan-tech-tls
  rules:
  - host: k8s.yuhan.tech
    http:
      paths:
      - path: "/"
        pathType: Prefix
        backend:
          service:
            name: kubernetes-dashboard
            port:
              number: 443

microk8s enable cert-manager

apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: letsencrypt
spec:
  acme:
    privateKeySecretRef:
      name: letsencrypt-account-key
    server: https://acme-v02.api.letsencrypt.org/directory
    solvers:
    - dns01:
        cloudflare:
          email: my-cloudflare-acc@example.com # 替换成你的 cloudflare 邮箱账号，API Token 方式认证非必需，API Keys 认证是必需
          apiTokenSecretRef:
            key: api-token
            name: cloudflare-api-token-secret # 引用保存 cloudflare 认证信息的 Secret

apiVersion: v1
kind: Secret
metadata:
  name: cloudflare-api-token-secret
  namespace: cert-manager  # 需要在这个命名空间
type: Opaque
stringData:
  api-token: <API Token> # 粘贴 Token 到这里，不需要 base64 加密。

apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: test-mydomain-com
  namespace: default
spec:
  dnsNames:
  - test.mydomain.com # 要签发证书的域名
  issuerRef:
    kind: ClusterIssuer
    name: letsencrypt # 引用 ClusterIssuer，指示采用 dns01 方式进行校验
  secretName: test-mydomain-com-tls # 最终签发出来的证书会保存在这个 Secret 里面

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    # add an annotation indicating the issuer to use.
    cert-manager.io/cluster-issuer: nameOfClusterIssuer
  name: myIngress
  namespace: myIngress
spec:
  rules:
  - host: example.com
    http:
      paths:
      - pathType: Prefix
        path: /
        backend:
          service:
            name: myservice
            port:
              number: 80
  tls: # < placing a host in the TLS config will determine what ends up in the cert's subjectAltNames
  - hosts:
    - example.com
    secretName: myingress-cert # < cert-manager will store the created certificate in this secret.

apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: all-yuhan-tech-tls
spec:
  dnsNames:
  - yuhan.tech
  - "*.yuhan.tech"
  issuerRef:
    name: letsencrypt
    kind: ClusterIssuer
  secretName: all-yuhan-tech-tls

apiVersion: v1
kind: Pod
metadata:
  name: test-pd
spec:
  containers:
  - image: registry.k8s.io/test-webserver
    name: test-container
    volumeMounts:
    - mountPath: /my-nfs-data
      name: test-volume
  volumes:
  - name: test-volume
    nfs:
      server: my-nfs-server.example.com
      path: /my-nfs-volume
      readOnly: true

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: haha-nfs
provisioner: example.com/external-nfs
parameters:
  server: nfs.yuhan.tech
  path: /data
  readOnly: "false"

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: haha-nfs-claim
spec:
  accessModes:
    - ReadWriteOnce
  volumeMode: Filesystem
  resources:
    requests:
      storage: 200Gi
  storageClassName: haha-nfs

apiVersion: v1
kind: Pod
metadata:
  name: mypod
spec:
  containers:
    - name: myfrontend
      image: nginx
      volumeMounts:
      - mountPath: "/var/www/html"
        name: mypd
  volumes:
    - name: mypd
      persistentVolumeClaim:
        claimName: haha-nfs-claim

helm upgrade nfs-subdir-external-provisioner nfs-subdir-external-provisioner/nfs-subdir-external-provisioner -f nfs-subdir-external-provisioner-0.yml

helm upgrade nfs-subdir-external-provisioner-1 nfs-subdir-external-provisioner/nfs-subdir-external-provisioner -f nfs-subdir-external-provisioner-1.yml

helm repo add bitnami https://charts.bitnami.com/bitnami

# 创建密码，按指定的规则随机生成密码
kubectl create secret generic postgresql-secret \
  --from-literal=postgres-password=$(openssl rand -base64 18)

# 安装，nfs 这就用上了
~~helm upgrade --install \
  --set auth.existingSecret=postgresql-secret \
  --set primary.persistence.enabled=true \
  --set primary.persistence.size=50Gi \
  --set primary.persistence.storageClass=nfs-client \
  postgresql bitnami/postgresql~~

helm show values bitnami/postgresql > postgresql.yml

helm install my-postgresql bitnami/postgresql -f postgresql.yml

apiVersion: v1 
kind: PersistentVolumeClaim 
metadata: 
  name: postgresql-pvc 
spec: 
  accessModes: 
  - ReadWriteOnce 
  storageClassName: nfs-client 
  resources:  
    requests: 
      storage: 50Gi

PostgreSQL can be accessed via port 5432 on the following DNS names from within your cluster:

    my-postgresql.default.svc.cluster.local - Read/Write connection

To get the password for "postgres" run:

    export POSTGRES_PASSWORD=$(kubectl get secret --namespace default my-postgresql -o jsonpath="{.data.postgres-password}" | base64 -d)

To connect to your database run the following command:

    kubectl run my-postgresql-client --rm --tty -i --restart='Never' --namespace default --image docker.io/bitnami/postgresql:15.3.0-debian-11-r24 --env="PGPASSWORD=$POSTGRES_PASSWORD" \
      --command -- psql --host my-postgresql -U postgres -d postgres -p 5432

    > NOTE: If you access the container using bash, make sure that you execute "/opt/bitnami/scripts/postgresql/entrypoint.sh /bin/bash" in order to avoid the error "psql: local user with ID 1001} does not exist"

To connect to your database from outside the cluster execute the following commands:

    export NODE_IP=$(kubectl get nodes --namespace default -o jsonpath="{.items[0].status.addresses[0].address}")
    export NODE_PORT=$(kubectl get --namespace default -o jsonpath="{.spec.ports[0].nodePort}" services my-postgresql)
    PGPASSWORD="$POSTGRES_PASSWORD" psql --host $NODE_IP --port $NODE_PORT -U postgres -d postgres

# 创建密码，按指定的规则随机生成密码
kubectl create secret generic postgresql-gitlab-secret \
  --from-literal=postgres-password=$(openssl rand -base64 18)

# 查看密码
kubectl get secret postgresql-gitlab-secret -o jsonpath="{.data.postgres-password}" | base64 -d

CREATE ROLE "gitlab" CREATEDB CREATEROLE LOGIN REPLICATION BYPASSRLS PASSWORD 'tO+Qo4jvFoyDGpgef44j69+r';

CREATE DATABASE "gitlabhq_production"
WITH
  OWNER = "gitlab"
;

helm uninstall my-postgresql

helm install my-postgresql bitnami/postgresql -f postgresql.yml

apiVersion: v1 
kind: PersistentVolumeClaim 
metadata: 
  name: redis-pvc 
spec: 
  accessModes: 
  - ReadWriteOnce 
  storageClassName: nfs-client 
  resources:  
    requests: 
      storage: 20Gi

---
apiVersion: v1 
kind: PersistentVolumeClaim 
metadata: 
  name: redis-pvc-replica
spec: 
  accessModes: 
  - ReadWriteOnce 
  storageClassName: nfs-client 
  resources:  
    requests: 
      storage: 40Gi

helm repo add bitnami https://charts.bitnami.com/bitnami

~~helm install my-redis bitnami/redis --version 17.8.0  --set persistence.storageClass=nfs-client~~

helm delete my-redis

~~~~helm show values bitnami/redis > redis.yml

helm install my-redis bitnami/redis -f redis.yml

my-redis-master.default.svc.cluster.local for read/write operations (port 6379)
my-redis-replicas.default.svc.cluster.local for read-only operations (port 6379)

export REDIS_PASSWORD=$(kubectl get secret --namespace default my-redis -o jsonpath="{.data.redis-password}" | base64 -d)

kubectl run --namespace default redis-client --restart='Never'  --env REDIS_PASSWORD=$REDIS_PASSWORD  --image docker.io/bitnami/redis:7.0.8-debian-11-r13 --command -- sleep infinity

kubectl exec --tty -i redis-client \
   --namespace default -- bash

REDISCLI_AUTH="$REDIS_PASSWORD" redis-cli -h my-redis-master
REDISCLI_AUTH="$REDIS_PASSWORD" redis-cli -h my-redis-replicas

kubectl port-forward --namespace default svc/my-redis-master 6379:6379 &
    REDISCLI_AUTH="$REDIS_PASSWORD" redis-cli -h 127.0.0.1 -p 6379

> ACL GENPASS 64
5fd1203ac95a0424

> ACL SETUSER redis on >5fd1203ac95a0424 ~* +@all
OK

helm3 repo add bitnami https://charts.bitnami.com/bitnami

helm install my-gitea bitnami/gitea --version 0.3.6

helm show values bitnami/gitea > gitea.yml

helm install my-gitea bitnami/gitea -f gitea.yml

1. Get the Gitea URL:

  Or running:

  export NODE_PORT=$(kubectl get --namespace default -o jsonpath="{.spec.ports[0].nodePort}" services my-gitea)
  export NODE_IP=$(kubectl get nodes --namespace default -o jsonpath="{.items[0].status.addresses[0].address}")
  echo "Gitea URL: http://$NODE_IP:$NODE_PORT/"

2. Get your Gitea login credentials by running:

  echo Username: admin
  echo Password: $(kubectl get secret --namespace default my-gitea -o jsonpath="{.data.admin-password}" | base64 -d)

apiVersion: v1 
kind: PersistentVolumeClaim
metadata: 
  name: gitea-pvc
spec: 
  accessModes: 
  - ReadWriteMany
  storageClassName: nfs-client 
  resources:  
    requests: 
      storage: 10Gi

------
persistence:
  ## @param persistence.enabled Enable persistence using PVC
  ##
  enabled: true
  ## @param persistence.storageClass PVC Storage Class for Gitea volume
  ## If defined, storageClassName: <storageClass>
  ## If set to "-", storageClassName: "", which disables dynamic provisioning
  ## If undefined (the default) or set to null, no storageClassName spec is
  ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
  ##   GKE, AWS & OpenStack)
  ##
  storageClass: ""
  ## @param persistence.accessModes PVC Access Mode for Gitea volume
  ## Requires persistence.enabled: true
  ## If defined, PVC must be created manually before volume will be bound
  ##
  accessModes:
    - ReadWriteMany
  ## @param persistence.size PVC Storage Request for Gitea volume
  ##
  size: 10Gi
  ## @param persistence.dataSource Custom PVC data source
  ##
  dataSource: {}
  ## @param persistence.existingClaim A manually managed Persistent Volume Claim
  ## Requires persistence.enabled: true
  ## If defined, PVC must be created manually before volume will be bound
  ##
  existingClaim: "gitea-pvc"
  ## @param persistence.hostPath If defined, the gitea-data volume will mount to the specified hostPath.
  ## Requires persistence.enabled: true
  ## Requires persistence.existingClaim: nil|false
  ## Default: nil.
  ##
service:
  ## @param service.type Kubernetes Service type
  ##
  type: NodePort
	nodePorts:
	    http: 30005
	    ssh: 30006
	  ## @param service.externalTrafficPolicy Enable client source IP preservation
	  ## ref https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
	  ##
	  externalTrafficPolicy: Local

helm show values bitnami/minio  > minio-helm-values.yml

helm install my-minio bitnami/minio -f minio-helm-values.yml 

apiVersion: v1 
kind: PersistentVolumeClaim 
metadata: 
  name: minio-pvc 
spec: 
  accessModes: 
  - ReadWriteOnce 
  storageClassName: nfs-client 
  resources:  
    requests: 
      storage: 60Gi

** Please be patient while the chart is being deployed **

MinIO® can be accessed via port  on the following DNS name from within your cluster:

   my-minio.default.svc.cluster.local

To get your credentials run:

   export ROOT_USER=$(kubectl get secret --namespace default my-minio -o jsonpath="{.data.root-user}" | base64 -d)
   export ROOT_PASSWORD=$(kubectl get secret --namespace default my-minio -o jsonpath="{.data.root-password}" | base64 -d)

To connect to your MinIO® server using a client:

- Run a MinIO® Client pod and append the desired command (e.g. 'admin info'):

   kubectl run --namespace default my-minio-client \
     --rm --tty -i --restart='Never' \
     --env MINIO_SERVER_ROOT_USER=$ROOT_USER \
     --env MINIO_SERVER_ROOT_PASSWORD=$ROOT_PASSWORD \
     --env MINIO_SERVER_HOST=my-minio \
     --image docker.io/bitnami/minio-client:2023.2.16-debian-11-r1 -- admin info minio

To access the MinIO® web UI:

- Get the MinIO® URL:

   echo "MinIO® web URL: http://127.0.0.1:9001/minio"
   kubectl port-forward --namespace default svc/my-minio 9001:9001

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: default-ingress
  namespace: default
  annotations:
    # use the shared ingress-nginx
    # kubernetes.io/ingress.class: public
    # nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
    cert-manager.io/cluster-issuer: letsencrypt
spec:
  ingressClassName: public  # 最新用法，不是在注解里面了
  # https://kubernetes.io/docs/concepts/services-networking/ingress/
  # https://kubernetes.github.io/ingress-nginx/user-guide/tls/
  tls:
  - hosts:
    - objectstorage.yuhan.tech
    - objectstorage-web.yuhan.tech
    secretName: objectstorage-yuhan-tech-tls
  rules:
  - host: objectstorage.yuhan.tech
    http:
      paths:
      - path: "/"
        pathType: Prefix
        backend:
          service:
            name: my-minio
            port:
              number: 9000  # 这是 API 不是网页，网页是 9001 需要另外配置
  - host: objectstorage-web.yuhan.tech
    http:
      paths:
      - path: "/"
        pathType: Prefix
        backend:
          service:
            name: my-minio
            port:
              number: 9001

extraEnvVars:  # 必填，否则地址就是 localhost 了 https://github.com/minio/console/issues/1632
  - name: MINIO_SERVER_URL
    value: https://objectstorage.yuhan.tech
  - name: MINIO_BROWSER_REDIRECT_URL
    value: https://objectstorage.yuhan.tech

ingress.kubernetes.io/proxy-body-size: 10000m  # 老 k8s 版本用
nginx.ingress.kubernetes.io/proxy-body-size: 10000m  # 最新版本使用

provider: AWS
# Specify the region
region: cn
# Specify access/secret keys
aws_access_key_id: H3vCj0L3LIBHWvbh
aws_secret_access_key: LevG9vCPLvNguatIMJfQdGZhKRUgNl0h
# The below settings are for S3 compatible endpoints
#   See https://docs.gitlab.com/ee/administration/job_artifacts.html#s3-compatible-connection-settings
aws_signature_version: 4
host: objectstorage.yuhan.tech
endpoint: "https://objectstorage.yuhan.tech"
path_style: true

## https://docs.gitlab.com/charts/charts/globals#lfs-artifacts-uploads-packages-external-mr-diffs-and-dependency-proxy
object_store:
  enabled: true
  proxy_download: true
  storage_options: {}
    # server_side_encryption:
    # server_side_encryption_kms_key_id
  connection:
    secret: **minio-storage-secret**
    key: **connection

# 记得创建对应的桶 git-lfs gitlab-artifacts gitlab-uploads gitlab-packages gitlab-backups

# When consolidated object storage is enabled, for each item `bucket` must be specified and the `connection` must be empty. Check the following object storage configuration(s): artifacts,lfs,uploads,packages**

helm repo add argo https://argoproj.github.io/argo-helm

helm install my-argo-cd argo/argo-cd --version 5.23.1

# 可选自行设置，包括 ingress 的配置等
helm show values argo/argo-cd > argo.yml
helm install my-argo-cd argo/argo-cd -f argo.yml

# 代理设置
url=socks5://127.0.0.1:7890
# 如果代理失效的话直接运行 poff 即可断开 proxy
alias poff='unset http_proxy;unset https_proxy'
# 快捷方式打开
alias pon='export http_proxy=$url; export https_proxy=$url'

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: default-tls-ingress
  namespace: default
  annotations:
    # use the shared ingress-nginx
    kubernetes.io/ingress.class: public
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
    # cert-manager.io/cluster-issuer: letsencrypt
spec:
  # https://kubernetes.io/docs/concepts/services-networking/ingress/
  # https://kubernetes.github.io/ingress-nginx/user-guide/tls/
  tls:
  - hosts:
    - argo.yuhan.tech
    secretName: all-yuhan-tech-tls
  rules:
  - host: argo.yuhan.tech
    http:
      paths:
      - path: "/"
        pathType: Prefix
        backend:
          service:
            name: my-argo-cd-argocd-server
            port:
              number: 443

helm repo add argo https://argoproj.github.io/argo-helm

~~helm install my-argo-workflows argo/argo-workflows --version 0.22.12~~

helm show values argo/argo-workflows > argo-workflows.yml

helm install my-argo-workflows argo/argo-workflows -f argo-workflows.yml

helm repo add gitlab http://charts.gitlab.io/  # 还是得 pon 开代理哦

~~helm install my-gitlab gitlab/gitlab --version 6.9.1  # 但是失败了，得看文档了

helm repo update
helm upgrade --install gitlab gitlab/gitlab \
  --timeout 600s \
  --set global.hosts.domain=gitlab.yuhan.tech \
  --set global.hosts.externalIP=10.130.158.191 \
  --set certmanager-issuer.email=1106741606@qq.com \
  --set postgresql.image.tag=15.2.0~~

# 导出默认配置到文件
helm show values gitlab/gitlab > gitlab.yml

# 修改这个配置
# 过程中注意设置数据库用户、对象存储等等
# 再安装

helm install my-gitlab gitlab/gitlab --version 6.9.1 -f gitlab.yml

apiVersion: v1 
kind: PersistentVolumeClaim 
metadata: 
  name: my-gitlab-prometheus-server
spec: 
  accessModes: 
  - ReadWriteOnce 
  storageClassName: nfs-client 
  resources:  
    requests: 
      storage: 50Gi

---
apiVersion: v1 
kind: PersistentVolumeClaim 
metadata: 
  name: repo-data-my-gitlab-gitaly-0
spec: 
  accessModes: 
  - ReadWriteOnce 
  storageClassName: nfs-client 
  resources:  
    requests: 
      storage: 50Gi

rules:
  - host: kas.yuhan.tech
    http:
      paths:
      - backend:
          service:
            name: my-gitlab-kas
            port:
              number: 8154
        path: /k8s-proxy/
        pathType: Prefix
      - backend:
          service:
            name: my-gitlab-kas
            port:
              number: 8150
        path: /
        pathType: Prefix

- host: registry.yuhan.tech
    http:
      paths:
      - backend:
          service:
            name: my-gitlab-registry
            port:
              number: 5000
        path: /
        pathType: Prefix
  tls:
  - hosts:
    - registry.yuhan.tech
    secretName: all-yuhan-tech-tls

- host: gitlab.yuhan.tech
    http:
      paths:
      - backend:
          service:
            name: my-gitlab-webservice-default
            port:
              number: 8181
        path: /
        pathType: Prefix

git clone **ssh://**git@gitlab.yuhan.tech**:30122/kgd**/dataacquire.git

Host gitlab
  User git
  Hostname gitlab.yuhan.tech:30122
  PreferredAuthentications publickey
  IdentityFile ~/.ssh/id_ed25519_gitlab_dfface

# 集群名
clusterName: "cluster-production"

image:
  repository: "apache/rocketmq"
  tag: "4.9.4"

broker:
  # 3 个 master 节点，每个 master 具有1个副节点，共6个 broker 节点
  size:
    master: 1
    replica: 1

  persistence:
    enabled: true
    size: 8Gi
    storageClass: nfs-client

  # 主节点资源分配
  master:
    brokerRole: ASYNC_MASTER
    jvmMemory: " -Xms4g -Xmx4g -Xmn1g "
    resources:
      limits:
        cpu: 4
        memory: 12Gi
      requests:
        cpu: 200m
        memory: 6Gi
  
  # 副节点资源分配
  replica:
    jvmMemory: " -Xms1g -Xmx1g -Xmn256m "
    resources:
      limits:
        cpu: 4
        memory: 8Gi
      requests:
        cpu: 50m
        memory: 2Gi

nameserver:
  replicaCount: 3

  # 修改 nameserver 容器镜像地址和版本
  #image:
  #  repository: "apacherocketmq/rocketmq-nameserver"
  #  tag: "4.5.0-alpine-operator-0.3.0"

  resources:
    limits:
      cpu: 4
      memory: 8Gi
    requests:
      cpu: 50m
      memory: 1Gi
  
  persistence:
    enabled: true
    size: 8Gi
    #storageClass: gp2

dashboard:
  enabled: true
  replicaCount: 1

  ingress:
    enabled: false
    className: "nginx"
    hosts:
      - host: rocketmq.yuhan.tech
        paths:
          - path: /
            pathType: ImplementationSpecific
    #tls:
    #  - secretName: example-com-tls
    #    hosts:
    #      - rocketmq.example.com

- host: rocketmq.yuhan.tech
    http:
      paths:
      - backend:
          service:
            name: my-rocketmq-dashboard
            port:
              number: 8080
        path: /
        pathType: ImplementationSpecific

apiVersion: v1 
kind: PersistentVolumeClaim 
metadata: 
  name: mongodb-pvc 
spec: 
  accessModes: 
  - ReadWriteOnce 
  storageClassName: nfs-client 
  resources:  
    requests: 
      storage: 20Gi

** Please be patient while the chart is being deployed **

MongoDB® can be accessed on the following DNS name(s) and ports from within your cluster:

    my-mongodb.default.svc.cluster.local

To get the root password run:

    export MONGODB_ROOT_PASSWORD=$(kubectl get secret --namespace default my-mongodb -o jsonpath="{.data.mongodb-root-password}" | base64 -d)

To connect to your database, create a MongoDB® client container:

    kubectl run --namespace default my-mongodb-client --rm --tty -i --restart='Never' --env="MONGODB_ROOT_PASSWORD=$MONGODB_ROOT_PASSWORD" --image docker.io/bitnami/mongodb:6.0.4-debian-11-r10 --command -- bash

Then, run the following command:
    mongosh admin --host "my-mongodb" --authenticationDatabase admin -u root -p $MONGODB_ROOT_PASSWORD

To connect to your database from outside the cluster execute the following commands:

    kubectl port-forward --namespace default svc/my-mongodb 27017:27017 &
    mongosh --host 127.0.0.1 --authenticationDatabase admin -p $MONGODB_ROOT_PASSWORD

Thank you for installing neo4j.

Your release "my-neo4j" has been installed
 .

The neo4j user's password has been set to "YmkGAFYzieUlA8".To view the progress of the rollout try:

  $ kubectl rollout status --watch --timeout=600s statefulset/my-neo4j

Once rollout is complete you can log in to Neo4j at "neo4j://my-neo4j.default.svc.cluster.local:7687". Try:

  $ kubectl run --rm -it --image "neo4j:5.5.0" cypher-shell \
     -- cypher-shell -a "neo4j://my-neo4j.default.svc.cluster.local:7687" -u neo4j -p "or6saMeRDcZyL1"

Graphs are everywhere!

WARNING: Passwords set using 'neo4j.password' will be stored in plain text in the Helm release ConfigMap.
Please consider using 'neo4j.passwordFromSecret' for improved security.

kubectl run -it --rm neo4j-utils
--image=neo4j:4.0.3 --restart=Never --namespace neo4j --command -- bash

./bin/neo4j-admin

docker run -it --restart always \
  --publish=7474:7474 --publish=7687:7687 \
  --user="$(id -u):$(id -g)" \
  -e NEO4J_AUTH=none \
  --env NEO4JLABS_PLUGINS='["graph-data-science"]' \
  neo4j:4.4

~~helm repo add bitnami https://charts.bitnami.com/bitnami

helm show values bitnami/harbor > harbor.yml

helm install my-harbor bitnami/harbor -f harbor.yml

helm upgrade my-harbor bitnami/harbor -f harbor.yml~~

helm repo add harbor https://helm.goharbor.io
helm show values harbor/harbor > harbor.yml
helm install my-harbor  harbor/harbor -f harbor.yml

** Please be patient while the chart is being deployed **

1. Get the Harbor URL:

  NOTE: It may take a few minutes for the LoadBalancer IP to be available.
        Watch the status with: 'kubectl get svc --namespace default -w my-harbor'
    export SERVICE_IP=$(kubectl get svc --namespace default my-harbor --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
    echo "Harbor URL: http://$SERVICE_IP/"

2. Login with the following credentials to see your Harbor application

  echo Username: "admin"
  echo Password: $(kubectl get secret --namespace default my-harbor-core-envvars -o jsonpath="{.data.HARBOR_ADMIN_PASSWORD}" | base64 -d)

# 账户 admin 密码 Harbor12345
Please wait for several minutes for Harbor deployment to complete.
Then you should be able to visit the Harbor portal at https://harbor.yuhan.tech
For more details, please visit https://github.com/goharbor/harbor

ingress.kubernetes.io/proxy-body-size: 10000m  # 老 k8s 版本用
nginx.ingress.kubernetes.io/proxy-body-size: 10000m  # 最新版本使用

helm repo add bitnami https://charts.bitnami.com/bitnami
helm install my-fluentd bitnami/fluentd --version 5.5.15

helm show values bitnami/fluentd > fluentd.yml
helm install my-fluentd bitnami/fluentd -f fluentd.yml

** Please be patient while the chart is being deployed **

  To verify that Fluentd has started, run:

    kubectl get all -l "app.kubernetes.io/name=fluentd,app.kubernetes.io/instance=my-fluentd"

  Logs are captured on each node by the forwarder pods and then sent to the aggregator pods. By default, the aggregator pods send the logs to the standard output.
  You can see all the logs by running this command:

    kubectl logs -l "app.kubernetes.io/component=aggregator"

  You can mount your own configuration files to the aggregators and the forwarders. For example, this is useful if you want to forward the aggregated logs to Elasticsearch or another service.

helm repo add jenkins https://charts.jenkins.io
helm repo update

helm show values jenkins/jenkins > jenkins.yml
helm install my-jenkins jenkins/jenkins -f jenkins.yml

helm upgrade my-jenkins jenkins/jenkins -f jenkins.yml

NOTES:
1. Get your 'admin' user password by running:
  kubectl exec --namespace default -it svc/my-jenkins -c jenkins -- /bin/cat /run/secrets/additional/chart-admin-password && echo
2. Visit https://jenkins.yuhan.tech

3. Login with the password from step 1 and the username: admin
4. Configure security realm and authorization strategy
5. Use Jenkins Configuration as Code by specifying configScripts in your values.yaml file, see documentation: https://jenkins.yuhan.tech/configuration-as-code and examples: https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos

For more information on running Jenkins on Kubernetes, visit:
https://cloud.google.com/solutions/jenkins-on-container-engine

For more information about Jenkins Configuration as Code, visit:
https://jenkins.io/projects/jcasc/

NOTE: Consider using a custom image with pre-installed plugins

sudo systemctl edit docker.service

# 修改默认 nano 为 vim
sudo update-alternatives --config editor

[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -H fd:// -H tcp://127.0.0.1:2375

sudo systemctl daemon-reload

sudo systemctl restart docker.service

sudo systemctl edit docker.service

sudo systemctl daemon-reload

sudo systemctl restart docker.service