mm

To build and deploy a Go service using Bazel and Helm, you need a coordinated workflow that compiles the binary, creates an OCI image, pushes it to a registry, and applies Helm deployments using image digests. This ensures deterministic builds and consistent cluster releases.

Managing database migrations during a Kubernetes deployment requires running repeatable migration steps aligned with dev and prod constraints. You need a workflow that applies migrations safely during rollout and provides rollback mechanics to handle schema changes without breaking active deployments.

Pushing a Bazel-built OCI image to ECR involves building the image locally using Bazel, loading it into your local runtime, and then pushing the stamped image digest to the dev or prod ECR repository to ensure the deployment uses an exact, validated version.

Bazel works with Go toolchain outputs by coordinating the build environments to support both local iteration and hermetic CI-style builds. This coordination enforces deterministic build requirements so that locally validated changes behave consistently in automated CI pipelines.

Before building, you must run tests and lint checks, then generate any embedded UI, audit, or sqlc artifacts. This generation step ensures that the Go or Bazel build process compiles all necessary assets correctly into the final release or debug binary.

Digest-based deployments via Helm are needed to guarantee that the Kubernetes cluster pulls the exact OCI image version you validated. By referencing image digests instead of mutable tags, you prevent unverified code from running in dev or prod environments.