5 steps to bring DevX automation to your company
Get the guide

Using GitHub Actions and Okteto Cloud to Preview your Changes

Preview environments serve an important role when performing code reviews for an incoming change or addition to an application's codebase. It is a fantastic way for technical and non-technical members of your team to assess and give feedback on the changes made to your application.

In previous posts of our series on FastAPI you have learned how to build a FastAPI application, deploy the application to Okteto and add a database to it using Okteto stacks. In this article, you will learn how to automatically create a preview environment for your pull requests, using GitHub Actions and Okteto.

What Are GitHub Actions

GitHub Actions are event-driven task automation tools that runs a series of command after an event has occurred. These events and commands are contained in a workflow file. The workflow file is responsible for the orderly execution by GitHub Actions.

Creating A GitHub Action Workflow

GitHub Actions are created and managed from the Actions tab in a repository. Create a new workflow from the Actions tab:

Create A New Workflow

There are a number of available templates in the GitHub Actions page. However, click on the set up a workflow yourself link. This opens a new page with a default workflow, let's rewrite the workflow file:

Start by defining the name of the workflow, and the event which should trigger the execution of the workflow file:

name: CRUD App Preview Deployment

      - main

In the code block above, we have set the name of the workflow, and the event to trigger the workflow. The workflow file is executed when a pull request is made to the main branch. Next, let's define the series of tasks to be executed. These tasks are called jobs in GitHub Actions.

Add the instructions below to the existing code in the workflow file:

    runs-on: ubuntu-latest
    - name: Context
      uses: okteto/context@latest
        token: ${{ secrets.OKTETO_TOKEN }}

    - name: Deploy preview environment
      uses: okteto/deploy-preview@latest
       GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        name: pr-${{ github.event.number }}-cindylopez
        scope: personal
        timeout: 15m

In the code block above, we defined the job preview which runs on the ubuntu-latest environment. The steps to be executed under this job is defined under the steps heading. Let's go over these steps.

Replace namespace in the code block above with your Okteto default namespace.


In our preview job, we have just one task to be executed.

  1. Deploy preview environment: This step uses the action okteto/deploy-preview@latest to deploy the application using the okteto stack file defined in the repository. It will automatically login into your Okteto account making use of secrets.OKTETO_TOKEN. It will also add a comment on the pull request discussion indicating a link to the deployed application. Once again, we have witnessed the adaptability of Okteto stacks.

Adding Your Okteto Token To GitHub

Before adding your Okteto token to GitHub, retrieve your Okteto token from your dashboard settings:

Okteto dashboard - Settings

The workflow file needs your Okteto account token to function properly. Follow the steps below to add your okteto token to your GitHub repository:

  1. In your repository, navigate to the Settings tab and click on the Secrets link on the menu by the left:


  1. Click on New Repository Secret

Add A New Secret

  1. Create a new secret OKTETO_TOKEN and set the value to the token you copied from your dashboard.

Create New Secret

You can learn more on how to store and manage GitHub secrets on their official documentation.

Building The Preview Environment

With the secret in place, let's go on to create a pull request from the mongodb-crud branch into the main branch to see the workflow in action:

New Pull Request

Immediately the pull request is created, the workflow kicks into action:

Workflow In Action

To monitor the progress of the workflow in action, navigate to the Actions tab. The current workflow is listed like in the image below:

Actions Tab

Click on the workflow currently under execution. In the workflow page, click on the preview job to view the execution and logs of each step:

Preview Job

The tasks undergoing execution are listed:

Tasks undergoing execution

With all the necessary details put in place, the execution completes successfully:

Workflow complete

Return to the pull request thread to view the comment made by github-actions bot:


Destroying Preview Environment

The preview environment ceases to be of use after the pull request has been merged. As such, there is no point in keeping the namespace created by the workflow earlier as newer pull requests will create new namespaces. Okteto provides an action to automatically delete a namespace.

Repeating the steps followed in creating a workflow above, create a new workflow preview-close to automatically destroy the namespace after the pull request has either been merged or close:

name: Delete Preview Namespace

      - closed

    runs-on: ubuntu-latest
      - name: checkout
        uses: actions/checkout@master

      - name: Context
        uses: okteto/context@latest
          token: ${{ secrets.OKTETO_TOKEN }}

      - name: Destroy preview environment
        uses: okteto/destroy-preview@latest
          name: pr-${{ github.event.number }}-namespace

Remember to change namespace to your Okteto namespace.

With the workflow in place, let's merge the pull request and verify that the Destroy Preview environment workflow was executed:

Merge Pull Request

Navigate to the Actions tab and click on the workflow undergoing execution:

Actions Tab

The namespace has been deleted successfully:

Workflow Execution Complete


In this article, you built a workflow for creating a preview environment when a pull request is made to the main branch and another workflow to delete the namespace containing the preview environment after the pull request has either been closed or merged.

Once again, the deployment of the preview environment was made possible by the stack manifest we have been using from the first post in the series. This way, you are reusing the same manifest for development, deployment, and preview environments.

The complete code used in this article can be found in our GitHub repository

Abdulazeez Abdulazeez AdeshinaDeveloper Advocate / The ProfessorView all posts

Automate Provisioning Any Dev Resource on Any Cloud Provider With Pulumi and Okteto

The Value It is common in today's landscape to build microservices-based applications that leverage resources like RDS databases, storage buckets, etc...

October 19, 2023
Avatar of Arsh SharmaAvatar of Arsh SharmaArsh Sharma

How Developers Can Seamlessly Collaborate When Building Microservice Apps

Building microservices based applications is inherently challenging. Given the multitude of components involved, it is unrealistic to expect any individual...

October 10, 2023
Avatar of Arsh SharmaAvatar of Arsh SharmaArsh Sharma