#Spinnaker may be popular, but it has HUGE hidden cost when using with/on #Kubernetes.
1. The primitives are all IaaS-based
2. Many config changes require admin management and halyard reboot, meaning you need continuous deployment for your continuous deployment
1. The primitives are all IaaS-based
2. Many config changes require admin management and halyard reboot, meaning you need continuous deployment for your continuous deployment
3. There’s no abstraction for container platform in spinnaker, so you have to have a new “account” per k8s
4. There’s no namespace abstraction in Spinnaker, so you need a new account for each cluster+namespace permutation.
4. There’s no namespace abstraction in Spinnaker, so you need a new account for each cluster+namespace permutation.
5. If you use RBAC in K8s, you have to synchronize Spinnaker permissions manually or write a tool.
6. The usability cliff to use Spinnaker is multiplicative when combined with the usability cliff of K8s, making onboarding new team members a nightmare.
6. The usability cliff to use Spinnaker is multiplicative when combined with the usability cliff of K8s, making onboarding new team members a nightmare.
7. There’s no “config as code” solution that allows you to manage pipelines in the two with your service code.
8. Using the API requires manually configuring mTLS for 2FA and doesn’t support mobile authenticator options.
8. Using the API requires manually configuring mTLS for 2FA and doesn’t support mobile authenticator options.
9. Spinnaker wants to manage your load balancing for advance workflows, which is hard when every K8s provider uses a different configuration mechanism. If your private and public ingress are different stacks, good luck!
10. What’s Service Mesh?
10. What’s Service Mesh?
s/two/repo
