mirror of https://github.com/knative/docs.git
Sam O'Dell
Knative Prow Robot
parent
a6773bcd62
commit
292d0050fe
|
|
@ -2613,5 +2613,5 @@ knative.dev/eventing/pkg/apis/duck/v1alpha1.SubscribableTypeStatus
|
|||
<hr/>
|
||||
<p><em>
|
||||
Generated with <code>gen-crd-api-reference-docs</code>
|
||||
on git commit <code>c409ee07</code>.
|
||||
on git commit <code>395598e8</code>.
|
||||
</em></p>
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -1,9 +1,6 @@
|
|||
<p>Packages:</p>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="#serving.knative.dev%2fv1beta1">serving.knative.dev/v1beta1</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="#autoscaling.internal.knative.dev%2fv1alpha1">autoscaling.internal.knative.dev/v1alpha1</a>
|
||||
</li>
|
||||
<li>
|
||||
|
|
@ -15,460 +12,10 @@
|
|||
<li>
|
||||
<a href="#serving.knative.dev%2fv1alpha1">serving.knative.dev/v1alpha1</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="#serving.knative.dev%2fv1beta1">serving.knative.dev/v1beta1</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="serving.knative.dev/v1beta1">serving.knative.dev/v1beta1</h2>
|
||||
<p>
|
||||
</p>
|
||||
Resource Types:
|
||||
<ul><li>
|
||||
<a href="#serving.knative.dev/v1beta1.Configuration">Configuration</a>
|
||||
</li><li>
|
||||
<a href="#serving.knative.dev/v1beta1.Revision">Revision</a>
|
||||
</li><li>
|
||||
<a href="#serving.knative.dev/v1beta1.Route">Route</a>
|
||||
</li><li>
|
||||
<a href="#serving.knative.dev/v1beta1.Service">Service</a>
|
||||
</li></ul>
|
||||
<h3 id="serving.knative.dev/v1beta1.Configuration">Configuration
|
||||
</h3>
|
||||
<p>
|
||||
<p>Configuration represents the “floating HEAD” of a linear history of Revisions.
|
||||
Users create new Revisions by updating the Configuration’s spec.
|
||||
The “latest created” revision’s name is available under status, as is the
|
||||
“latest ready” revision’s name.
|
||||
See also: <a href="https://github.com/knative/serving/blob/master/docs/spec/overview.md#configuration">https://github.com/knative/serving/blob/master/docs/spec/overview.md#configuration</a></p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>apiVersion</code></br>
|
||||
string</td>
|
||||
<td>
|
||||
<code>
|
||||
serving.knative.dev/v1beta1
|
||||
</code>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>kind</code></br>
|
||||
string
|
||||
</td>
|
||||
<td><code>Configuration</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>metadata</code></br>
|
||||
<em>
|
||||
<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#objectmeta-v1-meta">
|
||||
Kubernetes meta/v1.ObjectMeta
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
Refer to the Kubernetes API documentation for the fields of the
|
||||
<code>metadata</code> field.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>spec</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.ConfigurationSpec">
|
||||
ConfigurationSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<br/>
|
||||
<br/>
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<code>template</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.RevisionTemplateSpec">
|
||||
RevisionTemplateSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Template holds the latest specification for the Revision to be stamped out.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>status</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.ConfigurationStatus">
|
||||
ConfigurationStatus
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="serving.knative.dev/v1beta1.Revision">Revision
|
||||
</h3>
|
||||
<p>
|
||||
<p>Revision is an immutable snapshot of code and configuration. A revision
|
||||
references a container image. Revisions are created by updates to a
|
||||
Configuration.</p>
|
||||
<p>See also: <a href="https://github.com/knative/serving/blob/master/docs/spec/overview.md#revision">https://github.com/knative/serving/blob/master/docs/spec/overview.md#revision</a></p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>apiVersion</code></br>
|
||||
string</td>
|
||||
<td>
|
||||
<code>
|
||||
serving.knative.dev/v1beta1
|
||||
</code>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>kind</code></br>
|
||||
string
|
||||
</td>
|
||||
<td><code>Revision</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>metadata</code></br>
|
||||
<em>
|
||||
<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#objectmeta-v1-meta">
|
||||
Kubernetes meta/v1.ObjectMeta
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
Refer to the Kubernetes API documentation for the fields of the
|
||||
<code>metadata</code> field.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>spec</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.RevisionSpec">
|
||||
RevisionSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<br/>
|
||||
<br/>
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<code>PodSpec</code></br>
|
||||
<em>
|
||||
<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#podspec-v1-core">
|
||||
Kubernetes core/v1.PodSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>
|
||||
(Members of <code>PodSpec</code> are embedded into this type.)
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>containerConcurrency</code></br>
|
||||
<em>
|
||||
int64
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>ContainerConcurrency specifies the maximum allowed in-flight (concurrent)
|
||||
requests per container of the Revision. Defaults to <code>0</code> which means
|
||||
concurrency to the application is not limited, and the system decides the
|
||||
target concurrency for the autoscaler.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>timeoutSeconds</code></br>
|
||||
<em>
|
||||
int64
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>TimeoutSeconds holds the max duration the instance is allowed for
|
||||
responding to a request. If unspecified, a system default will
|
||||
be provided.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>status</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.RevisionStatus">
|
||||
RevisionStatus
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="serving.knative.dev/v1beta1.Route">Route
|
||||
</h3>
|
||||
<p>
|
||||
<p>Route is responsible for configuring ingress over a collection of Revisions.
|
||||
Some of the Revisions a Route distributes traffic over may be specified by
|
||||
referencing the Configuration responsible for creating them; in these cases
|
||||
the Route is additionally responsible for monitoring the Configuration for
|
||||
“latest ready revision” changes, and smoothly rolling out latest revisions.
|
||||
See also: <a href="https://github.com/knative/serving/blob/master/docs/spec/overview.md#route">https://github.com/knative/serving/blob/master/docs/spec/overview.md#route</a></p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>apiVersion</code></br>
|
||||
string</td>
|
||||
<td>
|
||||
<code>
|
||||
serving.knative.dev/v1beta1
|
||||
</code>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>kind</code></br>
|
||||
string
|
||||
</td>
|
||||
<td><code>Route</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>metadata</code></br>
|
||||
<em>
|
||||
<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#objectmeta-v1-meta">
|
||||
Kubernetes meta/v1.ObjectMeta
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
Refer to the Kubernetes API documentation for the fields of the
|
||||
<code>metadata</code> field.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>spec</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.RouteSpec">
|
||||
RouteSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Spec holds the desired state of the Route (from the client).</p>
|
||||
<br/>
|
||||
<br/>
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<code>traffic</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.TrafficTarget">
|
||||
[]TrafficTarget
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Traffic specifies how to distribute traffic over a collection of
|
||||
revisions and configurations.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>status</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.RouteStatus">
|
||||
RouteStatus
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Status communicates the observed state of the Route (from the controller).</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="serving.knative.dev/v1beta1.Service">Service
|
||||
</h3>
|
||||
<p>
|
||||
<p>Service acts as a top-level container that manages a Route and Configuration
|
||||
which implement a network service. Service exists to provide a singular
|
||||
abstraction which can be access controlled, reasoned about, and which
|
||||
encapsulates software lifecycle decisions such as rollout policy and
|
||||
team resource ownership. Service acts only as an orchestrator of the
|
||||
underlying Routes and Configurations (much as a kubernetes Deployment
|
||||
orchestrates ReplicaSets), and its usage is optional but recommended.</p>
|
||||
<p>The Service’s controller will track the statuses of its owned Configuration
|
||||
and Route, reflecting their statuses and conditions as its own.</p>
|
||||
<p>See also: <a href="https://github.com/knative/serving/blob/master/docs/spec/overview.md#service">https://github.com/knative/serving/blob/master/docs/spec/overview.md#service</a></p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>apiVersion</code></br>
|
||||
string</td>
|
||||
<td>
|
||||
<code>
|
||||
serving.knative.dev/v1beta1
|
||||
</code>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>kind</code></br>
|
||||
string
|
||||
</td>
|
||||
<td><code>Service</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>metadata</code></br>
|
||||
<em>
|
||||
<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#objectmeta-v1-meta">
|
||||
Kubernetes meta/v1.ObjectMeta
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
Refer to the Kubernetes API documentation for the fields of the
|
||||
<code>metadata</code> field.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>spec</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.ServiceSpec">
|
||||
ServiceSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<br/>
|
||||
<br/>
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<code>ConfigurationSpec</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.ConfigurationSpec">
|
||||
ConfigurationSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>
|
||||
(Members of <code>ConfigurationSpec</code> are embedded into this type.)
|
||||
</p>
|
||||
<p>ServiceSpec inlines an unrestricted ConfigurationSpec.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>RouteSpec</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.RouteSpec">
|
||||
RouteSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>
|
||||
(Members of <code>RouteSpec</code> are embedded into this type.)
|
||||
</p>
|
||||
<p>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).</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>status</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.ServiceStatus">
|
||||
ServiceStatus
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<hr/>
|
||||
<h2 id="autoscaling.internal.knative.dev/v1alpha1">autoscaling.internal.knative.dev/v1alpha1</h2>
|
||||
<p>
|
||||
</p>
|
||||
|
|
@ -3034,8 +2581,8 @@ ServiceStatus
|
|||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#serving.knative.dev/v1beta1.Configuration">Configuration</a>,
|
||||
<a href="#serving.knative.dev/v1.Configuration">Configuration</a>,
|
||||
<a href="#serving.knative.dev/v1beta1.Configuration">Configuration</a>,
|
||||
<a href="#serving.knative.dev/v1.ServiceSpec">ServiceSpec</a>)
|
||||
</p>
|
||||
<p>
|
||||
|
|
@ -3165,8 +2712,8 @@ Configuration. It might not be ready yet, for that use LatestReadyRevisionName.<
|
|||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#serving.knative.dev/v1beta1.Revision">Revision</a>,
|
||||
<a href="#serving.knative.dev/v1.Revision">Revision</a>,
|
||||
<a href="#serving.knative.dev/v1beta1.Revision">Revision</a>,
|
||||
<a href="#serving.knative.dev/v1alpha1.RevisionSpec">RevisionSpec</a>,
|
||||
<a href="#serving.knative.dev/v1.RevisionTemplateSpec">RevisionTemplateSpec</a>)
|
||||
</p>
|
||||
|
|
@ -3231,8 +2778,8 @@ be provided.</p>
|
|||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#serving.knative.dev/v1beta1.Revision">Revision</a>,
|
||||
<a href="#serving.knative.dev/v1.Revision">Revision</a>)
|
||||
<a href="#serving.knative.dev/v1.Revision">Revision</a>,
|
||||
<a href="#serving.knative.dev/v1beta1.Revision">Revision</a>)
|
||||
</p>
|
||||
<p>
|
||||
<p>RevisionStatus communicates the observed state of the Revision (from the controller).</p>
|
||||
|
|
@ -3611,8 +3158,8 @@ defaults).</p>
|
|||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#serving.knative.dev/v1beta1.Service">Service</a>,
|
||||
<a href="#serving.knative.dev/v1.Service">Service</a>)
|
||||
<a href="#serving.knative.dev/v1.Service">Service</a>,
|
||||
<a href="#serving.knative.dev/v1beta1.Service">Service</a>)
|
||||
</p>
|
||||
<p>
|
||||
<p>ServiceStatus represents the Status stanza of the Service resource.</p>
|
||||
|
|
@ -5652,7 +5199,460 @@ Ultimately all non-v1 fields will be deprecated.</p>
|
|||
</tbody>
|
||||
</table>
|
||||
<hr/>
|
||||
<h2 id="serving.knative.dev/v1beta1">serving.knative.dev/v1beta1</h2>
|
||||
<p>
|
||||
</p>
|
||||
Resource Types:
|
||||
<ul><li>
|
||||
<a href="#serving.knative.dev/v1beta1.Configuration">Configuration</a>
|
||||
</li><li>
|
||||
<a href="#serving.knative.dev/v1beta1.Revision">Revision</a>
|
||||
</li><li>
|
||||
<a href="#serving.knative.dev/v1beta1.Route">Route</a>
|
||||
</li><li>
|
||||
<a href="#serving.knative.dev/v1beta1.Service">Service</a>
|
||||
</li></ul>
|
||||
<h3 id="serving.knative.dev/v1beta1.Configuration">Configuration
|
||||
</h3>
|
||||
<p>
|
||||
<p>Configuration represents the “floating HEAD” of a linear history of Revisions.
|
||||
Users create new Revisions by updating the Configuration’s spec.
|
||||
The “latest created” revision’s name is available under status, as is the
|
||||
“latest ready” revision’s name.
|
||||
See also: <a href="https://github.com/knative/serving/blob/master/docs/spec/overview.md#configuration">https://github.com/knative/serving/blob/master/docs/spec/overview.md#configuration</a></p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>apiVersion</code></br>
|
||||
string</td>
|
||||
<td>
|
||||
<code>
|
||||
serving.knative.dev/v1beta1
|
||||
</code>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>kind</code></br>
|
||||
string
|
||||
</td>
|
||||
<td><code>Configuration</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>metadata</code></br>
|
||||
<em>
|
||||
<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#objectmeta-v1-meta">
|
||||
Kubernetes meta/v1.ObjectMeta
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
Refer to the Kubernetes API documentation for the fields of the
|
||||
<code>metadata</code> field.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>spec</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.ConfigurationSpec">
|
||||
ConfigurationSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<br/>
|
||||
<br/>
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<code>template</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.RevisionTemplateSpec">
|
||||
RevisionTemplateSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Template holds the latest specification for the Revision to be stamped out.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>status</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.ConfigurationStatus">
|
||||
ConfigurationStatus
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="serving.knative.dev/v1beta1.Revision">Revision
|
||||
</h3>
|
||||
<p>
|
||||
<p>Revision is an immutable snapshot of code and configuration. A revision
|
||||
references a container image. Revisions are created by updates to a
|
||||
Configuration.</p>
|
||||
<p>See also: <a href="https://github.com/knative/serving/blob/master/docs/spec/overview.md#revision">https://github.com/knative/serving/blob/master/docs/spec/overview.md#revision</a></p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>apiVersion</code></br>
|
||||
string</td>
|
||||
<td>
|
||||
<code>
|
||||
serving.knative.dev/v1beta1
|
||||
</code>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>kind</code></br>
|
||||
string
|
||||
</td>
|
||||
<td><code>Revision</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>metadata</code></br>
|
||||
<em>
|
||||
<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#objectmeta-v1-meta">
|
||||
Kubernetes meta/v1.ObjectMeta
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
Refer to the Kubernetes API documentation for the fields of the
|
||||
<code>metadata</code> field.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>spec</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.RevisionSpec">
|
||||
RevisionSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<br/>
|
||||
<br/>
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<code>PodSpec</code></br>
|
||||
<em>
|
||||
<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#podspec-v1-core">
|
||||
Kubernetes core/v1.PodSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>
|
||||
(Members of <code>PodSpec</code> are embedded into this type.)
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>containerConcurrency</code></br>
|
||||
<em>
|
||||
int64
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>ContainerConcurrency specifies the maximum allowed in-flight (concurrent)
|
||||
requests per container of the Revision. Defaults to <code>0</code> which means
|
||||
concurrency to the application is not limited, and the system decides the
|
||||
target concurrency for the autoscaler.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>timeoutSeconds</code></br>
|
||||
<em>
|
||||
int64
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>TimeoutSeconds holds the max duration the instance is allowed for
|
||||
responding to a request. If unspecified, a system default will
|
||||
be provided.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>status</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.RevisionStatus">
|
||||
RevisionStatus
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="serving.knative.dev/v1beta1.Route">Route
|
||||
</h3>
|
||||
<p>
|
||||
<p>Route is responsible for configuring ingress over a collection of Revisions.
|
||||
Some of the Revisions a Route distributes traffic over may be specified by
|
||||
referencing the Configuration responsible for creating them; in these cases
|
||||
the Route is additionally responsible for monitoring the Configuration for
|
||||
“latest ready revision” changes, and smoothly rolling out latest revisions.
|
||||
See also: <a href="https://github.com/knative/serving/blob/master/docs/spec/overview.md#route">https://github.com/knative/serving/blob/master/docs/spec/overview.md#route</a></p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>apiVersion</code></br>
|
||||
string</td>
|
||||
<td>
|
||||
<code>
|
||||
serving.knative.dev/v1beta1
|
||||
</code>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>kind</code></br>
|
||||
string
|
||||
</td>
|
||||
<td><code>Route</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>metadata</code></br>
|
||||
<em>
|
||||
<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#objectmeta-v1-meta">
|
||||
Kubernetes meta/v1.ObjectMeta
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
Refer to the Kubernetes API documentation for the fields of the
|
||||
<code>metadata</code> field.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>spec</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.RouteSpec">
|
||||
RouteSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Spec holds the desired state of the Route (from the client).</p>
|
||||
<br/>
|
||||
<br/>
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<code>traffic</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.TrafficTarget">
|
||||
[]TrafficTarget
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Traffic specifies how to distribute traffic over a collection of
|
||||
revisions and configurations.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>status</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.RouteStatus">
|
||||
RouteStatus
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Status communicates the observed state of the Route (from the controller).</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="serving.knative.dev/v1beta1.Service">Service
|
||||
</h3>
|
||||
<p>
|
||||
<p>Service acts as a top-level container that manages a Route and Configuration
|
||||
which implement a network service. Service exists to provide a singular
|
||||
abstraction which can be access controlled, reasoned about, and which
|
||||
encapsulates software lifecycle decisions such as rollout policy and
|
||||
team resource ownership. Service acts only as an orchestrator of the
|
||||
underlying Routes and Configurations (much as a kubernetes Deployment
|
||||
orchestrates ReplicaSets), and its usage is optional but recommended.</p>
|
||||
<p>The Service’s controller will track the statuses of its owned Configuration
|
||||
and Route, reflecting their statuses and conditions as its own.</p>
|
||||
<p>See also: <a href="https://github.com/knative/serving/blob/master/docs/spec/overview.md#service">https://github.com/knative/serving/blob/master/docs/spec/overview.md#service</a></p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>apiVersion</code></br>
|
||||
string</td>
|
||||
<td>
|
||||
<code>
|
||||
serving.knative.dev/v1beta1
|
||||
</code>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>kind</code></br>
|
||||
string
|
||||
</td>
|
||||
<td><code>Service</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>metadata</code></br>
|
||||
<em>
|
||||
<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#objectmeta-v1-meta">
|
||||
Kubernetes meta/v1.ObjectMeta
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
Refer to the Kubernetes API documentation for the fields of the
|
||||
<code>metadata</code> field.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>spec</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.ServiceSpec">
|
||||
ServiceSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<br/>
|
||||
<br/>
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<code>ConfigurationSpec</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.ConfigurationSpec">
|
||||
ConfigurationSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>
|
||||
(Members of <code>ConfigurationSpec</code> are embedded into this type.)
|
||||
</p>
|
||||
<p>ServiceSpec inlines an unrestricted ConfigurationSpec.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>RouteSpec</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.RouteSpec">
|
||||
RouteSpec
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>
|
||||
(Members of <code>RouteSpec</code> are embedded into this type.)
|
||||
</p>
|
||||
<p>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).</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>status</code></br>
|
||||
<em>
|
||||
<a href="#serving.knative.dev/v1.ServiceStatus">
|
||||
ServiceStatus
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<hr/>
|
||||
<p><em>
|
||||
Generated with <code>gen-crd-api-reference-docs</code>
|
||||
on git commit <code>96cffffa1</code>.
|
||||
on git commit <code>bf0a84876</code>.
|
||||
</em></p>
|
||||
|
|
|
|||
Loading…
Reference in New Issue