Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
MathiasPius
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
31.
▲
by
MathiasPius
3y ago
My solution for this setup is having ingress controllers on all three nodes, and then specifying all three IPs in all DNS records. That way the end user will "load balance" based on the DNS randomization. Of course, if a node goes
32.
▲
by
MathiasPius
3y ago
When it comes to load balancing, I think the hcloud-cloud-controller-manager[1] is probably your best bet, and although I haven't tested it, I'm sure it can be coerced into some kind of working configuration with the vSwitch/
33.
▲
by
MathiasPius
3y ago
Hetzner Cloud is officially supported, but that means setting up VPSs in Hetzner's Cloud offering, whereas this project was intended as a more or less independent pure bare-metal cluster. I see they offer Bare Metal support as well, bu
34.
▲
by
MathiasPius
3y ago
I rand rados benchmarks and it seems writes are about 74MB/s, whereas both random and sequential reads are running at about 130MB/s, which is about wire speed given the 1Gbit/s NICs. Complete results are here: https:/&#
35.
▲
by
MathiasPius
3y ago
I haven't had an excuse to test it yet, but since it's only 6 OSDs across 3 nodes and all of them are spinning rust, I'd be surprised if performance was amazing. I'm definitely curious to find out though, so I'll ru
36.
▲
by
MathiasPius
3y ago
I haven't had much opportunity to work with Docker Swarm, but the one time I did, we hit certificate expiration and other issues constantly, and it was not always obvious what was going on. It soured my perception of it a bit, but like
37.
▲
by
MathiasPius
3y ago
Absolutely! If at all possible, go managed, preferably with a cloud provider that handles all the hard things for you like load balancing and so on. *Sometimes* however, you want or need full control, either for compliance or economic reaso
38.
▲
by
MathiasPius
3y ago
Have seen age pop up here and there, but haven't spent the cycles to see where it fits in yet, so I just went with what I knew. Will definitely take a look though, thanks!
39.
▲
by
MathiasPius
3y ago
I believe the recommended[1] way to deploy Talos to Hetzner Cloud (not bare metal) is to use the rescue system and Hashicorp Packer to upload the Talos ISO, deploying your VPS using this image, and then configuring Talos using the standard
40.
▲
Bare-Metal Kubernetes, Part I: Talos on Hetzner
(datavirke.dk)
214 points
by
MathiasPius
3y ago
|
77 comments
41.
▲
by
MathiasPius
3y ago
I recently rebuilt my Kubernetes cluster running across three dedicated servers hosted by Hetzner and decided to document the process. It turned into a (so far) 8-part series covering everything from bootstrapping and firewalls to setting u
42.
▲
Fallible – The lost sibling of Result and Option
(datavirke.dk)
3 points
by
MathiasPius
4y ago
|
0 comments
43.
▲
by
MathiasPius
4y ago
One way in which it is useful, is that you can tag your build artifacts (like docker images) with the commit id in the development branch, and just re-tag them when you want to promote the artifact to main or production, or whatever. Withou
44.
▲
by
MathiasPius
5y ago
The Rust formatting macros depend on string literals because the macro expansion necessarily happens at compile-time, which means that it's not possible to override the actual format string at runtime, nor is recursive resolution possi
45.
▲
by
MathiasPius
5y ago
It's so that a reader of the calling code can immediately reason about which calls might be mutating state. If you have 10 calls, all taking &bytes, any of which may or may not be mutating the data while others are merely reading i
46.
▲
by
MathiasPius
6y ago
How do you know that the first certificate was not produced by the MitM?
47.
▲
by
MathiasPius
6y ago
And if the international community had been more critical of the US claims on the alleged weapons of mass destruction of Saddam Hussein, 2 decades of war and the deaths of millions could likely have been avoided. It's not as black and
48.
▲
by
MathiasPius
6y ago
A custom tld is only custom until it's not (see .dev, .corp), and using them for intranet purposes is widely regarded as bad practice. If you're already serving regular content over HTTPS internally, then I don't see the big
49.
▲
by
MathiasPius
6y ago
In regards to point number 2: the Name Constraints extension[1] appears to be getting more support, at least in Chrome and Firefox on non-OSX devices[2], which could help mitigate the very serious vulnerability presented by installing root