[HN Gopher] Container Training
___________________________________________________________________
 
Container Training
 
Author : thunderbong
Score  : 79 points
Date   : 2023-07-08 18:20 UTC (4 hours ago)
 
web link (container.training)
w3m dump (container.training)
 
| ChrisArchitect wrote:
| (2018)
 
| natsucks wrote:
| One does not simply deploy...
 
| dp-hackernews wrote:
| btw, Jerome Petazzoni is one of the very early adopters of
| docker, so while some stuff may seem a bit dated, it'll still be
| worth looking into...
 
| stargrazer wrote:
| this stuff is at least 4 years old
 
  | hooverd wrote:
  | Where can I learn the latest and greatest container practices?
 
    | benjaminwootton wrote:
    | Check out Bret Fishers courses and content -
    | https://www.bretfisher.com/
 
      | hooverd wrote:
      | Thanks. I'm excited to become a pod person.
 
    | dp-hackernews wrote:
    | This guy has pretty comprehensive and well rated courses for
    | docker and kubernetes - keep an eye out for sales with huge
    | value discounts on his courses...
    | 
    | https://www.udemy.com/user/mumshad-mannambeth/
 
      | hooverd wrote:
      | Thank you.
 
  | recursive wrote:
  | I see a 2021 in there.
 
    | ethbr0 wrote:
    | Docker, where 2021 content is 4 years old in 2023.
 
  | cbarrick wrote:
  | Have best practices changed since 2019?
  | 
  | I'm genuinely curious. Should I not consider this learning
  | resource?
 
| anderspitman wrote:
| I used to feel like docker wasn't worth the complexity but I've
| come around. It strikes a pretty dang good balance. Is kubernetes
| worth learning if you don't use microservices at work?
 
  | benjaminwootton wrote:
  | Docker is really easy. A few lines to describe your environment
  | and a handful of commands (docker build, run, ps, images) and
  | you are up and running.
  | 
  | Orchestration is more complex, but not too bad if you are using
  | a managed platform.
  | 
  | A few days and you can get your head around it enough to get
  | started with huge payback in efficiency.
  | 
  | After that, you can spend years really going deep on K8s and
  | fully containerised stacks, but that's more for DevOps/Cloud
  | engineers rather than Devs.
 
  | ericbarrett wrote:
  | _Using_ Kubernetes is a skill worth learning and is pretty
  | straightforward to pick up.
  | 
  |  _Running_ a Kubernetes cluster, in a shared environment (e.g.
  | not just a hobbyist or single-purpose cluster), is much more
  | involved. I 'd never say developing a skill isn't worth it, but
  | it is a deep subject with lots of unintuitive and frustrating
  | corners, and you won't pick it up in a day or without scars.
  | There's a reason lots of small- and medium-sized business just
  | write a check to their cloud provider.
 
  | [deleted]
 
  | theossuary wrote:
  | I'd say so. I've been using k8s as a basis for all my projects
  | for years. It's the best solution I've seen to the problem of
  | packaging and deploying apps. I have a kubespray cluster at
  | home that runs dozens of services flawlessly. Flux is the
  | easiest devops deployment system I've ever had.
  | 
  | For work, having minikube + skaffold is perfect for local dev
  | of complex apps. And it's easy to use production deployment
  | manifests with it. It's also easy to use Kind for running
  | integration and e2e tests. The ecosystem is second to none.
 
  | paulgb wrote:
  | If you're interested enough to be curious, it's worth sitting
  | down for a day with a mini kubernetes distribution and working
  | through the basics of pods, deployments, and services. They are
  | relatively simple conceptually (the hard part is grokking the
  | kubernetes way of doing things) but they give you a feel for
  | the way Kubernetes works.
 
  | jahsome wrote:
  | I don't think so. It's overkill for most stuff and probably not
  | particularly worth learning until you /need/ to.
  | 
  | If you're curious about orchestration concepts in general,
  | something like nomad is a nice way to wade into the pool rather
  | than the whirlpool of obscenity that is k8s.
 
    | bittermandel wrote:
    | I fully support this! Nomad has a much smaller API surface
    | compared to Kubernetes, at least by default. Expanding Nomad
    | is also much more straight forward.
 
    | abalashov wrote:
    | +1, Nomad is fantastically simple (but still flexible), and
    | gives you the proper level of insight into the nature of
    | orchestration and distributed container workloads without
    | bogging you down with arbitrary figments of "because
    | Kubernetes" complexity.
    | 
    | After spending a day with Nomad, I feel I fully understand
    | how this could get nightmarishly complicated in a Kubernetes
    | way, and what that would look like, and why someone would
    | want that in some situations. All the understanding without
    | pointless but exacting detours.
 
    | chromatin wrote:
    | Nomad is worth learning and something that can feasibly
    | orchestrate your containers at home, as well.
 
___________________________________________________________________
(page generated 2023-07-08 23:00 UTC)