Version: 3.10

Scaffold and Deploy FastAPI Application

Overview

This use case outlines the process of creating and deploying a FastAPI application using KubeRocketCI. The purpose is to provide developers with a streamlined approach to generate a functional code structure for a FastAPI web application, including basic read functionality. The process also allows for customization to meet specific requirements and deployment to a development environment. By utilizing a standardized process for code review, testing, and deployment, developers can save time and effort while ensuring high code quality and reliability. The goal is to empower the development team to release new features and applications more efficiently, while maintaining a high level of code quality and reliability. The KubeRocketCI is used to facilitate this process.

Roles

This documentation is tailored for the Developers and Team Leads.

Goals

Create a new FastAPI application quickly.
Deploy the initial code to the DEV environment.
Check CI pipelines.
Delivery update using the GitOps approach.

Preconditions

KubeRocketCI instance is configured with GitOps repo.
Developer has access to the KubeRocketCI instances using the Single-Sign-On approach.
Developer has merge permissions in the GitOps repository on GitHub.

Scenario

To scaffold and deploy FastAPI Application, follow the steps below.

Scaffold the New FastAPI Application

Log in to the KubeRocketCI portal:
Navigate to the user's Account settings tab:
Ensure the Namespace value points to the namespace with the KubeRocketCI installation:

note
Don't forget to click the + Add button to add the namespace to the allowed namespaces list.
Create a new Codebase with the Application type using the Create from template strategy. Select the Components section and click + Create component:
Choose the Application Codebase type as we intend to deliver our application as a container and deploy it within the Kubernetes cluster. Click the Next button:
Opt for the Create from template strategy to scaffold our application from the template provided by the KubeRocketCI and click Create:
On the Add component info tab, define the following values and click Next:
- Git server: github
- Repository name: {github_account_name}/fastapi-demo
- Component name: fastapi-demo
- Description: fastapi-demo
- Application code language: Python
- Language version/framework: FastAPI
- Build tool: Python
On the Specify advanced settings tab, define the values and click Create:
- Default branch: main
- Deployment Options: helm-chart
- Codebase versioning type: edp
- Start version from: 0.1.0 and SNAPSHOT
Check the application status. It should be green:

Deploy Application to the Development Environment

This section outlines the approach for deploying the application from the latest commit on the main branch. The following steps are involved:

Build the initial version of the application from the last commit on the main branch. This version is generated from the provided template.
Set up a deployment flow to enable continuous delivery to the development environment.
Deploy the initial version of the application to the development environment.

To succeed with the steps above, follow the instructions below:

Build Container from the latest branch commit. To build the initial version of the application's main branch, go to the Components -> fastapi-demo -> Branches -> main and click the Build button:
Build pipeline for the fastapi-demo application starts:
Track Pipeline's status by clicking the build-fastapi-demo-main-6ef1 pipeline link.
Ensure that Build Pipeline was successfully completed.
To enable application deployment create a Deployment Flow with a single environment - Development (with the name dev).

note
To utilize and manage various environments through the KubeRocketCI platform, the initial step is to onboard a new GitOps repository.
Navigate to the Deployment Flows tab and click the corresponding button to create new GitOps repository:
Click to the + Add GitOps repository:
Select the Create strategy and github server, enter GitHub account name and click Save:
In the KubeRocketCI portal, navigate to Deployment FLows tab and click the + Create deployment flow button to create pipeline:
In the Create deployment flow dialog, fill in the required fields:
- Enter name:
  - Pipeline name: mypipe
  - Description: Deployment flow for fasapi application
- Add applications:
  - Applications: Add fastapi-demo application
  - Branch: Select main branch
  - Promote applications: Leave unchecked
Now click the Go to deployment flow button to continue creating the environment:
In the Deployment Flow details page, click the + Create environment button to create new environment and fill in the required fields:
- Cluster: in-cluster
- Environment name: dev
- Description: Development Environment
- Trigger type: Manual
- Deploy Pipeline template: deploy
- Clean Pipeline template: clean
- Quality gate type: Manual
As soon as the values is defined, click the Create button.
Deploy the initial version of the application to the development environment:
- Open deployment flow with the name mypipe.
- Select the dev environment from the Environment tab.
- Click the Configure deploy button.
- In the Select image tag field select version 0.1.0-SNAPSHOT.1 and click the Start deploy button.

Check the Application Status

To ensure the application is deployed successfully, follow the steps below:

Ensure application status is Healthy and Synced, and the Deployed version points to 0.1.0-SNAPSHOT.1:

Check that the selected version of the container is deployed on the dev environment. ${KRCI_ENV} - is the KRCI namespace name:

# Check the deployment status of fastapi-demo application
$ kubectl get deployments -n ${KRCI_ENV}-mypipe-dev
NAME           READY   UP-TO-DATE   AVAILABLE   AGE
fastapi-demo   1/1     1            1           14m

Deliver New Code

This section describes the code delivery process. We need to deploy our fastapi-demo application that deploys Ingress object to expose API outside the Kubernetes cluster.

Within the GitOps repository, follow the naming convention <deployment-flow>/<environment>/<application-name>-values.yaml to create the chart values file. For our case, use mypipe/dev/fastapi-demo-values.yaml as the file name. To deploy application with custom application Helm chart values, follow he steps below:

Commit mypipe/dev/fastapi-demo-values.yaml file to the default branch of the GitOps repository:

mypipe/dev/fastapi-demo-values.yaml
ingress:
  enabled: true

Deploy the fastapi-demo application to the environment. Before the new version deployment, check the ingress object in dev environment:
```
$ kubectl get ingress -n ${KRCI_ENV}-mypipe-dev
No resources found in ${KRCI_ENV}-mypipe-dev namespace.
```
No ingress object exists as expected.
Deploy the fastapi-demo application which has the ingress object in place. Since we use Manual deployment approach, we perform version upgrade manually:

To ensure our application recognizes the changes in the GitOps repository related to enabling the creation of the Ingress resource, we need to set the Override values checkbox to true before deploying.
- Go to the Environments section of the KubeRocketCI portal, select mypipe and choose dev stage.
- In the Select image tag section select the version 0.1.0-SNAPSHOT.1.
- Set the Values override checkbox to true and click the Start deploy button.
- Check that the application is deployed and application status is Healthy and Synced.

Check that the new version with Ingress is deployed:

# Check Ingress object
kubectl get ingress -n ${KRCI_ENV}-mypipe-dev
NAME           CLASS    HOSTS                                     ADDRESS          PORTS   AGE
fastapi-demo   <none>   fastapi-demo-ko1zs-example.com         10.100.182.134        80    14m

# Check application external URL
curl https://your-hostname-appeared-in-hosts-column-above.example.com
{"Hello":"World"}

Overview​

Roles​

Goals​

Preconditions​

Scenario​

Scaffold the New FastAPI Application​

Deploy Application to the Development Environment​

Check the Application Status​

Deliver New Code​

Related Articles​