Mark McLoughlin
Mark McLoughlin
Could the "decomposed view of Service" line of thinking from [GEP-1324](https://gateway-api.sigs.k8s.io/geps/gep-1324/) could be useful here? Let's say: - Part of the Service resource defines the "backend" - most obviously the...
> That said, I feel like spending too much time figuring that out falls into the "how" bucket - where this GEP is meant to represent our agreement that we...
Focusing on backend properties sounds good. But the way I read the the "why" section, a lot of the stuff after "In terms of other implementations existing use cases for...
Quoting #818 > Although we discussed the possibility of preemptively making port optional prior to beta graduation, that would open a rather complex topic of how an empty/unspecified port should...
#1066 adds docs for implementors about the possibility of required fields become optional in future: > Handle fields that have transitioned from required to optional without crashing
It's also important to distinguish things we put in place to make development easier, versus things we recommend real-world users do (and therefore that we should support) If we wanted...
Setting up DNS is currently a prerequisite that must be made clear to real-world users If we believe something like this is a good way of eliminating this prerequisite, then...
@stefwalter seems this is a gcc issue, see #1666 > This uninitialized variable issue is being addressed with https://github.com/pytorch/FBGEMM/pull/1697. However, this alone will not fix the build because there a...
Still an issue, would be great to fix such a prominent mistake in the docs