Deploy Anywhere using the OpsMx Enterprise for Spinnaker Anywhere Agent

Across many organisations, each development team uses one or more Kubernetes clusters (on-premise, VPC, hybrid, etc) as their target environments for their application deployments and Spinnaker as their preferred tool for continuous delivery.

When Spinnaker is installed locally in a shared services cluster, it usually has access privileges to these clusters and can carry out deployments easily.

But often it is found that the Kubernetes clusters are spread across multiple security zones. Spinnaker’s default configuration does not support it to deploy into different security domains. Enterprise security policies often prevent Spinnaker from accessing the targeted Kubernetes cluster from an external location.

Some of the common scenarios where this happens are:

• Using cloud-based Spinnaker to rollout deployments to on-premise environments
• Using a central and shared Spinnaker service that will need access privileges for:
• Deploying into multiple security domains for multiple teams
• Deploying into a new K8 environment
• Kubernetes cluster admin needing to exercise access control
• Single teams need to deploy across multiple security domains (different geo-locations)

The OpsMx team provides a perfect solution to address these situations. The OpsMx Enterprise for Spinnaker (OES) addresses these challenges through the use of the OpsMx Enterprise for Spinnaker Anywhere agent. To know more, please read our blog “Deploy Anywhere using the OpsMx Enterprise for Spinnaker Anywhere Agent”.