Skip to main content

Set up Deploy Details

For deployment configuration automation BuildPiper has 2 approaches:

1. Automated Manifest Generation via Guided Form(Buildpiper UI) : By asking a few questions about your service deployment, Buildpiper allows you to generate a compliant, secure, scalable, and reliable service manifest, which can be transparently utilized for the service deployments.

2. Manifest/Helm-based definition : With Buildpiper, you can easily configure the CD details by uploading your custom manifest file. If you already have Manifests or a Helm and values file, you can provide the file or the Git URL and we’ll use the same to automate deployments.

Docs Version Dropdown

Automated Manifest Generation via Guided Form(BuildPiper UI)#

Choose Access Level#

Specify the access details and fill in the required information.

1. Add service name.

2. Add image name.

3. Fill in the deployment name.

Docs Version Dropdown

4. Choose the access level. Buildpiper offers multiple options to securely manage access with custom ingress rules for public, protected, and private traffic on the services. All you need to do is,

  • Select Ingress
  • Enter the URL details.
  • Specify the expose path.
  • Fill in the port details.

5. Finally click on continue to proceed further.

Docs Version Dropdown

Set Resource Quota#

6. Fill in the Resource Memory Quota.

7. Specify the Request CPU Quota. Buildpiper provides the option to specify the limit quota.

8. Unlike any other Microservice management platform, BuildPiper provides UI-driven options to make the services auto-scalable. All that you need is to mention,

  • Minimum Replication- the minimum number of pods that need to be replicated.
  • Maximum Replication- the maximum number of pods that can be replicated.
  • CPU Threshold- Specify and allocate the CPU quota.
  • RAM Threshold- Specify and allocate the memory quota.

9. In case you don’t want to make the service auto-scalable, you can define the desired replica count. The count you specify here will be the number of pods your service will be replicated on, irrespective of the load that it receives.

Docs Version Dropdown

Configuration and Secrets#

Buildpiper supports comprehensive manageability with automated log shipping, secrets, config maps, and service access management. With BuildPiper’s focus on Day 1 & 2 operations, the manageability of production-ready services becomes very simple with pre-configured features such as Config Maps, Secrets, automated log shipping, autoscaling, and secrets management!

10. Config Maps : Users need to select the ConfigMap name and then specify the volume mount path.

11. Secrets : You can select the secret’s name and then specify the volume mount path.

12. Custom Entry Point : Enter the command if there exists a custom entry point.

Docs Version Dropdown

Define Runtime Environment Variables#

13. Specify and define the key-value pairs for seamless configuration of deployment details.

14. Add configMap details via these simple steps.

  • Add Service Key.
  • Choose the ConfigMap name.
  • Specify the ConfigMap key.

15. Define and add Secrets details through these easy steps.

  • Add Service Key.
  • Select secrets name.
  • Specify secret key.

Docs Version Dropdown

With this simple input information, you can easily set up the deploy details through UI-driven options on the Buildpiper platform. All you need is to provide these details.

  • Node and Service Affinity
  • Liveness/Readiness
  • Labels/Annotations
  • Hooks

Docs Version Dropdown

Manifest/Helm-Based Definition#

With Buildpiper, you can easily configure the deployment details by uploading the custom manifest file. If you already have Manifests or a Helm template and values file, you can provide the file or the Git URL and we’ll use the same to automate deployments.

With these simple and intuitive steps, you can avail seamless configuration of CD details.

1. Specify a name for the Deployment process.

2. Enter the Service Name that you want to deploy.

3. Enter the image name.

4. You can configure deploy details via,

  • Manifest File Upload
  • Git URL
  • Helm Templates

Docs Version Dropdown