Viewing profile — justinsb
justinsb
HN member- Joined
- Tue, Aug 21, 2007, 6:30 PM UTC
- HN karma
- 3,831
- Public activity
- 913 items
- HN profile
- View on Hacker News ↗
About justinsb
Recent public activity
-
comment
Comment #33276011
I also started (non-trivially) contributing to OSS with OpenStack, and later switched to contributing to Kubernetes. I whole-heartedly agree with the points made here; these same o…
-
comment
Comment #32305916
> we'd like the scheduler to be aware of which node has which image The kubernetes scheduler should be aware of which node has which image, that is why the Node object has the stat…
-
comment
Comment #31978587
Maybe it could be read that way, but I think it's a good indication of the problem that a strict reading doesn't include that. The article advocates that you should be using Heroku…
-
comment
Comment #31976730
The problem with this sort of argument is that it sets up a straw-man, without describing what you should do instead. Kubernetes could be better - of course - but what better appro…
-
comment
Comment #31686705
The only nuclear plant under construction in the US is at Plant Vogtle, in Georgia. Regulators set up a system (CWIP) whereby the companies building the plant earn a 10% return on …
-
comment
Comment #19497759
Thanks for the input on kops. There's a lot of functionality in kops - e.g. we can manage CNI providers, etcd etc. In some places this manifests as more code, but my gut is that if…
-
comment
Comment #19497703
Yes, the reality is probably somewhere in between. We've heard that users like the idea that kops releases are more ready, where the .0 releases of k8s might have more issues parti…
-
comment
Comment #19031508
Oh sorry - yes that's me! Disclaimer: I work for Google on GKE & Kubernetes! I thought this was more of a community question and forgot...
-
comment
Comment #19031467
Not the cause. The release team asked for KEPs for all new features in the next release and the deadline was today.
-
comment
Comment #18613193
Yes, we're waiting till 1.11.6 lands - some important fixes for clouds in there. We've debated releasing at the same time as Kubernetes, but the feedback we've got is that users pr…
-
comment
Comment #18429164
The general page is at https://status.cloud.google.com/ ; you can scroll down to see GKE, and my (unofficial) belief is that https://status.cloud.google.com/incident/container-engi…
-
comment
Comment #18429117
I can assure you that's not the case! Also, while people like to repeat this meme, Google Cloud does have a formal deprecation policy ( https://cloud.google.com/terms/ ), whose int…
-
comment
Comment #18429094
The incident with the UI (where we suggested using gcloud temporarily) was opened in https://status.cloud.google.com/incident/container-engine/18... , but then what sure looks to m…
-
comment
Comment #18428985
Hi - I work at Google on GKE - sorry about the problems you're experiencing. There's a lot of people inside Google looking into this right now! It looks like the UI issue was actua…
-
comment
Comment #18315646
This looks very well done - I've been hoping for something like this for a long time! For code review (pull requests) there's also https://gerrit-review.googlesource.com/Documentat…
-
comment
Comment #18015657
The article suggests that the difference is the water recirculation - that the "waste" water is cleaned rather than being removed. Is that how your farm's raceway worked?
-
comment
Comment #17787902
I believe you forgot to divide by the $100
-
comment
Comment #17453598
Which company is that from, and did you include the surcharges? I'm on Georgia Power on the R-22 residential tariff, and I pay about twice as much as the "headline rate", once I've…
-
comment
Comment #16700457
Ah - sorry, probably should have disclaimered that! I did write the original kops code, but now there's a pretty active set of contributors working on kops (and contributions are a…
-
comment
Comment #16699654
kops 1.9 is very close to ready now, but this is a longer lag than normal. We've historically released kops 1.x when we consider that k8s 1.x is stable, including all the networkin…
-
comment
Comment #16408785
Thanks for the note on the renewals (and the caveat!) - that does make it less concerning as it would only impact new services.
-
comment
Comment #16408746
By "when moving domains" I mean that I'm enabling a production domain (project.com), where previously I was working on a development domain (project-dev.com). More recently, I was …
-
comment
Comment #16404781
I love LetsEncrypt - the only problem I've hit is the rate limits (in particular 20 new certificates per registered domain per week, when moving domains). I guess I could have avoi…
-
comment
Comment #16031431
Is any of this enabled yet (even if only in the dev channels)? Being able to run arbitrary containers locally would make a Pixelbook a lot more powerful.
-
comment
Comment #16009241
I think it's a huge positive development that there's a reference implementation as well, in go. At least helpful for evaluation, possibly for a production implementation also.