benth
"For example, one customer told us that they plan to create hundreds of VPCs, each hosting and providing a single microservice"
At first glance, that sounds pretty neat, but looking at VPC pricing shows that PrivateLink pricing is 1 cent per hour and 1 cent per GB.
It'd be nice to discuss pricing before suggesting we partition microservices into separate VPCs. Or after. Somewhere :-)
That pricing can add up if you're making "hundreds of VPCs"!
See: https://www.plex.tv/blog/its-not-easy-being-green-secure-com... and https://blog.filippo.io/how-plex-is-doing-https-for-all-its-...
Coincidentally, I'm working on a project that uses Kubernetes and it has a very locked down pod placement policy, so the attack you described would be significantly scoped down. But I don't think the same is true of most Kubernetes deployments.
Quoting the docs at https://kubernetes.io/docs/user-guide/secrets/#security-prop...:
"Currently, anyone with root on any node can read any secret from the apiserver, by impersonating the kubelet. It is a planned feature to only send secrets to nodes that actually require them, to restrict the impact of a root exploit on a single node."
As your cluster grows, your risk grows.
Give us packets, get IT and business insight.
Like systems-level programming? C, Go, Python? Let's talk! [email protected]
Deep L7 protocol analysis at scale.
I am grateful this free alternative exists, because the subject matter is really fun.
From packets to perspicacity.
If you want to work at a company with a strong engineering team, founded and run by engineers, send us an email: [email protected]
Six months later, July 2011, the first Beta was released and Jon Skinner said there would be monthly updates now that ST2 was in beta.
True to his word, there's been about an update a month and then in June 2012 the Beta label was dropped. After that, there were a few ST2 updates, mostly fixes, until September 2012. So by no means is ST2 an "unfinished" piece of software. And while I'm sure it has many bugs, that's practically a truism for any piece of complicated software. I personally have not actually noticed any. I wonder if the author has.
My takeaway from all this is that Jon Skinner delivers.
If you want a yearly subscription, well, that's really no different than what Jon Skinner is providing, except that instead of paying once a year, you're paying once every TWO years, if the past is any indication of the future.
Finally, complaining about plugins breaking is like complaining about the Lightning connector on new iPhones. There's a strong list of good reasons to make backward-incompatible changes to the plugin system.
I am curious why RAID6 is (still) used given its poor behavior in failure conditions. I am guessing that Backblaze is not as worried about additional drive failure in an array during a rebuild because they are periodically verifying each drive.
Comparing to a X4540 is kind of a stretch. The use cases seem very different. Also, it for Backblaze, they wouldn't exist at the price they charge, with the price that Sun charged for an X4540.
I hope Joyent does release something about their config, that would be very interesting.
Some code does not round-trip. This JS terminates but if I convert the resulting CS back to JS, I get an infinite loop.
function test() {
var i;
var countdown = function(n) {
var i;
for (var i = n; i > 0; i--) {
console.log(i);
}
}
for (var i = 0; i < 10; i++) {
countdown(i);
}
}
test();