From e6420c8d21eebe338da77f3e742dd75150c24451 Mon Sep 17 00:00:00 2001 From: Muse Mulatu Date: Tue, 22 Jul 2025 14:56:43 -0600 Subject: [PATCH] doc: add cse config --- docs/install/colony-prod/install-colony.md | 33 +++++++++++----------- 1 file changed, 17 insertions(+), 16 deletions(-) diff --git a/docs/install/colony-prod/install-colony.md b/docs/install/colony-prod/install-colony.md index 536e7df..23ae605 100644 --- a/docs/install/colony-prod/install-colony.md +++ b/docs/install/colony-prod/install-colony.md @@ -10,10 +10,10 @@ After reviewing the [required prerequisites](../colony-prod/prereqs-colony.md), ## Step 1 - Installing Colony -The following installation instructions apply to Colony version `v0.2`. +The following installation instructions apply to Colony version `v0.2.2`. ```bash - git clone https://github.com/konstructio/colony.git + git clone -b cse-config https://github.com/konstructio/colony.git cd colony go build . ``` @@ -28,17 +28,27 @@ The following installation instructions apply to Colony version `v0.2`. ## Step 3 - Run the Colony `init` +We introducted 3 additional arugments in the latest version. These arguments are required for CSE install. `gitlab-token` is used to clone and push changes to `autopilot` repository in the new Gitlab instance. `docker-token` is a Github PAT that has permission to GCR and `cse-installer` container image. `api-go-token` is used for creating region in staging (default endpoint). + ```bash ./colony init \ --api-key $YOUR_COLONY_API_KEY \ --load-balancer-interface \ --load-balancer-ip + --gitlab-token \ + --api-token \ + --docker-token \ ``` ```bash export KUBECONFIG=~/.colony/config ``` +Then update colony-agent image + ```bash + kubectl set image -n tink-system deploy/colony-colony-agent colony-agent=ghcr.io/konstructio/colony-agent:652a30e + ``` + ### Items to Note - `` refers to the interface connected to `network boot`. @@ -47,26 +57,17 @@ The following installation instructions apply to Colony version `v0.2`. ## Step 4 - Asset Discovery -To discover an asset run: - - ```bash - ./colony add-ipmi \ - --ip \ - --username \ - --password \ - --auto-discover - ``` - -The new asset will appear under the assets tab in the Colony UI. +PXE boot your new servers. The asset will appear under the assets tab in the Colony UI. ## Step 5 - Adding a Cluster -After your Assets are discovered and listed as available you can use them to provision a cluster. You must have a minimum of two Assets to create a cluster (one for the Control plane and one for the Worker node). +After your Assets are discovered and listed as available you can use them to provision a cluster. You must have a minimum of 5 Assets to create a cluster (three for the Control plane and two for the Worker node). ![Create Cluster with Civo](../../img/civostack/initial-configuration.png) 1. Select **Create Cluster** to start this process. -2. Complete Cluster details, Control plane details, and Worker node information as desired. -3. Select **Create CivoStack**** to complete this process. +2. Fill out CSE config +3. Complete Control plane details, and Worker node information as desired. +4. Select **Create CivoStack**** to complete this process. ![Provisioning Clusters](../../img/civostack/provisioning.png)