xaleeks
xaleeks
@a-mccarthy not sure if this is worth highlighting in the docs, your call.
Bringing this back now, can we implement a controller in our operator for checking compatibility? Imagine it would be useful for when upgrading through the operator
Sounds good, we’ll leave it in parking lot1 if someone wants to pick this up
This seems no longer relevant. Please let me know if it needs to be reopened
>What I'm saying is, that in the case that there are multiple, weighted services defined on a route, and one of those services has zero available endpoints, then the weighting...
>if you combined this will health-checks, i think your intention is to have the corresponding repartitions when everything is working fine but have contour stop routing to unresponsive targets when...
@youngnick moved this to Prioritized Backlog because we need to address this better in docs even if it doesn't land immediately in a release
@youngnick Yup, we should support this. However, EndpointSlice started in k8s 1.17 it seems. Do we need to add a check that the version of K8s running supports it before...
Also according to https://kubernetes.io/docs/concepts/services-networking/endpoint-slices/, it allows for setting a "topology.kubernetes.io/zone" key. Which opens us to this https://kubernetes.io/docs/concepts/services-networking/service-topology/ So a client can hit his preferred node specified in the topologyKeys for...
Great idea. Just want to add we need to support both IPv4 and v6, specified in both single IPs and CIDR blocks. Another comment is we can either make this...