Matthias Wessendorf
Matthias Wessendorf
I'd say we add the deprecated warning, as a vehicle to communicate that things are changing, via the code
/cherry-pick release-1.7
/cherry-pick release-1.6
/cherry-pick release-1.5
/cc @houshengbo @psschwei
@houshengbo Is there additional work needed on the actual operator code base ?
@nak3 we have some code updating the HPA `minReplica` here: https://github.com/knative/operator/blob/main/pkg/reconciler/common/ha.go#L76-L89 I think we should do something similar on the `deployments_override.go` file, to check/tweak for both: `min` and `max`...
or that as a vehicle to make more options directly configurable, w/o guessing. Regardless, it would also would relate to the `ha.go` file
Below is a suggested content. But I am not sure where exactly to place this? Admin vs Dev ? or mix? ------------------------------------ # User Authentication with Istio and JWT This...
What eventually made it work is to point to the `Service` of the Knative Broker Ingress, like: ```yaml apiVersion: serving.knative.dev/v1alpha1 kind: DomainMapping metadata: name: brokers.apps.ci-ln-ksz9nx2-72292.origin-ci-int-gce.dev.rhcloud.com namespace: knative-eventing spec: ref: name:...