3 Common Spinnaker Challenges (and Easy Ways to Solve Them)

Spinnaker is the most powerful continuous delivery tool on the market. 

DevOps engineers and developers recognize this power and are looking to use Spinnaker as a foundational tool in their Continuous Integration and Continuous Delivery (CI/CD) process for hybrid and multi-cloud deployments.

Such a powerful, expansive open source tool needs expertise within your organization to set up, scale, and manage. Many organizations are willing to tackle these challenges head-on. Others, however, require assistance to take full advantage of Spinnaker for continuous delivery. If you focus and anticipate your organization’s needs before embarking on a continuous delivery transformation, you will see success with this powerful tool.

So what are a few common challenges developers face when adding Spinnaker to their CI/CD strategy? Let’s explore the challenges, and some easy solutions, in this blog post. 

Getting Up and Running

The most common challenge we hear with Spinnaker is simply getting started at your organization. Onboarding, optimizing, and iterating on the process all require your developers’ full attention. 

In the long-run, Spinnaker is an excellent CI/CD tool that saves time and automates manual efforts to more efficiently move your code and software into production. In the short-run, the first challenge will be to configure Spinnaker so that it fits into—and enhances—your tool stack. 

Here are some resources to help you get started with Spinnaker more quickly:

• Get Started Using Spinnaker – https://spinnaker.io/docs/guides/user/get-started/
• Open Source Spinnaker Training Series – https://www.youtube.com/playlist?list=PL4yLrwUObNktsYHFzJA9W3uF4PgRE6fPD 

Want to meet up with the Spinnaker Community? Spinnaker Summit is co-located with KubeCon this year! Join us in Detroit. Register here.