serving
serving copied to clipboard
Kubernetes-based, scale-to-zero, request-driven compute
Fixes # ## Proposed Changes * * * **Release Note** ```release-note ```
## What version of Knative? v1.17 ## Expected Behavior I have a ksvc using hpa for autoscaling class. After changes made to ksvc, a new revision is generated, I'd expect...
Fixes #15755 ## Proposed Changes For the specific case described [here](https://github.com/knative/serving/issues/15755#issue-2836669521), we now check for a NotFound error and return an empty list. **Release Note** ```release-note NONE ```
Fixes #15889 ## Proposed Changes * Revision is set to healthy, when the deployment has the minimum number of replicas running and ready. **Release Note** ```release-note Revision is set to...
```yaml apiVersion: serving.knative.dev/v1 kind: Service metadata: name: hoge namespace: hoge spec: template: metadata: annotations: autoscaling.knative.dev/minScale: "0" features.knative.dev/http-full-duplex: Enabled instrumentation.opentelemetry.io/inject-nodejs: opentelemetry-collector/instrumentation refresh: "true" creationTimestamp: null spec: containerConcurrency: 0 containers: - envFrom:...
## Describe the feature Currently there is no possibility to ignore health check metrics in knative metrics. We have multiple knative services with different health check URL's which are called...
## What version of Knative? 1.17.0 net-istio: 1.17.0 istio: 1.24.2 ## Expected Behavior The knative service status should be “Ready” instead of hanging in “Unknown” state. ## Actual Behavior When...
## Ask your question here: I am trying to set up knative with a custom istio gateway with TLS all the way through to the pod. I followed these direction,...
## Proposed Changes * When in roll out, skip minScale until traffic shifts for workloads with a specific annotation `features.knative.dev/skip-min-scale-during-rollout: "Enabled"`. Although we dont provide guarantees for a smooth traffic...
> Hi, thanks for pushing this fix. I had this issue, and when I tried to upgrade to 1.18.0, I now see the following instead, which also appears to be...