Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker, Kubernetes, Terraform, and AWS crash course series

blog.gruntwork.io

Post reply on HN
Print view View original

51–60 of 84 posts

Re: Docker, Kubernetes, Terraform, and AWS crash course series

#51

Post by jen20 »

hotpotamus wrote: post #22
synergy20 wrote: post #19

Earlier quoted context omitted.

not sure if IaC will help, I'm just started reading about it. Indeed the cloud vendors are all lock-ins, something needs to be designed to mitigate the switching cost among cloud providers. Each one has its own SDK and own complicated infrastructures, so far it seems impossible to switch once you started with any one of them.

> so far it seems impossible to switch once you started with any one of them Do you think cloud vendors (FAANG companies) are fools who have accidentally created this situation? And do you think they will stand idly by while you try to abstract away the differences between them?

> And do you think they will stand idly by while you try to abstract away the differences between them?

Yes - letting people try something futile and fail is much better than telling them that it is futile.

Re: Docker, Kubernetes, Terraform, and AWS crash course series

#52

Post by jen20 »

lakomen wrote: post #32

Oh boy... Guys and gals, learn the basics. You don't need Docker, just a version control system (e.g. git). You don't need overpriced cloud offerings in the first place. First of all, pick the right language. For me, that's Go, because it has lots of performance for little resource usage. Docker is written in Go. Why would I put a Go proxy in front of my Go program to have nothing but what's essentially a zip file wi…

> Go can handle about 500 million visitors a month on 12 year old hardware per 1 server.

Doing what? I'm absolutely no fan of Kubernetes, or overcomplexity, but this is just meaningless platitude.

The feasibility of 12,000 requests per second (assuming evenly distributed throughout a 30 day month) largely depends on what the system is _doing_ for each of those requests.

Re: Docker, Kubernetes, Terraform, and AWS crash course series

#53

Post by k8sToGo »

tootie wrote: post #48
k8sToGo wrote: post #24

Earlier quoted context omitted.

Because then your endpoint is the standardized kubernetes rather than ECS. Also I don't think you can use Kubernetes logic with ECS Finally I think with ECS you have quite the vendor lock in.

Having deployed Dockerized services to ECS and Azure App Service, doing it from scratch twice is still easier than figuring out k8s.

If you don't know k8s, sure. But if you have someone who does, EKS makes more sense.

Re: Docker, Kubernetes, Terraform, and AWS crash course series

#54

Post by oxff »

cloudyporpoise wrote: post #47
oxff wrote: post #44

All these "you don't need X / Y / Z" points critically miss the point that it's irrelevant when that is what the companies hiring people want anyway.

Companies hiring the people probably also have a need if they are hiring and looking to grow and scale out. I made a "you don't need X / Y / Z" point because I strongly believe most people don't need these tools and really need a better understanding of Linux basics. You can also learn these tools on your own if they're mentioned in job descriptions of jobs you're applying for, but that doesn't mean you have to use t…

Using these tools in personal projects is how you learn them though, so you can talk about your experience, and maybe even show some prototype in an interview / CV etc.

Re: Docker, Kubernetes, Terraform, and AWS crash course series

#55

Post by cjalmeida »

elbigbad wrote: post #35
ericbarrett wrote: post #30

Earlier quoted context omitted.

> Maybe that is the answer ?? The fact that the middle-situations(lamp apps with low-med traffic) tutorials dont exists means i dont need it ?? SRE for 15 years with FAANG (MAGMA?) scale experience; I would argue this, yes. That's a little over 2 requests per minute. If you're cloud hosting then you could get away with single tiny hosts for your front end and DB, like t3.small on AWS, and Cloudwatch alarms for monito…

Our platform team got into k8s for some reason at my company. Because it’s enterprise there’s never really the “millions of requests per second” sort of problems because every deployment is single tenant. We have experienced k8s engineers who I guess we’re just using the tools we know, but wow it’s been such a hassle and has caused so much toil. Right now we’re having trouble scaling back ends for parallel jobs with…

On enterprises, k8s solves a different kind of scaling problem. You tend to have hundreds of apps that are business critical and need to be managed.

K8s provides a consistent way to package, deploy with HA and monitor those apps. Ideally it replaced tons of ad-hoc scripts and confluence pages that are very poorly maintained.

Re: Docker, Kubernetes, Terraform, and AWS crash course series

#56

Post by BossingAround »

waynesonfire wrote: post #45
BossingAround wrote: post #2

