Kubernetes-native applications require careful planning for CI/CD pipelines to ensure confidence in shipping products with minimal onboarding complications. The team developed a pipeline using Kind for integration testing, semantic versioning for tagging products, and GitHub Pages for publishing Helm charts. They balanced automation with manual steps to achieve a developer-first approach, leveraging Travis CI (with migration to CircleCI) for orchestration. The pipeline consists of four stages: testing in a clean environment, ensuring non-conflicting merged branches, building the product, and publishing it to the public Helm chart repository. While improvements can be made, such as extending testing infrastructure or skipping manual steps before release, the team has built an excellent CI/CD pipeline that increases confidence in what is shipped.