Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
K
knative-docs
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
COUTURIER Christophe
knative-docs
Commits
d35fb3e6
Commit
d35fb3e6
authored
5 years ago
by
Lv Jiawei
Committed by
Knative Prow Robot
5 years ago
Browse files
Options
Downloads
Patches
Plain Diff
update service resource spec url (#2031)
parent
2500dffa
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/serving/README.md
+4
-4
4 additions, 4 deletions
docs/serving/README.md
with
4 additions
and
4 deletions
docs/serving/README.md
+
4
−
4
View file @
d35fb3e6
...
...
@@ -15,22 +15,22 @@ Knative Serving defines a set of objects as Kubernetes Custom Resource
Definitions (CRDs). These objects are used to define and control how your
serverless workload behaves on the cluster:
-
[
Service
](
https://github.com/knative/
serving
/blob/master/docs/s
pec/spec
.md#service
)
:
-
[
Service
](
https://github.com/knative/
docs
/blob/master/docs/s
erving/spec/knative-api-specification-1.0
.md#service
)
:
The
`service.serving.knative.dev`
resource automatically manages the whole
lifecycle of your workload. It controls the creation of other objects to
ensure that your app has a route, a configuration, and a new revision for each
update of the service. Service can be defined to always route traffic to the
latest revision or to a pinned revision.
-
[
Route
](
https://github.com/knative/
serving
/blob/master/docs/s
pec/spec
.md#route
)
:
-
[
Route
](
https://github.com/knative/
docs
/blob/master/docs/s
erving/spec/knative-api-specification-1.0
.md#route
)
:
The
`route.serving.knative.dev`
resource maps a network endpoint to one or
more revisions. You can manage the traffic in several ways, including
fractional traffic and named routes.
-
[
Configuration
](
https://github.com/knative/
serving
/blob/master/docs/s
pec/spec
.md#configuration
)
:
-
[
Configuration
](
https://github.com/knative/
docs
/blob/master/docs/s
erving/spec/knative-api-specification-1.0
.md#configuration
)
:
The
`configuration.serving.knative.dev`
resource maintains the desired state
for your deployment. It provides a clean separation between code and
configuration and follows the Twelve-Factor App methodology. Modifying a
configuration creates a new revision.
-
[
Revision
](
https://github.com/knative/
serving
/blob/master/docs/s
pec/spec
.md#revision
)
:
-
[
Revision
](
https://github.com/knative/
docs
/blob/master/docs/s
erving/spec/knative-api-specification-1.0
.md#revision
)
:
The
`revision.serving.knative.dev`
resource is a point-in-time snapshot of the
code and configuration for each modification made to the workload. Revisions
are immutable objects and can be retained for as long as useful. Knative
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment