justinsb

7 ms·

1.
by justinsb 4y ago
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 observations really shaped how I chose to contribute to Kube
2.
by justinsb 4y ago
> 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 status.images field: https://kubernetes.io&#x
3.
by justinsb 4y ago
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 or Vercel or Netlify or Fly as not doing so is a
4.
by justinsb 4y ago
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 approach is the author recommending to use instead? It would be
5.
by justinsb 4y ago
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 their costs, until the plants come online. I think it&#x27
6.
by justinsb 7y ago
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 you add up all the code you're relying on it tu
7.
by justinsb 7y ago
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 particularly with ecosystem components. So we do lag a lit
8.
by justinsb 8y ago
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...
9.
by justinsb 8y ago
Not the cause. The release team asked for KEPs for all new features in the next release and the deadline was today.
10.
by justinsb 8y ago
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 prefer that a kops release is ready to run, bu
11.
by justinsb 8y ago
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-engine/18... should h
12.
by justinsb 8y ago
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 intent is to give you some assurances
13.
by justinsb 8y ago
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 me like the same incident was close
14.
by justinsb 8y ago
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 actually fixed, and that we just didn't update th
15.
by justinsb 8y ago
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/Documentation/note-db... which may be
16.
by justinsb 8y ago
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?
17.
by justinsb 8y ago
I believe you forgot to divide by the $100
18.
by justinsb 8y ago
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 added them all in: http://w
19.
by justinsb 8y ago
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 always welcome and appreciated!)
20.
by justinsb 8y ago
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 networking providers and ecosystem components. That's typ
21.
by justinsb 9y ago
Thanks for the note on the renewals (and the caveat!) - that does make it less concerning as it would only impact new services.
22.
by justinsb 9y ago
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 deploying gitlab and exhausted my quota sim
23.
by justinsb 9y ago
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 avoided this by combining names into a single certificate,
24.
by justinsb 9y ago
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.
25.
by justinsb 9y ago
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.
26.
by justinsb 9y ago
Are there things that can cost-effectively be done in existing houses? That seems a good way to create demand for greater efficiency - demonstrate the value on a smaller scale first.
27.
by justinsb 9y ago
Ron was one of our investors in FathomDB, and that turned out to be a bad financial investment, much to my personal dismay & regret. However, something that I think the essay modestly overlooks is the non-financial elements. The invest
28.
by justinsb 9y ago
We should update that issue. There is support for private route53 domains, which means you don't need a DNS domain name, and there is early experimental support for gossip discovery (i.e. no Route53 at all) - just create a cluster wit
29.
by justinsb 9y ago
100% agreed and looking forward to that - kops is a big part of that effort, actually. If you look under the hood you'll see that kops uses a lot of the kubernetes apimachinery. There's obviously a tricky chicken & egg situa
30.
by justinsb 9y ago
kops can set up an ELB for HA apiservers, but I think you're primarily talking about Ingress for your own services. We don't actually take an opinion on which Ingress controller you use, so you can just choose e.g. https:/&

More ›