Kubernetes vs. Spinnaker

K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.

Incentivized

Spinnaker suits well for applications which are stateless and can adapt to an immutable architecture of deployment. But for applications which are stateful and cannot afford to spin up new servers for every deployment doesn't go well with Spinnaker. It can handle only deployments which are VM based and cannot support deployments to serverless architecture like AWS Lambda etc.

Incentivized

• Complex cluster management can be done with simple commands with strong authentication and authorization schemes
• Exhaustive documentation and open community smoothens the learning process
• As a user a few concepts like pod, deployment and service are sufficient to go a long way

Incentivized

• Fast deployments.
• Can be integrated with a good variety of other products.
• Also provides some insights from your environment.

Incentivized

• Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
• The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
• Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.

Incentivized

• It does NOT support CFN based deployments
• Windows based systems finds it difficult to onboard to Spinnaker.
• Pipeline level access authorisation is not there.
• Support for EBS volume encryption is probably missing.
• Attach/detach EBS volumes during deployments is difficult.
• No support to deploy the artifacts without re-creating the servers. Only pure immutable deployment are allowed.
• Open-source - so good and bad!
• Spinnaker on its own has 10 underlying micro services. Managing Spinnaker needs a focussed platform approach.
• User authentication is easy but authorisation management is not straight forward.

Incentivized

Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.

Incentivized

• Pipeline Expressiveness • Self-Service/Override • Visibility of Client Teams • Operability of Client Teams - • High-Quality Integrations (AWS, IHP, Google) • Extensibility – (Ability to add code) • The maturity of Deployment Process • Speed/Ease of Onboarding

Incentivized

• Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
• Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.

Incentivized

• By using Spinnaker we are able to deploy new versions of our product quickly.
• A deployment takes in average 2 minutes.
• Our investment on Spinnaker was just time learning it.

Incentivized