Hey peeps, my team at #Oda is hiring! If you enjoy working with a variety of nerds and non-nerds in an inclusive and open culture and have some experience with #infrastructure engineering, click on the #job link! We're more into how you think than what stack you have experience with. You don't have to live in #Norway to apply.
My first #retrocomputing YT video will be titled “How I Got #Kubernetes to Run on An #Amstrad#PCW” and the video will be me just laughing and shaking my head and mouthing “nope”
I saw this tweet by @dberkholz (hi btw, long time no see; I hope all is well!), and I'm not sure which one of the 4 big cloud providers is being singled out. :)
I recently wrote #Terraform configurations to deploy (simple) #Kubernetes clusters on a dozen of cloud providers; and Oracle was not the worst experience - very far from it.
In fact, that exercise gave me the impression that if anything, Google and AWS just hate developers 😬
A new ICSNPP-Synchrophasor parser for Synchrophasor Data Transfer for Power Systems (IEEE C37.118) has been integrated.
We've also got a plethora of component version updates, including Arkime to v4.3.0, Capa to v5.1.0, Fluent Bit to v2.1.2, NetBox to v3.5.0, NGINX to v1.22.1, Supercronic to v0.2.24, Suricata to v6.0.10, Yara to v4.3.0, and Zeek to v5.2.1.
Check out the release on GitHub or grab my ISO builds at malcolm.fyi.
This is still in the realms of dirty hacks, but might actually be useful to people now :)
I refactored my #Kubelet configuration dumping utility to use the /configz endpoint via the #Kubernetes API Server proxy.
This means you can dump the configuration of any Kubelet regardless of the distribution in use.
The previous method relied on starting pods on the nodes and reading files but that's error prone as they are put in different paths depending on the distro.
The endpoint is a bit unsupported/undocumented, but for now at least it works fine :)
my coworker is getting a kubernetes error, connection refused to 6443 but it's intermittent. it works fine and then suddenly it's nonstop connection refused. He created a control plane and a node and it connects but then it refuses connection. We've tried everything, there's no firewall, he ran init, not sure what else to check here. He's doing the trial aws $5 thing I believe.
Any ideas? I've never used kubernetes so I have no clue.
If you wanted to protect a high availability #kubernetes or similar #cluster#webserver#server from #hacking, would it be advantageous and possible to use sufficiently different #Linux versions for each #node so that not all nodes have the same #vulnerabilities. Which Linux versions would be most different & so most unlikely to suffer the same vulnerabilities or #vulnerability yet work together somehow? Would using a #riscv node with an #arm node & an #intel node offer any #security advantages?
I have been struggling with #Traefik for the better part of two days now.
Any services in my #Kubernetes cluster that happens to be hosted on port 80 can be accessed through Traefik. (whoami, nginx)
Any service where the container is not running the service on port 80 gives me a 503. (jellyfin, teamcity, even an ingress to traefik's admin panel on port 8080)
I cant for the life of me understand what is going on. My deployment, service, and ingress definitions all line up.
I've tried connecting the dots by name, and by explicit port number.