Aug 18, 2021
Automate your deployment into Kubernetes using OpsMx Spinnaker pipelines. With pipeline for canary and support for istiod, you can deploy safely into K8S.
seen from China
seen from United States
seen from Sweden
seen from United States
seen from United States
seen from United States
seen from United States
seen from China
seen from Ireland
seen from France
seen from Sweden
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from Australia
seen from Germany
Automate your deployment into Kubernetes using OpsMx Spinnaker pipelines. With pipeline for canary and support for istiod, you can deploy safely into K8S.
Overview of Canary Analysis using Kayenta for Spinnaker pipelines
Kayenta is the Spinnaker microservice that is responsible for enabling canary deployments in Spinnaker and performing automated canary analysis. Canary deployment is a release deployment strategy where a new release version is deployed alongside the stable running version.
It is exposed to a small subset of the end-users and then evaluated against the baseline (a copy of current deployment) to find out if the new release is stable and ready to be rolled out. The application config in Spinnaker has the configuration option to activate canary config and canary reports on Deck.
Kayenta supports monitoring tools like Stackdriver, Prometheus, Datadog, New Relic, e.t.c. Performing automated canary analysis with Kayenta involves two stages — Metric Retrieval and Judgement. Key metrics are retrieved from canary and baseline clusters, tagged, and stored in a time-series database.
This data is then validated, cleaned, compared and a score is then computed for each metric. An overall high score results in a favorable judgment for the canary or else it is failed. Please read the full blog “Overview of Canary Analysis using Kayenta for Spinnaker pipelines” to know more about the configurations and best practices for automated canary analysis using Kayenta.
Configure Slack notifications for Spinnaker pipelines
Slack is a popular communication and collaboration platform used widely in business for quick notifications and updates. Spinnaker supports sending CI/CD pipeline notifications to Slack.
In case a Spinnaker pipeline fails, DevOps teams could simply click on the link in a Slack notification and check for the reasons behind the failure. Spinnaker needs to be aware of the Slack bot’s identity (name & token) so that Spinnaker can communicate with the Slack bots and can automatically post notifications about Spinnaker pipeline information to a channel.
Read our blog “Configure Slack notifications for Spinnaker pipelines” to know about creating an app (bot) in Slack, adding/inviting it to a Slack channel, and know-how to configure Spinnaker to send notifications to Slack. To know more about this integration between Spinnaker CI/CD pipelines and Slack read our blog here!
Overview of Canary Analysis using Kayenta for Spinnaker pipelines
Canary Analysis is a deployment strategy for ensuring stable release where any change is partially rolled out and then evaluated against the current deployment i.e. baseline.
Kayenta microservice assesses the risk of a Canary release and checks for significant degradation between the baseline and Canary. Kayenta consists of two stages — Metric Retrieval and Judgement. Kayenta supports integration with APM monitoring tools like Stackdriver, Prometheus, Datadog, New Relic e.t.c. In the Metric Retrieval stage, Kayenta retrieves performance metrics from these tools. In the Judgement stage, it compares those retrieved metrics and makes a decision to pass or fail the canary release.
This is the best way to ensure that the software’s availability is not abruptly disrupted by the new releases and business can go on as usual. Read our blog “Overview of Canary Analysis using Kayenta for Spinnaker pipelines” to know more about Canary Analysis, Kayenta stages, and the best practices to configure Kayenta for ACA in Spinnaker pipelines. Read the blog now !!!
The blog to configure Spinnaker to trigger pipelines based on commits to a GitHub repository and inject changed GitHub files as artifacts into a pipeline.
Application deployment into multi cloud and hybrid cloud is now super easy with automated pipelines by Spinnaker. Learn how these pipelines can be abstracted and repurposed by multiple teams in an enterprise to handle thousands of application releases. #Spinnaker #Pipelines #JSON #Scale #Application #Delivery