James Peach

xref #432

This use case sounds it could be satisfied by en external authentication service that validates the API key. External authentication is tracked in #432 and there is initial scoping in...

@stevesloka Any reason we can't take the knative patch? Or perhaps we should double-check what kubebuilder would generate and ensure we have the expected API there ...

> We removed the generated Informer types earlier because we weren't using them, and we didn't realise anyone else was. I don't see any issue with putting the generation back...

@stevesloka @youngnick I checked what kubebuilder does, and it generates a `groupversion_info.go` like this: ```Go import ( "k8s.io/apimachinery/pkg/runtime/schema" "sigs.k8s.io/controller-runtime/pkg/scheme" ) var ( // GroupVersion is group version used to register...

You could use either [genclient](https://www.openshift.com/blog/kubernetes-deep-dive-code-generation-customresources) to generate a typed client, or just use the client-go [dynamic client](https://github.com/kubernetes/client-go/tree/master/examples/dynamic-create-update-delete-deployment) with the Contour types registered with your scheme.

Duplicate of #855

The contour `Cookie` load balancer strategy uses a session cookie. IIUC, the HAProxy "persistent" session affinity does cookie-balancing but uses an application-specified cookie to do so (which means that the...

> @jpeach IIUC, stickiness survives contour or envoy restarts; because it is based upon cookies. Let me know if I am missing something here. Contour is not in the data...

See also the discussion in #2099. If you don't preserve multiple versions, then I don't think clusters can be automatically upgraded. You'd have to manually delete the old CRD versions...