Kubernetes must probably be one of the most tutorialized pieces of SW out there. You want a "crash course" on the platform of your choice? You got it. You want it for the price of your choice? You got it. The docs are great [1] and offer even interactive parts [2]. There are a ton of good materials on youtube. There are Coursera and EdX courses, e.g. [3] from Google and [4] from Red Hat. There are a ton of Udemy cour…

I just don't want to do that, no thanks. I've spent so much time learning about how an OS can solve these problems and these lessons have paid dividends many times over my career. Instead, I will continue to invest in the core foundation. I'm not interested in re-learning these abstractions reading [1]-[5] tutorials plus many more and studying an unrefined, new layer of complicated abstractions built on top of the OS…

That sounds like a bit of an extreme reaction to what seems to be a "this technology is yucky and I don't like it" problem.

Re: Docker, Kubernetes, Terraform, and AWS crash course series

#57

Post by BossingAround »

starkd wrote: post #5
BossingAround wrote: post #2

Kubernetes must probably be one of the most tutorialized pieces of SW out there. You want a "crash course" on the platform of your choice? You got it. You want it for the price of your choice? You got it. The docs are great [1] and offer even interactive parts [2]. There are a ton of good materials on youtube. There are Coursera and EdX courses, e.g. [3] from Google and [4] from Red Hat. There are a ton of Udemy cour…

This is no doubt a useful commment, since you provide other sources. However, it's not particularly a mark of courtesy to denigrate others' contribution to the space. If you had substantive criticism of the OP offered tutorial, it might be helpful. However, you offer none.

I can see your point. Thanks for your comment, I'll try to restate my point next time.

Re: Docker, Kubernetes, Terraform, and AWS crash course series

#58

Post by waynesonfire »

BossingAround wrote: post #56
waynesonfire wrote: post #45

Earlier quoted context omitted.

I just don't want to do that, no thanks. I've spent so much time learning about how an OS can solve these problems and these lessons have paid dividends many times over my career. Instead, I will continue to invest in the core foundation. I'm not interested in re-learning these abstractions reading [1]-[5] tutorials plus many more and studying an unrefined, new layer of complicated abstractions built on top of the OS…

That sounds like a bit of an extreme reaction to what seems to be a "this technology is yucky and I don't like it" problem.

No, you're way off. Maybe my reaction is extreme, but my problem isn't. What's yucky is that you're trying to convince people that reading five tutorials on k8s will make them productive. No, the problem, and I'll repeat it since you conveniently skipped over it, k8s requires 10+ engineers to maintain and manage, full time.

_I_ don't have 10 engineers and thus it's the wrong tool for me and I've decided to not invest in it.

Re: Docker, Kubernetes, Terraform, and AWS crash course series

#59

Post by MuffinFlavored »

davewritescode wrote: post #50

I can’t think of a worse way to manage Kubernetes than Terraform. After years of running into issues, I think it’s really only suitable for small clusters. ClusterAPI has been the way my company has been doing things lately and I can honestly tell you it’s been transformative. https://github.com/kubernetes-sigs/cluster-api There’s nothing more amazing that updating a kubelet version in a git repo and watching Cluster…

How does ClusterAPI compare to Helm charts (or just managing Kubernetes YAML manually or through Kustomize?)

Why do you need clusterctl / clusterawsadm? Can't you just kubectl apply once you have your .kube/config set up for your AWS k8s cluster (or Azure or GCP or whatever)?

Re: Docker, Kubernetes, Terraform, and AWS crash course series

#60

Post by MuffinFlavored »

rawoke083600 wrote: post #4
BossingAround wrote: post #2

Kubernetes must probably be one of the most tutorialized pieces of SW out there. You want a "crash course" on the platform of your choice? You got it. You want it for the price of your choice? You got it. The docs are great [1] and offer even interactive parts [2]. There are a ton of good materials on youtube. There are Coursera and EdX courses, e.g. [3] from Google and [4] from Red Hat. There are a ton of Udemy cour…

To be fair. Just last night i was googling kubernetes and k3s tutorials. All of them on page 1 of SERPS are super simple and brilliant and ONLY show you how to add nodes to clusters. Ok now what ?? Ive drank the k-Koolaid signup for the newsletters but how do i get value from this 'thing' ??? When i code a webapp how do setup/config the db ? How do I do a regular LAMP app ? Lol i never thought i say this but i need a…

> SERPS

Search Engine Result Pages

Post reply on HN