CStack to Airbase V2 Migration Guide

This guide will help you evaluate and migrate your CStack application to Airbase V2.

Need help? Reach out at #cstack-helloworld.

Migration Steps

Before proceeding with migration, review the compatibility requirements and limitations below to ensure your application is suitable for migration.

Once you’ve confirmed you want to proceed with migration. Follow these steps to convert from a CStack repo to an Airbase repo

1. Replace CStack pipeline with Airbase pipeline
2. Log in to Airbase, create team and project
3. Integrate with GitLab to setup Airbase + GitLab variables
4. Deploy to Airbase V2

Compatibility

Your application is suitable for migration if it meets these criteria:

1. Uses only CStack internet; no CStack gen-routable components
2. Does not use CStack S3 or CStack RDS
3. Does not require SE Laptop access
4. Does not need filesystem volumes (Persistent Volume Claims)
5. Does not use Kubernetes Cron Jobs

Supported Applications for Airbase V2

Airbase V2 supports the following types of applications:

1. Single-container applications
2. Containerised frontend and backend apps
3. Apps with API integrations only (S3 via access key, DynamoDB via access key)

Airbase V2 Limitations

• No database
• No S3 bucket
• No access from SE laptop
• No custom domain support (for now)
• No private networking within a micro-service architecture (backend service to call worker service)
• Limited support for micro-service architectures
• No one-off or cron jobs (Kubernetes jobs)