Knative Serving Component

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 holds the max duration the instance is allowed for responding to a request. 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.

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

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.

(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.)

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

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

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

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

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

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

DeprecatedGeneration was used prior in Kubernetes versions <1.11 when metadata.generation was not being incremented by the api server

This property will be dropped in future Knative releases and should not be used - use metadata.generation

Tracking issue: https://github.com/knative/serving/issues/643

Build optionally holds the specification for the build to perform to produce the Revision’s container image.

DeprecatedRevisionTemplate holds the latest specification for the Revision to be stamped out. If a Build specification is provided, then the DeprecatedRevisionTemplate’s BuildName field will be populated with the name of the Build object created to produce the container for the Revision. DEPRECATED Use Template instead.

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.

The revision name to pin this service to until changed to a different service type.

The configuration for this service.

Revisions is an ordered list of 1 or 2 revisions. The first will have a TrafficTarget with a name of “current” and the second will have a name of “candidate”.

RolloutPercent is the percent of traffic that should be sent to the “candidate” revision. Valid values are between 0 and 99 inclusive.

The configuration for this service. All revisions from this service must come from a single configuration.

(Members of RevisionSpec are embedded into this type.)

DeprecatedGeneration was used prior in Kubernetes versions <1.11 when metadata.generation was not being incremented by the api server

This property will be dropped in future Knative releases and should not be used - use metadata.generation

Tracking issue: https://github.com/knative/serving/issues/643

DeprecatedServingState holds a value describing the desired state the Kubernetes resources should be in for this Revision. Users must not specify this when creating a revision. These values are no longer updated by the system.

DeprecatedContainer defines the unit of execution for this Revision. In the context of a Revision, we disallow a number of the fields of this Container, including: name and lifecycle. See also the runtime contract for more information about the execution environment: https://github.com/knative/serving/blob/master/docs/runtime-contract.md

(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.

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

DeprecatedGeneration was used prior in Kubernetes versions <1.11 when metadata.generation was not being incremented by the api server

This property will be dropped in future Knative releases and should not be used - use metadata.generation

Tracking issue: https://github.com/knative/serving/issues/643

Traffic specifies how to distribute traffic over a collection of Knative Serving 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}

DeprecatedDomain holds the top-level domain that will distribute traffic over the provided targets. It generally has the form {route-name}.{route-namespace}.{cluster-level-suffix}

DeprecatedDomainInternal holds the top-level domain that will distribute traffic over the provided targets from inside the cluster. It generally has the form {route-name}.{route-namespace}.svc.{cluster-domain-name} DEPRECATED: Use Address instead.

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.

The configuration for this service.

DeprecatedGeneration was used prior in Kubernetes versions <1.11 when metadata.generation was not being incremented by the api server

This property will be dropped in future Knative releases and should not be used - use metadata.generation

Tracking issue: https://github.com/knative/serving/issues/643

DeprecatedRunLatest defines a simple Service. It will automatically configure a route that keeps the latest ready revision from the supplied configuration running.

DeprecatedPinned is DEPRECATED in favor of ReleaseType

DeprecatedManual mode enables users to start managing the underlying Route and Configuration resources directly. This advanced usage is intended as a path for users to graduate from the limited capabilities of Service to the full power of Route.

Release enables gradual promotion of new revisions by allowing traffic to be split between two revisions. This type replaces the deprecated Pinned type.

(Members of ConfigurationSpec are embedded into this type.)

We are moving to a shape where the Configuration and Route specifications are inlined into the Service, which gives them compatible shapes. We are staging this change here as a path to this in v1beta1, which drops the “mode” based specifications above. Ultimately all non-v1beta1 fields will be deprecated, and then dropped in v1beta1.

(Members of RouteSpec are embedded into this type.)

(Members of Status are embedded into this type.)

(Members of RouteStatusFields are embedded into this type.)

(Members of ConfigurationStatusFields are embedded into this type.)

Name is optionally used to expose a dedicated hostname for referencing this target exclusively. It has the form: {name}.${route.status.domain}

(Members of TrafficTarget are embedded into this type.)

We inherit most of our fields by inlining the v1 type. Ultimately all non-v1 fields will be deprecated.

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

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