Kubernetes

​

Prerequisites

• Integration apps configured
• Backend and Frontend environment variables set up

​

Deployment

​

Step 1: Setting Up Your GitHub Access Token for Cloning

​

1.1. Obtain Your Cloning Access Token

• Reach out to the Duckie team for your cloning_access_token
• You can contact us at founders@duckie.ai

​

1.2. Set up the token on your machine

Once you have received your cloning_access_token, follow these steps to set it up:

1. Enter the following command, replacing your_cloning_access_token_here with the actual token you received:

   export GITHUB_TOKEN=your_cloning_access_token_here
   

2. To verify that the token has been set correctly, you can echo the variable: This should display your token.

   echo $GITHUB_TOKEN
   

​

Step 2: Cloning the Duckie Repository

To clone a Git repository, you can use the git clone command. Follow the steps below:

1. Open your terminal or command prompt.

2. Use the following command to clone the repository:

   git clone https://github.com/musa-dev-team/duckie-selfhost.git
   

​

Step 3: Create a new configmaps.yaml file in the kube_setup directory

1. Navigate to the kube_setup directory
2. Create a new file named configmaps.yaml
3. Paste the contents of the configmaps.yaml file into your configmaps.yaml file using the example below as a template
4. Use the default_values.yaml file to set the default values for the configurations, or configure your own in the superbase-kubernetes directory

    apiVersion: v1
    kind: ConfigMap
    metadata:
    name: backend-env
    namespace: duckie
    data:
    .env: |
        # Copy all backend .env content here

    ---
    apiVersion: v1
    kind: ConfigMap
    metadata:
    name: frontend-env
    namespace: duckie
    data:
    .env: |
        # Copy all frontend .env content here

​

Step 4: Deploying the Duckie Application

To deploy the Duckie application, follow the steps located in the README.md in the kubernetes directory.