1 views collected around this technical thread.
GitOps is a set of best‑practice principles that treat a Git repository as the single source of truth for declarative infrastructure and application code, enabling faster, auditable, and automated deployments to Kubernetes clusters, and can be realized using tools like OpsMx Enterprise for Spinnaker.
This guide explains how to obtain the latest stable Spinnaker version, run a GitHub Actions pipeline that pushes Docker images to Docker Hub, retrieve the resulting Spinnaker configuration files, and provides links to a detailed Spinnaker continuous‑delivery tutorial and QR‑code access.
GitOps is a set of best‑practice principles that treat Git as the single source of truth for declarative infrastructure and application delivery, enabling faster, auditable, and automated deployments on Kubernetes clusters, and can be realized with tools like OpsMx Enterprise for Spinnaker.
This article explains the concept of progressive delivery, its industrial origins, how cloud‑native tools like Kubernetes, Traefik and Spinnaker enable automated A/B testing, canary and gray releases, and the practical benefits for developers, operations, and product teams when releasing features to millions of users.
This article explains how Spinnaker enables continuous delivery in Kubernetes environments by describing its role, deployment workflow, micro‑service architecture, pipeline design across DEV and UAT namespaces, and practical best‑practice recommendations for secure and efficient CD operations.
This article examines Netflix’s open‑source Spinnaker platform, detailing its microservice architecture, GitHub‑based code management, GitHub Actions continuous‑integration workflow, and Halyard‑driven deployment process, including sample build.yml and version.yaml configurations, offering practical insights for cloud‑native DevOps implementations.
This article explains how Spinnaker enables continuous delivery on Kubernetes by describing its role, architecture, pipeline design, workflow steps, and best practices for deploying applications across multiple cloud providers in a cloud‑native environment.
This article provides a comprehensive guide to Spinnaker, covering its role in Kubernetes, integration with cloud providers, detailed architecture, pipeline design, workflow steps, and best practices for implementing continuous delivery in cloud‑native environments.
This guide walks through the complete deployment of Spinnaker on Kubernetes using Halyard, covering architecture analysis, preparation of Redis, MySQL and MinIO, container image retrieval, BOM preparation, Halyard configuration, external Redis and SQL database integration, authentication, canary analysis, monitoring, and additional settings.
This article explains Netflix's Spinnaker platform, detailing its microservice architecture, code repository management, GitHub Actions continuous integration workflow, versioned deployment configuration, and practical steps for deploying and rolling back Spinnaker in multi‑cloud environments.
Continuous delivery is a practice that enables rapid, safe, and automated software releases, reducing deployment pain by encouraging frequent, small changes, automating pipelines, fostering self‑service, visibility, and reliability, with examples and lessons drawn from Netflix’s implementation and its impact on developer productivity.
This guide walks through installing the Spinnaker continuous‑delivery platform on a Kubernetes 1.16+ cluster using Helm 3, covering environment preparation, Helm chart adjustments for API version compatibility, storage class configuration, proxy settings for Halyard, and exposing the service via Traefik IngressRoute.
Spinnaker, Netflix’s open‑source continuous‑delivery platform, enables cloud‑native microservice teams to automate, test, and deploy applications across multiple clouds with features like blue‑green and canary releases, a modular microservice architecture, Slack notifications, Chaos Monkey integration, and Artifactory package management.
The article explains Netflix's end‑to‑end build and deployment pipeline, detailing how Nebula, Jenkins, Spinnaker, and AWS are combined with a culture of cloud‑native microservices to deliver code from local compilation to immutable AMI‑based releases across regions in about sixteen minutes.