Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shosti
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
shosti
3y ago
https://www.iea.org/reports/direct-air-capture-2022/executiv... suggests $125-$335 per ton, so not quite an order of magnitude but still a big difference for CCS.
2.
▲
by
shosti
3y ago
> According to [2], the cost to reclaim CO2 from natural gas sources is approximately $90 per ton on the high end I may be reading that wrong, but I'm pretty sure that refers to the CCS cost when you capture at use (e.g. in a power
3.
▲
by
shosti
3y ago
It's buried in the article, but the 77% number seems to be based on resistance heating instead of heat pumps: > the annual energy bill to operate a standard gas furnace/AC combination is about $633 a year. With a heat pump, she
4.
▲
by
shosti
5y ago
Ingresses on EKS will set up an ALB that sends traffic directly to pods instead of nodes (basically skips the whole K8s Service/NodePort networking setup). You have to use ` alb.ingress.kubernetes.io/target-type: ip` as an annotat
5.
▲
by
shosti
5y ago
The ingress controller is so I can have multiple public apps and configure them with Ingresses (definitely possible to do the overall setup with just cloudflared but I wanted to use built in ingress objects instead of a complicated cloudfla
6.
▲
by
shosti
5y ago
I feel like Tailscale gets you pretty close to an “easy private cloud”, it’s just the “public” part that’s still a bit tricky.
7.
▲
by
shosti
5y ago
Yeah this is basically what I was planning to do before I learned about cloudflared.
8.
▲
by
shosti
5y ago
Yeah that’s what I would do if I was just hosting a blog, I already had the k8s lab set up for other reasons and wanted to get more use out of it.
9.
▲
by
shosti
5y ago
I would say you don't really need Kubernetes for this sort of setup (I already was running all the K8s stuff which is why I went with it, but docker compose or even just running things in systemd without containers would work too). I t
10.
▲
by
shosti
5y ago
(Author here) I mostly worry about security for this. If you have nothing private on your network it's probably fine, but if you have, say, a NAS that isn't using proper authentication (pretty common), an os/nginx vulnerabili
11.
▲
by
shosti
5y ago
(Author here) I’m kind of cruel to my hardware lol (they’re all frankenservers hacked together with random parts from eBay). I’m not doing anything fancy to protect from dust and whatnot, but it’s pretty much always chilly in the garage (an
12.
▲
by
shosti
5y ago
Thanks, glad you liked it! Minor clarification, I didn’t write the ingress comparison, that’s from https://learnk8s.io (who I’ve been working with recently). They have a bunch of awesome resources on their site.
13.
▲
by
shosti
5y ago
Location: San Francisco Remote: Open to it Willing to relocate: No Technologies: Go, Kubernetes, Postgres, Ruby/Rails, AWS/GCP, TypeScript, Rust Résumé/CV: https://www.linkedin.com/in/emanuelevans/
14.
▲
by
shosti
5y ago
This was a project I implemented for fun to try to understand how Raft works (and also get more practice with Rust). The basic idea is that some state gets synchronized between 3 browser windows (currently hard-coded) over WebRTC. It's
15.
▲
Show HN: WRaft, a WebAssembly Raft Implementation over WebRTC
(wraft0.eevans.co)
11 points
by
shosti
5y ago
|
1 comments
16.
▲
by
shosti
6y ago
SEEKING WORK | USA (UTC-8) | REMOTE Website and portfolio: https://eevans.co Technologies: Kubernetes, Google Cloud, AWS, Docker, Terraform, Go, others I specialize in cloud migrations, particularly in deploying applications to
17.
▲
The Simplest Multi-Node Kubernetes Cluster
(eevans.co)
1 points
by
shosti
6y ago
|
0 comments
18.
▲
Deconstructing Kubernetes Networking
(eevans.co)
2 points
by
shosti
6y ago
|
0 comments
19.
▲
Minimum Viable Kubernetes
(eevans.co)
3 points
by
shosti
6y ago
|
0 comments
20.
▲
How We Moved from Heroku to Google Kubernetes Engine
(rainforestqa.com)
1 points
by
shosti
7y ago
|
0 comments
21.
▲
How We Moved from Heroku to Google Kubernetes Engine
(rainforestqa.com)
8 points
by
shosti
7y ago
|
0 comments
22.
▲
by
shosti
7y ago
> This part seems very hand wavy, given that Heroku Shield would've solved many (all?) of their problems. Author here; I don’t want to go into too much detail, but we tried Shield early on and had a negative experience that made us
23.
▲
by
shosti
7y ago
Yeah AWS Aurora does have some nice capabilities compared to Cloud SQL; if it weren’t for the other issues mentioned in the article it would have been a driving factor towards choosing AWS. Still Cloud SQL seems “good enough” in general (ot
24.
▲
by
shosti
7y ago
Author here; yeah, helm is the part of our stack we’re least happy with tbh (it’s turned into a huge pile of templated yaml files for each project that seems like it might not be maintainable long-term). I’m curious about looking into kusto
25.
▲
Moving from Heroku to Google Kubernetes Engine
(rainforestqa.com)
225 points
by
shosti
7y ago
|
105 comments