GitHub Actions
vCluster.Pro provides the following GitHub Actions for use in workflows:
- Setup DevSpace: Installs the
devspaceCLI - Setup vCluster: Installs the
vclusterCLI
Virtual Clusters for Pull Requests
These examples show how to create and delete Virtual Clusters for pull requests.
- Basic
- Reuse
- DevSpace
This example shows how to create and delete a virtual cluster for testing an application named my-app on pull requests.
# .github/workflows/vclusters.yaml
name: Pull Request Checks
on:
pull_request:
branches:
- "main"
jobs:
e2e:
runs-on: ubuntu-latest
steps:
- name: Install vCluster CLI
uses: loft-sh/setup-vcluster@main
- name: Login to vCluster.Pro instance
env:
LOFT_URL: ${{ secrets.LOFT_URL }}
ACCESS_KEY: ${{ secrets.ACCESS_KEY }}
run: vcluster login $LOFT_URL --access-key $ACCESS_KEY
- name: Create PR Virtual Cluster
env:
NAME: pr-${{ github.event.pull_request.number }}-${{ github.sha }}-${{ github.run_id }}
run: vcluster create $NAME --project default
- name: Deploy Application
run: kubectl apply -Rf ./kubernetes
- name: Wait for Deployment
run: kubectl rollout status deployments/my-app
- name: Run Tests
run: make e2e
- name: Delete PR Virtual Cluster
env:
NAME: pr-${{ github.event.pull_request.number }}-${{ github.sha }}-${{ github.run_id }}
run: vcluster delete $NAME --project default
Explanation:
- The Setup vCluster.Pro action is used to install the vCluster CLI.
- The
vcluster logincommand is used to log in to the organization's vCluster.Pro instance. Environment variablesLOFT_URLandACCESS_KEYare populated using GitHub secrets. - The
vcluster createcommand is used to create a unique virtual cluster using information about the pull request in thedefaultproject. This will automatically configure the kube context for the next steps. - The next step deploys the application using the runner provided
kubectland manifests located under./kubernetes. - Before running tests, we use
kubectlto wait for themy-appdeployment to become ready. - Now we run the end-to-end tests. In this example we're using
maketo run tests, but the command should be customized for your testing framework. - Finally, the
vcluster deletecommand is used to delete the virtual cluster.
This example shows how to create and reuse a virtual cluster for testing an application named my-app on pull requests.
# .github/workflows/vclusters.yaml
name: Pull Request Checks
on:
pull_request:
branches:
- "main"
jobs:
e2e:
runs-on: ubuntu-latest
steps:
- name: Install vCluster CLI
uses: loft-sh/setup-vcluster@main
- name: Login to vCluster.Pro instance
env:
LOFT_URL: ${{ secrets.LOFT_URL }}
ACCESS_KEY: ${{ secrets.ACCESS_KEY }}
run: vcluster login $LOFT_URL --access-key $ACCESS_KEY
- name: Create PR Virtual Cluster
env:
NAME: pr-${{ github.event.pull_request.number }}-${{ github.sha }}-${{ github.run_id }}
run: vcluster create $NAME --project default --upgrade
- name: Deploy Application
run: kubectl apply -Rf ./kubernetes
- name: Wait for Deployment
run: kubectl rollout status deployments/my-app
- name: Run Tests
run: make e2e
Explanation:
- The Setup vCluster.Pro action is used to install the vCluster CLI.
- The
vcluster logincommand is used to log in to the organization's vCluster.Pro instance. Environment variablesLOFT_URLandACCESS_KEYare populated using GitHub secrets. - The
vcluster createcommand is used to create a unique virtual cluster using information about the pull request in thedefaultproject. This will automatically configure the kube context for the next steps. The--upgradeflag has been added to reuse the existing virtual cluster and upgrade it to the latest version. Additional flags may be used to control the desired virtual cluster version. - The next step deploys the application using the runner provided
kubectland manifests located under./kubernetes. - Before running tests, we use
kubectlto wait for themy-appdeployment to become ready. - Now we run the end-to-end tests. In this example we're using
maketo run tests, but the command should be customized for your testing framework.
This example shows how use the Setup Devspace GitHub Action to install the DevSpace CLI and DevSpace commands to run tests.
# .github/workflows/vclusters.yaml
name: Pull Request Checks
on:
pull_request:
branches:
- "main"
jobs:
e2e:
runs-on: ubuntu-latest
steps:
- name: Install DevSpace CLI
uses: loft-sh/setup-devspace@main
- name: Install vCluster CLI
uses: loft-sh/setup-vcluster@main
- name: Login to vCluster.Pro instance
env:
LOFT_URL: ${{ secrets.LOFT_URL }}
ACCESS_KEY: ${{ secrets.ACCESS_KEY }}
run: vcluster login $LOFT_URL --access-key $ACCESS_KEY
- name: Create PR Virtual Cluster
env:
NAME: pr-${{ github.event.pull_request.number }}-${{ github.sha }}-${{ github.run_id }}
run: vcluster create $NAME --project default
- name: Run Tests
run: devspace run e2e
Explanation:
- The Setup DevSpace action installs the DevSpace CLI.
- The Setup vCluster.Pro action is used to install the vCluster CLI.
- The
vcluster logincommand is used to log in to the organization's vCluster.Pro instance. Environment variablesLOFT_URLandACCESS_KEYare populated using GitHub secrets. - The
vcluster createcommand is used to create a unique virtual cluster using information about the pull request in thedefaultproject. This will automatically configure the kube context for the next steps. - Finally we use
devspace run e2eto perform the needed steps to deploy and testmy-app.