serving icon indicating copy to clipboard operation
serving copied to clipboard

Kubernetes-based, scale-to-zero, request-driven compute

Results 420 serving issues
Sort by recently updated
recently updated
newest added

/area networking ## What version of Knative? Knative Serving v1.17, v1.18, v1.19, v1.20.0 Also confirmed on main branch: `knative-v1.20.0-52-gabbe514be` ## Expected Behavior When creating a Knative Service with a private...

kind/bug
area/networking

Fixes #11916 Services can no longer route traffic to revisions belonging to different services. When a Service-owned Route references a revision with a different serving.knative.dev/service label, the Route will show...

size/L

## Ask your question here: I'm trying to monitor request latency for my Knative services broken down by HTTP response code (or response code class like 2xx, 4xx, 5xx), similar...

kind/question

## In what area(s)? /area API /area networking ## Describe the feature ### The Request We request the ability to customize HTTP Request Headers in the VirtualService generated and managed...

kind/feature
area/API
area/networking

## In what area(s)? /area API /area networking ## What version of Knative? > 1.6 with Istio ## Expected Behavior Assume that the foobar service is deployed to the baz...

kind/bug
area/API
area/networking
lifecycle/frozen
triage/accepted

## What version of Knative? Repro'd with 0.25.1 ## Expected Behavior Update the traffic rules of a Service to point to another revision should fail ## Actual Behavior The traffic...

kind/bug
lifecycle/frozen
triage/accepted

## Problem Description Revisions with `initialScale > 1` that are no longer referenced by any Route (i.e., `routingState = "reserve"`) cannot scale down to 0, causing resource waste when old...

kind/bug

Fixes # #15823 ## Proposed Changes Add `terminationGracePeriodSeconds` in the probe Mask used for the container probes. This will allw it to be configurable for the container probes. I add...

size/XL
ok-to-test

This is an automated cherry-pick of #16290 ```release-note Fix metric names to match the original design document `kn.queueproxy.app.duration` becomes `kn.serving.invocation.duration` and `kn.queueproxy.depth` becomes `kn.serving.queue.depth` ```

size/XS
lgtm
do-not-merge/hold
approved

This is an automated cherry-pick of #16290 ```release-note Fix metric names to match the original design document `kn.queueproxy.app.duration` becomes `kn.serving.invocation.duration` and `kn.queueproxy.depth` becomes `kn.serving.queue.depth` ```

size/XS
lgtm
do-not-merge/hold
approved