Hacker Newsnew | past | comments | ask | show | jobs | submit | rifelpet's commentslogin

There's a KubeCon North America talk (also from 2019) that goes into more detail on this very issue including some additional recommendations

https://youtu.be/0o5C12kzEDI?t=57


Location: USA (Central Time)

Remote: Yes (only)

Willing to relocate: No

Technologies: Kubernetes, AWS, Terraform, GitLab CI, Golang, Python, Ansible, Linux, Shell scripting

Email: pgrifel at gmail / https://github.com/rifelpet / https://www.linkedin.com/in/peterrifel/

I have 7 years of experience in DevOps / Platform / Site Reliability Engineering. I'm a maintainer of Kops (a Kubernetes cluster management tool) and have years of experience building and maintaining self-serve CI-based solutions for Kubernetes clusters and cloud resource management with Terraform. I've worked to significantly improve reliability of high volume services (>15k req/sec) and their underlying infrastructure. I've helped reduce outage frequency and impact while also reducing lead time on infrastructure needs through automation and the aforementioned self-serve solutions. I can facilitate engineering team growth by helping establish infrastructure patterns for success.


They're addressing the lack of service accounts, targeted for 13.1:

https://gitlab.com/gitlab-org/gitlab/-/issues/6883


Yep, we want to charge only for people, not bots. Sorry it took a while to resolve this, it was complex.


I’m really glad you’ve reached this decision, but I’m still not happy with being asked “why are these automation tasks costing us $XXX” per year during our last recent license license update.

Until this epic is completed you are charging people full-seat price for automation users which, because of the poorly-scoped token permissions, require multiple “user” accounts to implement securely.

An automation utility in no way delivers the same value as a full time developer and it really shook me to know that this is how you have historically valued bots. It runs counter to everything that you publicise.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: