Local timeline

Replying to a post that is no longer available

@stfn @KevinGimbel this appears correct. The external IP will probably fill once the (local) cloud controller has ran it's reconcilation loop.

Replying to a post that is no longer available

@stfn I just noticed, wasn't able to view the screenshot correctly due to poor WiFi here. 8080 is the port of the NodePort service, but when exposing using the CLI command from your screenshot you're connecting to 8080 on the container, but this should probably be 80.

The NodePort service will do network forwarding from [random port] -> <clusterIP>:8080 -> <container>:80.

Replying to a post that is no longer available

@stfn @KevinGimbel

Judging from the YAML; the containerPort is 80, but you're trying to expose the deployment with port 8080.

Replying to a post that is no longer available

@stfn

It'll click once you put in some more miles. These are good questions :-)

LoadBalancer objects in Kubernetes are used by the cloud-controller to request actual Load Balancers from whatever cloud you're using. Since you're developing locally, there is none. Because of this, the external IP will stay Pending, and you can't reach the service using this.

For a single-node cluster, you'll want to use either NodePort (what you already figured out, nice!) or look up running the Ingress (NGINX) controller as a DaemonSet in "host mode". You can instruct NGINX to listen on the machine's ports 80 and 443.

You should read this to understand why. Details on using this through the Helm charts can be found here.

Replying to a post that is no longer available

@synq @systeemkabouter

Actually, yes. 90% of my day job is doing things with Kubernetes. I know a lot about scaling and cloud-architecture. I'd be happy to lend a hand.

Replying to a post that is no longer available

@synq @systeemkabouter

Awesome. I didn't know about Garage, so thanks for that. Thanks for the insights :)

Replying to a post that is no longer available

@synq @support @jelv

Ging voor mij om deze thread: https://social.jorijn.com/@jorijn/statuses/01JDKG3WSYS3ATPQV08T6PN3R4

Ik zie dat mijn eerste reply als veroordelend kan overkomen, was natuurlijk niet de insteek. Hier is nooit meer reactie op gekomen.

Replying to a post that is no longer available

@jelv @support

Ze zijn bezig met een migratie/proof of concept met Kubernetes. Alleen jammer dat er een defensieve houding is als je er vragen over stelt. :-)

Replying to a post that is no longer available

@mahryekuh interesting, how does this relate to posts on Mastodon written in Markdown?

  • one
  • two
  • three
Replying to a post that is no longer available
TV gif. Joe Minoso as Joe Cruz in Chicago Fire, seated, turns around with a WTF? look on his face.

@teufen my face when I noticed your recovery run pace is my threshold pace.

Replying to a post that is no longer available

@solarisfire damn, that games has some realistic graphics!

Replying to a post that is no longer available

@solarisfire OK I'll bite: How did you manage to take a picture of that plane?

Replying to a post that is no longer available

@hmblank Dit is iets waarvan ik niet wist dat ik het nodig had. :-)

Alvast gefeliciteerd.

Replying to @jorijn

@KevinGimbel @stfn also, nice! Best of luck. Kubernetes is super fun.

Replying to a post that is no longer available

@KevinGimbel @stfn

Tip: Stay away at operating Kubernetes for now. You should set up minikube or so. If you're serious about learning Kubernetes, do CKAD.

Good morning 👋☕️

Replying to a post that is no longer available

@me only for men :) single one shop I need

It’s nap time on this sunny #Caturday.

Replying to a post that is no longer available

@Karelgil ooh that's awesome! just a few hours more.. 🖨️

Webcam picture from the BambuLabs P1S cabin.
Webcam picture from the BambuLabs P1S cabin.

#3DPrinting the first board of the marble track built by #BambuLabs. I could've probably buy the thing, but it's pretty satisfactory to see it being built layer by layer.

Model can be seen here.

Load older posts