Dave Protasowski
Dave Protasowski
> so add MaxDuration back to the spec? No - `TimeoutSeconds` is MaxDuration
> Are you saying use TimeoutSeconds for max duration and add a new fields for timeoutFirstByte and idleTimeout? yup `TimeoutSeconds` should behave as the spec originally intended which is max...
@cdlliuy thanks for the report - I'll take a look tomorrow (I'm on EST) and see if I can reproduce the issue
> When creating knative application in a namespace in which limit range min/max specified, Are you setting a [ResourceQuota](https://kubernetes.io/docs/concepts/policy/resource-quotas/) or [LimitRange](https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/cpu-constraint-namespace/#create-a-limitrange-and-a-pod) on the namespace? Do you have the example yaml?
Also what version of K8s are you are running
Great thanks - I'll take a look later today
So I was able to repro on Kind and [this script](https://gist.github.com/dprotaso/56c1fd920291eff29cce48f0501732a0). Looking at the code we don't propagate the deployment status to the revision unless it's 'active' so it'll time...
Potentially Related: https://github.com/knative/serving/issues/8540
/assign @dprotaso
/lifecycle frozen I believe there's some work to be done to not apply _new_ defaults on updates if the revisions has BYON