Spec holds the desired state of the PodAutoscaler (from the client).

Status communicates the observed state of the PodAutoscaler (from the controller).

Spec holds the desired state of the Metric (from the client).

Status communicates the observed state of the Metric (from the controller).

StableWindow is the aggregation window for metrics in a stable state.

PanicWindow is the aggregation window for metrics where quick reactions are needed.

ScrapeTarget is the K8s service that publishes the metric endpoint.

(Members of Status are embedded into this type.)

ContainerConcurrency specifies the maximum allowed in-flight (concurrent) requests per container of the Revision. Defaults to 0 which means unlimited concurrency.

ScaleTargetRef defines the /scale-able resource that this PodAutoscaler is responsible for quickly right-sizing.

Reachability specifies whether or not the ScaleTargetRef can be reached (ie. has a route). Defaults to ReachabilityUnknown

The application-layer protocol. Matches ProtocolType inferred from the revision spec.

(Members of Status are embedded into this type.)

ServiceName is the K8s Service name that serves the revision, scaled by this PA. The service is created and owned by the ServerlessService object owned by this PA.

MetricsServiceName is the K8s Service name that provides revision metrics. The service is managed by the PA object.

DesiredScale shows the current desired number of replicas for the revision.

ActualScale shows the actual number of replicas for the revision.

“Reachable”

ReachabilityReachable means the ScaleTarget is reachable, ie. it has an active route.

“”

ReachabilityUnknown means the reachability of the ScaleTarget is unknown. Used when the reachability cannot be determined, eg. during activation.

“Unreachable”

ReachabilityUnreachable means the ScaleTarget is not reachable, ie. it does not have an active route.

Spec holds the desired state of the Route (from the client).

Status communicates the observed state of the Route (from the controller).

Template holds the latest specification for the Revision to be stamped out.

(Members of Status are embedded into this type.)

(Members of ConfigurationStatusFields are embedded into this type.)

LatestReadyRevisionName holds the name of the latest Revision stamped out from this Configuration that has had its “Ready” condition become “True”.

LatestCreatedRevisionName is the last revision that was created from this Configuration. It might not be ready yet, for that use LatestReadyRevisionName.

(Members of PodSpec are embedded into this type.)

ContainerConcurrency specifies the maximum allowed in-flight (concurrent) requests per container of the Revision. Defaults to 0 which means concurrency to the application is not limited, and the system decides the target concurrency for the autoscaler.

TimeoutSeconds is the maximum duration in seconds that the request routing layer will wait for a request delivered to a container to begin replying (send network traffic). If unspecified, a system default will be provided.

(Members of Status are embedded into this type.)

ServiceName holds the name of a core Kubernetes Service resource that load balances over the pods backing this Revision. Deprecated: revision service name is effectively equal to the revision name, as per #10540. 0.23 — stop populating 0.25 — remove.

LogURL specifies the generated logging url for this particular revision based on the revision url template specified in the controller’s config.

DeprecatedImageDigest holds the resolved digest for the image specified within .Spec.Container.Image. The digest is resolved during the creation of Revision. This field holds the digest value regardless of whether a tag or digest was originally specified in the Container object. It may be empty if the image comes from a registry listed to skip resolution. If multiple containers specified then DeprecatedImageDigest holds the digest for serving container. DEPRECATED: Use ContainerStatuses instead. TODO(savitaashture) Remove deprecatedImageDigest. ref https://kubernetes.io/docs/reference/using-api/deprecation-policy for deprecation.

ContainerStatuses is a slice of images present in .Spec.Container[*].Image to their respective digests and their container name. The digests are resolved during the creation of Revision. ContainerStatuses holds the container name and image digests for both serving and non serving containers. ref: http://bit.ly/image-digests

ActualReplicas reflects the amount of ready pods running this revision.

DesiredReplicas reflects the desired amount of pods running this revision.

Traffic specifies how to distribute traffic over a collection of revisions and configurations.

(Members of Status are embedded into this type.)

(Members of RouteStatusFields are embedded into this type.)

URL holds the url that will distribute traffic over the provided traffic targets. It generally has the form http[s]://{route-name}.{route-namespace}.{cluster-level-suffix}

Address holds the information needed for a Route to be the target of an event.

Traffic holds the configured traffic distribution. These entries will always contain RevisionName references. When ConfigurationName appears in the spec, this will hold the LatestReadyRevisionName that we last observed.

“active”

RoutingStateActive is a state for a revision which is actively referenced by a Route.

“pending”

RoutingStatePending is a state after a revision is created, but before its routing state has been determined. It is treated like active for the purposes of revision garbage collection.

“reserve”

RoutingStateReserve is a state for a revision which is no longer referenced by a Route, and is scaled down, but may be rapidly pinned to a route to be made active again.

“”

RoutingStateUnset is the empty value for routing state, this state is unexpected.

(Members of ConfigurationSpec are embedded into this type.)

ServiceSpec inlines an unrestricted ConfigurationSpec.

(Members of RouteSpec are embedded into this type.)

ServiceSpec inlines RouteSpec and restricts/defaults its fields via webhook. In particular, this spec can only reference this Service’s configuration and revisions (which also influences defaults).

(Members of Status are embedded into this type.)

(Members of ConfigurationStatusFields are embedded into this type.)

In addition to inlining ConfigurationSpec, we also inline the fields specific to ConfigurationStatus.

(Members of RouteStatusFields are embedded into this type.)

In addition to inlining RouteSpec, we also inline the fields specific to RouteStatus.

Tag is optionally used to expose a dedicated url for referencing this target exclusively.

RevisionName of a specific revision to which to send this portion of traffic. This is mutually exclusive with ConfigurationName.

ConfigurationName of a configuration to whose latest revision we will send this portion of traffic. When the “status.latestReadyRevisionName” of the referenced configuration changes, we will automatically migrate traffic from the prior “latest ready” revision to the new one. This field is never set in Route’s status, only its spec. This is mutually exclusive with RevisionName.

LatestRevision may be optionally provided to indicate that the latest ready Revision of the Configuration should be used for this traffic target. When provided LatestRevision must be true if RevisionName is empty; it must be false when RevisionName is non-empty.

Percent indicates that percentage based routing should be used and the value indicates the percent of traffic that is be routed to this Revision or Configuration. 0 (zero) mean no traffic, 100 means all traffic. When percentage based routing is being used the follow rules apply: - the sum of all percent values must equal 100 - when not specified, the implied value for percent is zero for that particular Revision or Configuration

URL displays the URL for accessing named traffic targets. URL is displayed in status, and is disallowed on spec. URL must contain a scheme (e.g. http://) and a hostname, but may not contain anything else (e.g. basic auth, url path, etc.)

Standard object’s metadata. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#metadata

Spec is the desired state of the DomainMapping. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

Status is the current state of the DomainMapping. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

Ref specifies the target of the Domain Mapping.

The object identified by the Ref must be an Addressable with a URL of the form {name}.{namespace}.{domain} where {domain} is the cluster domain, and {name} and {namespace} are the name and namespace of a Kubernetes Service.

This contract is satisfied by Knative types such as Knative Services and Knative Routes, and by Kubernetes Services.

(Members of Status are embedded into this type.)

URL is the URL of this DomainMapping.

Address holds the information needed for a DomainMapping to be the target of an event.