• 1 Post
  • 54 Comments
Joined 3 years ago
cake
Cake day: June 30th, 2023

help-circle
  • Yeah for reference I’d probably never run the full open source Kubernetes distribution unless I had to, and that would mean having access to millions of dollars of hardware in a datacenter.

    K3s is a lightweight Kuberbetes distribution that implements the full Kuberbetes API (full-ish? Maybe?). It’s super easy to run on Linux, I run a 3 node cluster with GPUs at home. Its only real downside is the backend is a single point of failure, but that’s ok for me cause it’s run from my storage node with all the disks, so if that disappears I have bigger problems.

    There are others like microk8s which can handle control plane failures, but it’s for that reason that I also dislike it - they wrote their own distributed sqlite instance and it failed on me, a story for another time.

    Minikube can run on your desktop, it’s also an option.

    But if you have docker desktop, you also have a built in Kuberbetes API server too, just have to enable it with one checkbox (not a full API server, but good enough for installing helm charts).

    Kind is a docker based Kubernetes server but I think that’s in the realm of testing not running. I believe K0s is in this camp too but could be wrong.

    At work the daily driver will be one of EKS, GKE, AKS, or whichever cloud providers implementation. They’re effectively free and a loss leader because you’ll pay for instances anyway (at least on EKS, I’m most familiar with that one).

    But if you’re interested in learning, start with docker desktops k8s API, or minikube, or k3s if you have a Linux host or raspberry Pi lying around.

    🌈The more you know!🌈










  • Are you running coredns in your cluster? This sounds like a Corefile change but maybe it’s just missing a service?

    Pods won’t have any entries in DNS aside from the pod IP addresses you’ve found. A Service will be in DNS and should have several entries depending on the namespace you’re calling from, eg:

    service-a
    service-a.namespace
    service-a.namespace.svc.cluster.local
    

    I’m on mobile so haven’t looked above to see if you’ve created a service for the pod. A service will have endpoints which are the pod ips and ports (and you can ignore endpoint slices for now)

    Edit: I see coredns in there now. I’d check Corefile or the kubelet configs, seems like it can contact DNS because you’re getting an NXDOMAIN response at least.




  • Not surprising. There’s a part of the Shopify careers site that has a letter you have to acknowledge that says (paraphrased): Care more about the ability to sell than what people sell, and if feel you might disagree with what people sell then this isn’t the workplace for you. They really drill that point home on the site and in interviews, not surprising their stance is ‘no comment’.

    (I didn’t get the job)






  • It’s a shortcut for experience, but you lose a lot of the tools you get with experience. If I were early in my career I’d be very hesitant relying on it as its a fragile ecosystem right now that might disappear, in the same way that you want to avoid tying your skills to a single companies product. In my workflow it slows me down because the answers I get are often average or wrong, it’s never “I’d never thought of doing it that way!” levels of amazing.




  • dimeslime@lemmy.catoComic Strips@lemmy.worldXXX
    link
    fedilink
    arrow-up
    24
    ·
    2 years ago

    I’m a lefty but my teachers never knew how to handle a lefty so my handwriting is also illegible. I had to go do handwriting basics (“colour in the enclosed area of the A shape”) in high school.

    So mileage may vary even if leftyism is tolerated. But look at me now teachers! I type obscure commands all day and get a sore hand when I pick up a pen! Checkmate!