Markus Thömmes
Markus Thömmes
I agree with @devguyio's sentiment. It feels like what you want is a resource in between, that can then implement whichever semantics you like (in your case calling some external...
Just to speak it out loud (re @devguyio's suggestion): You could install a webhook that leaves the API intact and does the translation for you ```yaml ref: apiVersion: my.batch.job/v1alpha1 kind:...
I'm not quite parsing in which way that's more confusing vs. having the resolution been done by some service that the user can't even inspect. In the outlined approach, the...
We also need to think about upgrade paths that are not just our K8s resources. Our recent work on the Activator -> Autoscaler communication or Queue-Proxy -> Autoscaler communication comes...
@mattmoor also mentioned in the Slack thread to possibly lower our release cadence as we near 1.0.0 (K8s and Istio are both on a 3 month schedule).
The Operations WG has a planned feature to support orchestrated upgrades across minor versions in https://github.com/knative/operator/issues/744
Ack! I need the very same thing, where my cluster has already mechanisms to come up with certificates that I'd like to mount for the webhook to "just" pick up....
Imma going to take a whack at this one. /assign
/unassign not doing this rn.
Still happening in serving too I believe: https://prow.knative.dev/view/gcs/knative-prow/logs/ci-knative-serving-continuous/1285454712115564545