85 karma · joined October 19, 2016
ahmed.taahir@gmail
The f1-micro would be the worker node. It's still a bit of a squeeze, because GKE has system workloads that need to run on user nodes.
That's what a standard vaccine with an attenuated virus does as well.
Effectively, all storage for production systems at Google goes through this layer. No service is ever interacting with individual disks, even including databases like Spanner.
Google Cloud Storage is a thin-ish layer over this system.
I was under the impression that Nix also wants to provide bit-for-bit reproducible builds, but that that is a much longer term goal. The immediate value proposition of Nix is ensuring that your source and your dependencies' source are the same.
For example, if you have two people arguing without weapons, the likely outcomes of the situation aren't strongly weighted towards one or both of the participants being maimed or killed --- it's difficult and requires commitment to really cause horrific damage if you're just hitting each other.
If you introduce a (supposedly value-neutral) tool, like a gun, into the situation, the outcomes become much more strongly weighted towards someone being maimed or killed.
Even though it's always a human using the tool, the tool itself can be seen as having an ethical character.
You might have more luck opening a GCP support case, or using the chat support. They may have the ability to help you figure out what's going on, especially if the affected credit card is the one linked to your GCP billing account.
And a Gentoo box without Make is just hosed.
Both COS and Ubuntu nodes are integrated with IAM, so this transparently provisions a user on the node, and copies a temporary SSH key. If your GCP user has the appropriate IAM permissions, they will also be able to use `sudo` to execute commands as root.
As long as you maintain the distinct type of the lambda, any captures (by reference or by value) will just be fields in a stack object.