From 383dced9a2d3851ea472c4ec90bdb4b41fe3aa31 Mon Sep 17 00:00:00 2001 From: Vladyslav_Prykhodko Date: Fri, 5 Jun 2026 18:41:03 +0300 Subject: [PATCH] fix(installation): clone k8s repos by full-version release branch thingsboard-ce-k8s / thingsboard-pe-k8s are branched per full version (release-4.3.1.2), not per minor release, so 'git clone -b release-4.3' failed on 12 cloud installation pages. Centralize the snippet in k8sCloneCmd() (src/util/install-commands.ts) and use it on all 16 k8s installation pages; keep CE_BRANCH for repos that do branch per minor release (thingsboard, rule-node-examples). --- .../docs/installation/aws-microservices.mdx | 8 ++-- .../docs/docs/installation/aws-monolith.mdx | 30 ++++++------- .../docs/installation/azure-microservices.mdx | 24 +++++----- .../docs/docs/installation/azure-monolith.mdx | 5 +-- .../docs/installation/gcp-microservices.mdx | 5 +-- .../docs/docs/installation/gcp-monolith.mdx | 5 +-- .../installation/minikube-cluster-setup.mdx | 5 +-- .../installation/openshift-cluster-setup.mdx | 5 +-- .../pe/installation/aws-microservices.mdx | 9 ++-- .../docs/pe/installation/aws-monolith.mdx | 45 +++++++++---------- .../pe/installation/azure-microservices.mdx | 9 ++-- .../docs/pe/installation/azure-monolith.mdx | 6 +-- .../pe/installation/gcp-microservices.mdx | 6 +-- .../docs/pe/installation/gcp-monolith.mdx | 25 +++++------ .../installation/minikube-cluster-setup.mdx | 6 +-- .../installation/openshift-cluster-setup.mdx | 6 +-- src/data/versions.ts | 6 ++- src/util/install-commands.ts | 10 +++++ 18 files changed, 107 insertions(+), 108 deletions(-) create mode 100644 src/util/install-commands.ts diff --git a/src/content/docs/docs/installation/aws-microservices.mdx b/src/content/docs/docs/installation/aws-microservices.mdx index 1fde69dd88..405e0b93e0 100644 --- a/src/content/docs/docs/installation/aws-microservices.mdx +++ b/src/content/docs/docs/installation/aws-microservices.mdx @@ -5,14 +5,12 @@ sidebar: description: "Deploy ThingsBoard CE in microservices mode on AWS EKS with managed PostgreSQL, MSK, and ElastiCache." --- import DocLink from '@components/DocLink.astro'; -import { Steps, Aside } from '@astrojs/starlight/components'; -import { Code } from '@astrojs/starlight/components'; +import { Aside, Code } from '@astrojs/starlight/components'; import ImageGallery from '~/components/ImageGallery.astro'; import { Products } from '~/models/site.models'; -import { CE_BRANCH } from '~/data/versions'; +import { k8sCloneCmd } from '~/util/install-commands'; -export const cloneCmd = `git clone -b ${CE_BRANCH} https://github.com/thingsboard/thingsboard-ce-k8s.git -cd thingsboard-ce-k8s/aws/microservices`; +export const cloneCmd = k8sCloneCmd('ce', 'aws/microservices'); This guide walks you through deploying ThingsBoard CE in microservices mode on AWS EKS. We use Amazon RDS for managed PostgreSQL, Amazon MSK for managed Kafka, and Amazon ElastiCache for managed Redis. diff --git a/src/content/docs/docs/installation/aws-monolith.mdx b/src/content/docs/docs/installation/aws-monolith.mdx index 673a145d30..f68c34842a 100644 --- a/src/content/docs/docs/installation/aws-monolith.mdx +++ b/src/content/docs/docs/installation/aws-monolith.mdx @@ -5,14 +5,12 @@ sidebar: description: "Deploy ThingsBoard CE in monolith mode on AWS EKS with managed PostgreSQL." --- import DocLink from '@components/DocLink.astro'; -import { Steps, Aside } from '@astrojs/starlight/components'; -import { Code } from '@astrojs/starlight/components'; +import { Aside, Code } from '@astrojs/starlight/components'; import ImageGallery from '~/components/ImageGallery.astro'; import { Products } from '~/models/site.models'; -import { CE_BRANCH } from '~/data/versions'; +import { k8sCloneCmd } from '~/util/install-commands'; -export const cloneCmd = `git clone -b ${CE_BRANCH} https://github.com/thingsboard/thingsboard-ce-k8s.git -cd thingsboard-ce-k8s/aws/monolith`; +export const cloneCmd = k8sCloneCmd('ce', 'aws/monolith'); This guide walks you through deploying ThingsBoard CE in monolith mode on AWS EKS. We use Amazon RDS for managed PostgreSQL. @@ -38,11 +36,11 @@ aws configure In the `cluster.yml` file you can find the suggested cluster configuration. Key fields you can change: -| Field | Default | Description | -|---|---|---| -| `region` | `us-east-1` | AWS region for the cluster | -| `availabilityZones` | `[us-east-1a, us-east-1b, us-east-1c]` | Region availability zones | -| `instanceType` | `m5.xlarge` | EC2 instance type for nodes | +| Field | Default | Description | +|---------------------|----------------------------------------|-----------------------------| +| `region` | `us-east-1` | AWS region for the cluster | +| `availabilityZones` | `[us-east-1a, us-east-1b, us-east-1c]` | Region availability zones | +| `instanceType` | `m5.xlarge` | EC2 instance type for nodes |