Benefits of Auto-Generated Manifest

This is the first method for configuring the deployment details in BuildPiper. For obtaining Auto-Generated Manifest via BuildPiper UI (Guided Form), you need to follow the steps listed below after signing in to the BuildPiper User Portal.

But, before we move further, let’s first read about why there is a need for Auto-Generated Manifest. Also know, how this approach helps in seamless, compliant & secure service deployment and empowers technology teams.

Why there is a need for BuildPiper Auto-Generated Manifest?

Although BuildPiper allows teams to bring their own manifest files (BYOM) for configuring the deployment details. But, a problem with this approach is that there is a constant need to upgrade the manifest according to the upgraded version of Kubernetes. Teams need to ensure that the manifest file is compliant and secure with the latest K8s version, whereas by using auto-generated manifest files via BuildPiper UI, there is no such requirement.

Auto-generated manifests via BuildPiper UI offers a standardized, secure, compliant, consistent, and reliable way to manage and deploy applications and services. The approach provides the following advantages.

• Empowers Technology Teams: Auto-generated manifest via BuildPiper UI (Guided form) enables the developers, QA engineers and DevOps to configure the services on Kubernetes on their own. There is no need for developers to possess an in-depth knowledge of Kubernetes.

• Provides Compliant Manifest: While using this approach, there is no need to upgrade the manifest file as per the latest version of Kubernetes. With the Kubernetes version upgrade, the product continuously upgrades itself. The product itself discovers the version of Kubernetes in action and accordingly, it automatically generates a compliant manifest.

How to Configure Deployment Details via BuildPiper Auto-Generated Manifest Approach?

You need to follow these simple steps in order to configure deployment details via this approach.

• Sign in to the User Portal -> Main Dashboard -> Service Overview.

• Select the Service that you want to Trigger.

• Click on “Configure Deploy Details”.

• Choose "BuildPiper UI" option for configuring the deployment process.

• Then, fill in and provide information regarding,

  • Access Level
  • Resource Quota
  • Configuration & Secrets
  • Environment Variables
  • Node and Service Affinity
  • Liveness/Readiness
  • Labels/Annotations
  • Custom Pre-Hooks and Post-Hooks

Read this documentation further to know about all the details required for successfully completing the deployment configuration process using this approach.

Click here to know how you can configure the deployment details via BYOM approach.