Kustomize Deployment Strategy¶

Use your existing Kubernetes manifests and Kustomize overlays as deployment assets while Omnistrate provides the surrounding product, tenant, and deployment control plane.

When to Use Kustomize¶

• Your application is already described by Kubernetes manifests or Kustomize bases and overlays.
• You want to preserve your Git-based configuration structure rather than convert it to Helm.
• You need to connect deployment parameters, dependencies, and endpoints to your existing manifests.

Reference a pinned Git revision and Kustomize path from a Plan specification. Wrap raw manifests in a kustomization.yaml before onboarding. If an operator owns the application lifecycle, use the Kubernetes Operators strategy instead.

Strategy Guide¶

• Start with Build from Kustomize for the end-to-end tutorial.
• Use the Plan Specification to configure Kustomize sources and resources.
• Review Resource Dependencies and Deployment API Parameters when connecting multiple components.
• Follow the troubleshooting workflow to inspect rendered artifacts and deployment failures.

After building the baseline, return to Step 4: Test the customer journey and release process.