Develop production-like blueprints using K8s and Helm source files
Creating a Production-Like blueprint is done using industry-standard formats and tooling.
The blueprint definition process is aligned with your existing configurations and workflows so that it's easier for you to keep updating the blueprint as your product evolves.
To create a Production-Like blueprint, all you need is your existing production Kubernetes resource files extended with Velocity annotations.
Why do I need annotations in order to add services to Velocity?
Annotations are needed since your production configuration targets a specific environment, and Velocity defines a blueprint that is used for deploying multiple isolated environments.
How should I manage my velocity configuration?
Normally there are 3 options for placing Velocity's annotations:
K8s resource files: Keeping a dedicated version of your Kubernetes resource definitions with Velocity annotations included.
Helm values file: Using your original Helm chart (with annotations enabled) and a separate values file that extends it with Velocity's annotations.
Kustomize overlay: Using your original K8s resource files and extending them with a separate overlay that includes Velocity's annotations.
For better code reuse, we recommend using Helm or Kustomize since they allow you to keep Velocity's annotations in a separate overlay file, similar to the way you normally manage the production configuration.
Terraform, AWS Cloud Formation, Ansible, Pulumi, and other formats:
Your blueprint can also be created using these formats or others via Velocity Blueprint Plugins. For more details, contact our support at [email protected]