Discover and read the best of Twitter Threads about #spinnaker
Most recents (1)
#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.
