pingcap / pingcap/docs-tidb-operator

阿里云 K8S环境搭建失败

Open
#2,516 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
52
Forks
129
Avg merge
12m
Merged PRs (30d)
2

Description

File: /release-1.5/zh/deploy-on-alibaba-cloud.md

文档提供的搭建方式太老了,不适配现在的阿里云服务。
比如创建k8s集群时报错如下
│ Error: [ERROR] terraform-provider-alicloud/alicloud/resource_alicloud_cs_managed_kubernetes.go:714: Resource alicloud_cs_managed_kubernetes CreateKubernetesCluster Failed!!! %!s(*cs.ClusterCommonResponse=):
│ Aliyun API Error: RequestId: Status Code: 400 Code: InvalidKubernetesVersion Message: The specified KubernetesVersion 1.14.8-aliyun.1 is invalid, allowd values are [1.28.3-aliyun.1 1.26.3-aliyun.1 1.24.6-aliyun.1]

│ with module.tidb-operator.alicloud_cs_managed_kubernetes.k8s,
│ on ../modules/aliyun/tidb-operator/main.tf line 51, in resource "alicloud_cs_managed_kubernetes" "k8s":
│ 51: resource "alicloud_cs_managed_kubernetes" "k8s" {
将集群配置更新为1.24.6-aliyun.1后,还有以下诸多错误
module.tidb-operator.null_resource.setup-env (local-exec): error: error parsing https://raw.githubusercontent.com/pingcap/tidb-operator/v1.5.2/manifests/crd.yaml: read tcp 172.16.147.188:56506->185.199.110.133:443: read: connection reset by peer
module.tidb-operator.null_resource.setup-env (local-exec): serviceaccount/tiller created
module.tidb-operator.null_resource.setup-env (local-exec): error: resource mapping not found for name: "tiller-clusterrolebinding" namespace: "" from "/root/tidb-operator/deploy/aliyun/tiller-rbac.yaml": no matches for kind "ClusterRoleBinding" in version "rbac.authorization.k8s.io/v1alpha1"
module.tidb-operator.null_resource.setup-env (local-exec): ensure CRDs are installed first
module.tidb-operator.null_resource.setup-env (local-exec): storageclass.storage.k8s.io/alicloud-disk created
module.tidb-operator.null_resource.setup-env (local-exec): configmap/local-provisioner-config created
module.tidb-operator.null_resource.setup-env (local-exec): storageclass.storage.k8s.io/local-volume created
module.tidb-operator.null_resource.setup-env (local-exec): daemonset.apps/local-volume-provisioner created
module.tidb-operator.null_resource.setup-env (local-exec): Error from server (NotFound): daemonsets.apps "flexvolume" not found
module.tidb-operator.null_resource.setup-env (local-exec): WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /root/tidb-operator/deploy/aliyun/credentials/kubeconfig
module.tidb-operator.null_resource.setup-env (local-exec): WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /root/tidb-operator/deploy/aliyun/credentials/kubeconfig
module.tidb-operator.null_resource.setup-env (local-exec): WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /root/tidb-operator/deploy/aliyun/credentials/kubeconfig
module.tidb-operator.null_resource.setup-env (local-exec): WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /root/tidb-operator/deploy/aliyun/credentials/kubeconfig
module.tidb-operator.null_resource.setup-env (local-exec): Error: unknown command "init" for "helm"

module.tidb-operator.null_resource.setup-env (local-exec): Did you mean this?
module.tidb-operator.null_resource.setup-env (local-exec): lint

module.tidb-operator.null_resource.setup-env (local-exec): Run 'helm --help' for usage.
module.tidb-operator.null_resource.setup-env (local-exec): WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /root/tidb-operator/deploy/aliyun/credentials/kubeconfig
module.tidb-operator.null_resource.setup-env (local-exec): WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /root/tidb-operator/deploy/aliyun/credentials/kubeconfig
module.tidb-operator.null_resource.setup-env: Still creating... [6m30s elapsed]
module.tidb-operator.null_resource.setup-env (local-exec): NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
module.tidb-operator.null_resource.setup-env: Creation complete after 6m31s [id=8988119212040749810]
module.tidb-operator.data.helm_repository.pingcap: Reading...
module.tidb-operator.data.helm_repository.pingcap: Read complete after 0s [id=pingcap]
module.tidb-operator.helm_release.tidb-operator: Creating...

│ Warning: "internet_max_bandwidth_in": [DEPRECATED] The attribute is invalid and no any affect for the instance. So it has been deprecated from version v1.121.2.

│ with module.bastion.alicloud_instance.bastion,
│ on ../modules/aliyun/bastion/bastion.tf line 32, in resource "alicloud_instance" "bastion":
│ 32: resource "alicloud_instance" "bastion" {



│ Error: deployments.apps "tiller-deploy" not found

│ with module.tidb-operator.helm_release.tidb-operator,
│ on ../modules/aliyun/tidb-operator/operator.tf line 52, in resource "helm_release" "tidb-operator":
│ 52: resource "helm_release" "tidb-operator" {

是否能基于当前的阿里云环境提供一个适配的文档?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with release-1.5/zh/deploy-on-alibaba-cloud.md and trace the referenced Terraform files, including modules/aliyun/tidb-operator/main.tf and operator.tf. Review the reported Kubernetes, RBAC, Helm, CRD, and FlexVolume failures against the current Alibaba Cloud environment. Done means the documented setup works with supported versions and no longer produces the reported deployment errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes, terraform
Domain
cloud, devops, documentation, infrastructure
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.