github.com/1aal/kubeblocks@v0.0.0-20231107070852-e1c03e598921/pkg/cli/cmd/kubeblocks/data/eks_preflight.yaml (about) 1 apiVersion: troubleshoot.sh/v1beta2 2 kind: Preflight 3 metadata: 4 name: kubeblocks_preflight 5 spec: 6 collectors: 7 - clusterInfo: {} 8 analyzers: 9 - clusterVersion: 10 checkName: EKS-Version 11 outcomes: 12 - fail: 13 when: "< 1.22.0" 14 message: This application requires at least Kubernetes 1.22.0 or later 15 uri: https://www.kubernetes.io 16 - pass: 17 when: ">= 1.22.0" 18 message: Your cluster meets the recommended and required versions(>= 1.22.0) of Kubernetes 19 uri: https://www.kubernetes.io 20 - nodeResources: 21 checkName: At-Least-3-Nodes 22 outcomes: 23 - warn: 24 when: "count() < 3" 25 message: This application requires at least 3 nodes 26 - pass: 27 message: This cluster has enough nodes. 28 - deploymentStatus: 29 checkName: AWS-Load-Balancer-Check 30 name: aws-load-balancer-controller 31 namespace: kube-system 32 outcomes: 33 - warn: 34 when: "absent" # note that the "absent" failure state must be listed first if used. 35 message: The aws-load-balancer-controller deployment is not present 36 - warn: 37 when: "< 1" 38 message: The aws-load-balancer-controller deployment does not have any ready replicas 39 - warn: 40 when: "= 1" 41 message: The aws-load-balancer-controller deployment has only a single ready replica 42 - pass: 43 message: There are multiple replicas of the aws-load-balancer-controller deployment ready 44 extendAnalyzers: 45 - clusterAccess: 46 checkName: Check-K8S-Access 47 outcomes: 48 - fail: 49 message: K8s cluster access fail 50 - pass: 51 message: K8s cluster access ok 52 - taint: 53 checkName: Required-Taint-Match 54 outcomes: 55 - fail: 56 message: All nodes had taints that the pod didn't tolerate 57 - pass: 58 message: The taint matching succeeded 59 - storageClass: 60 checkName: Required-Default-SC 61 outcomes: 62 - warn: 63 message: The default storage class was not found. To learn more details, please check https://docs.aws.amazon.com/zh_cn/eks/latest/userguide/storage-classes.html; Alternatively use option --set storageClass=<storageClassName> when creating cluster 64 - pass: 65 message: Default storage class is the presence, and all good on storage classes