mad_vill

9 ms·

1.
by mad_vill 4mo ago
Happy to see this trending, I probably share this in my company's slack once a month.
2.
by mad_vill 1y ago
For all the other comments, parent is probably talking about forward proxies and to their point many forward/enterprise proxies have configurations which cause websockets to break and it is a pain to debug this if you have many enterpr
3.
by mad_vill 2y ago
There are many cases where users are behind a forward proxy for security/compliance reasons. Most applications need to support these types of users.
4.
by mad_vill 2y ago
cluster-api in a nutshell
5.
by mad_vill 2y ago
Same. Typically call it “hung” but maybe stating certmanager is on strike will get the point across better. But sigh does it really get to the state of the kubernetes ecosystem. All these projects need to be operated, can’t just set it and
6.
by mad_vill 3y ago
Curious if oxide is considering a 1-2U product. Feel like there is a larger potential customer base there but it also seems like they would lose the edge they built by owning the full rack. (I.e. integrating with customer TORs and network f
7.
by mad_vill 3y ago
“Automatic recovery” That’s a joke.
8.
by mad_vill 3y ago
I am really curious if part of the reason why oxide is leaning into racksize is that joyent has scared them from attempting a 1U/2U solution.
9.
by mad_vill 3y ago
they did more than just CICD but I see your point.
10.
by mad_vill 3y ago
I feel like the next generation of this type of company is smaller consultancies that have awesome developers that build customer tooling on the side. But the main revenue driver is consultancy. Also it really feels like all the air has be
11.
by mad_vill 3y ago
oh wow ... can't wait to waste a bunch of time trying to get this running in hyper-v.
12.
by mad_vill 3y ago
Sounds more like a kubernetes problem than a dns problem. I hate coredns. Everything running inside of a kubernetes cluster should just be querying the kubernetes endpoints api for these IPs directly and using the node dnsservers for extern
13.
by mad_vill 3y ago
Bingo. Design for incompetence. There are few codebases in this world that don't need incompetent people to contribute to them. (This is typically driven by business incentives) If you get to work on one of those codebases ... good for
14.
by mad_vill 3y ago
iirc azure stack hci is only 1U and 2U configurations, not a full 32U rack.
15.
by mad_vill 3y ago
If you want to get an HA k3s cluster going quickly on your cloud-provider of choice: https://github.com/cluster-api-provider-k3s/cluster-api-k3s
16.
by mad_vill 3y ago
Well I notice that alias from the propolis repo :). Thanks for the heads up. Will probably ditch this effort. Really want to play around with some of the oxide stuffs but it’s hard with illumos not supporting nested virt.
17.
by mad_vill 3y ago
It’s funny this article popped up. I have been trying to get the oxide vmm working on freebsd in my spare time. Too bad I don’t know nearly enough about rust, bhyve, openbsd or illumos to ever come close to get this working.
18.
by mad_vill 3y ago
Looks really cool!
19.
by mad_vill 3y ago
well put. it was already a headache trying to unblock devs that went down terrible stack overflow copy/paste rabbit holes ... gpt4 only 10x that mess.
20.
by mad_vill 3y ago
The verge is doing a great job approaching the new AI tools from a non-software engineer technically technically inclined knowledge worker POV.
21.
by mad_vill 4y ago
makes sense ... karpathy is a pragmatic thinker. openai seems like a pragmatic company. Can't wait to see want gets built.
22.
by mad_vill 4y ago
The lack of detailed documentation for grpc is pretty crazy considering how many people seem to be using it. So many hours wasted investigating fringe http2 characteristics causing odd bugs on the platform.
23.
by mad_vill 4y ago
This is touching on something I have been thinking a lot about as I progress in my career. The thing good and bad code have in common is the fact that it needs to updated. Either for bugs or changing business need. So focusing on the operat
24.
by mad_vill 4y ago
What about companies that sell you on "If you come on, you will do it", and then you get there and it turns out you won't be doing "it" at all?
25.
by mad_vill 5y ago
the issues I see with kubernetes ingress are more related to an ingress pod going down than the upstream.
26.
by mad_vill 5y ago
I thought they shutdown their public api.
27.
Show HN: Deploy and Manage K3s Clusters with ClusterAPI(github.com)
2 points by mad_vill 5y ago|0 comments
28.
by mad_vill 5y ago
I would be pretty skeptical of anything that is owned by the devdiv division (github, dotnet, etc). It seems like they are still looking for ways to replace the revenue they lost from the classic VS model. As for anything in the Azure org,
29.
by mad_vill 5y ago
uw madison?
30.
by mad_vill 5y ago
Who needs this when you have the broken "blame" in azure devops/repos?

More ›