That brings back memories... https://github.com/kelseyhightower/nocode/issues/3#issuecomm... was one of my favorites

The motivation is more the latter, but it's not at all clear the proposed removal of the embedded kustomize will proceed, given the compatibility implications. See discussion at https://github.com/kubernetes/enhancements/issues/4706#issue... and following.

Thank you for this and your many many other contributions!

> if I may ask for an addition in go 1.22: encoding/yaml

FYI, encoding/yaml was recently requested, and was declined in https://github.com/golang/go/issues/61023#issuecomment-16106..., for reasons I largely agree with.

(I work for Google but not on Go)

That's explicitly not guaranteed. From https://proxy.golang.org:

> Why did a previously available module become unavailable in the mirror?

>

> proxy.golang.org does not save all modules forever. There are a number of reasons for this…

(I am a googler, but don't work on the go team – my opinions that projects should vendor and actually review their dependencies are my own)

> proxy.golang.org does not save all modules forever. There are a number of reasons for this, but one reason is if proxy.golang.org is not able to detect a suitable license.

If you're vendoring something without an appropriate license, you're skating on thin ice legally.

That's just one possible reason. The disclaimer does not specify all the possible reasons the proxy would drop a saved version. Treating it more like a cache seems appropriate.

https://www.youtube.com/watch?v=jlPaby7suOc&t=13s is a fantastic parody talk, and this is one of my favorite moments of it

Laggy loading of items into a tappable target area is begging to be called the “slow poke” pattern

I want to see the study on the impact of novice developers on senior developers' sleep deprivation

If you decide to run with the RBAC authorizer, tools like kubeadm run the control plane components with credentials that have the required permissions out of the box. If you're using your own deployment/setup, you'll want to consult https://kubernetes.io/docs/admin/authorization/rbac/#core-co... to either give standard user/group names to your components, or grant the appropriate roles to custom user/group names.

Once your control plane is running, granting API access to other apps that need it is typically a matter of creating a service account, setting that service account in the pod spec, and granting the service account a role with sufficient access. See https://kubernetes.io/docs/admin/authorization/rbac/#service...

Finally, if you're upgrading an existing cluster, and want to turn on RBAC authorization, there are tips at https://kubernetes.io/docs/admin/authorization/rbac/#upgradi... for easing the transition.