cbushko

16 ms·

121.
by cbushko 6y ago
For local development that debian container is fine but for production you want something small like scratch or alpine. The fewer binaries in the container, the better and more secure. This is one of the benefits of golang. You compile it i
122.
by cbushko 6y ago
I've been at this software thing for 20+ years and I could see a couple things happening based on your points but I mainly wish to address: 1. Senior engineer productivity Most companies have zero idea what to do with a senior engineer
123.
by cbushko 6y ago
Haha, it sounds like you have it covered. Even more so if you were to run on GKE (which I use and adore). When not to use it is a tough question. If I was ever in charge of a company, kubernetes would be the only way of running my product t
124.
by cbushko 6y ago
Hopefully tailscale gets to the size where kubernetes is worth it. It's a complex thing to run and understand but in the end I think it is worth it. It has certainly made my day to day life a lot easier and allowed our tiny team to bui
125.
by cbushko 6y ago
I upvoted because the content was technical, well written and different than what we normally see on HN.
126.
by cbushko 6y ago
I think a lot of people are missing the point that a traditional DB (MYSQL/Postgress) are not a good fit for this scenario. This isn't a CRUD application but is instead a distributed control plane with a lot of reads and a small d
127.
by cbushko 6y ago
This is why I use Terraform for my kubernetes objects. Yes, it is a DSL and not perfect but it has many advantages over helm such as: - State. I cannot express how useful having the desired and actual state of a system is. It makes it so mu
128.
by cbushko 6y ago
It must not fit your use case and that is ok. Kubernetes is made for the people that have to run your systems and keep them operational (ops/devops). It makes our lives a billion times easier on two fronts. Disclaimer, I am referring t
129.
by cbushko 6y ago
Could you expand on this a bit or point to articles that talk about it? It sounds interesting
130.
by cbushko 6y ago
You can tell by the volume of comments how interested in the topic the community is. I've noticed that there are a lot of replies such as "it is overhyped" and "I can just run a VM". Kubernetes is not for you as you
131.
by cbushko 7y ago
One of the reasons I recommend GKE over EKS is because of the lack of fees on the control plane. I guess that one advantage is gone now... Bad move Google Cloud. Bad move.
132.
by cbushko 7y ago
I think this depends on where you run kubernetes and how you set it up. We moved from AWS + ECS to GCP + kubernetes. We use and use terraform to set it all up so that consistency in tooling/patterns helps. We had one full time senior p
133.
by cbushko 7y ago
When that developer leaves you will still be saving 50%. It should pay for itself over the long haul.
134.
by cbushko 7y ago
We use terraform for our kubernetes app configuration and it works well. Being able to pass values from one resource to another is extremely powerful. For example, the database instance credentials down into cloudsql proxy. The only and mos
135.
by cbushko 7y ago
This is a decent article on how the load balancing between GCP loadbalancers and kubernetes works. We use terraform end to end and tried the http/https L7 loadbalancer first in our setup but I had a heck of a time with: - there is no A
136.
by cbushko 7y ago
It is easier because you can actually build that functionality locally with a docker container to test it out. This is coming from someone that spent 10+ years maintaining a build system that was a mix of makefiles and shell scripts. It can
137.
by cbushko 7y ago
Docker is the fatbinary that he is talking about. It supports all-the-languages and runs just about everywhere. The article ignores the fact that companies do not have the time, money, expertise, and desire to re-write their apps in a langu
138.
by cbushko 7y ago
We are eagerly awaiting GKE integration.
139.
by cbushko 7y ago
I do find that state management is a bit of a pain which is why I have the layered approach listed above. By keeping components/modules separate I am able to update things without worrying about breaking others. Each namespace has it&#
140.
by cbushko 7y ago
All of our services are containerized and running in kubernetes.
141.
by cbushko 7y ago
Something that really helped me convert our helm charts to terraform was this little tool that convert yaml to terraform HCL. I would just render out the helm template and convert it. Note: It uses the kubernetes terrform provider and onl
142.
by cbushko 7y ago
I do not understand what you mean by "how your software should be provisioned"? I have about 40 kubernetes services all as modules using the kubernetes terraform provider. I think I have 1000+ pods running on our one cluster all d
143.
by cbushko 7y ago
The terraform provider has caught up a bit in the last 6 months. It is still missing things like CRD support. For those things we use a direct kubectl yaml provider. I wish there was an istio provider!
144.
by cbushko 7y ago
I agree. Terraform and it's providers are unbelievably powerful for deployments. Being able to create any sort of resource and passing that information onto your kubernetes service to use is really great. An example would be creating a
145.
by cbushko 7y ago
I spent about 6 months using helm and made around 20+ charts for the services. In the end we got rid of it and replaced it with Terraform. If your infrastructure is 100% kubernetes then I think helm is great. Our infrastructure is not. We h
146.
by cbushko 7y ago
I have lived the first 1/2 of the article for the last 1.5+ years and have gone through that mental cycle. We've been moving our product from AWS to GCP. We have a custom deployment tool based of off Capistrano, Chef and Cloud For
147.
by cbushko 7y ago
Any tool that helps build infrastructure as code is great news. I hear good things about pulumi. In my case I have been moving our current infrastructure from AWS to GCP. After much evaluation and a small stint with Helm, we decided to go 1
148.
by cbushko 7y ago
I find this article to be a little frustrating. It is kind of like a layperson going to a mechanic convention and saying "all I heard about was engines, brakes and tires. Everyone is interested in tires". If you are not in the dom
149.
by cbushko 9y ago
Personally, I break everything down into 1 day sized chunks. It helps scope out the problem, creates a to-do and check list of what it takes to get the entire task done.
150.
by cbushko 9y ago
I have personally encountered this because while working on a legacy java code base. Maps were never used because java didn't even have maps until after 1.3 or 1.4. Our codebase pre-dated that by a long haul...

More ›