Service is the Schema for the Services API. A Cloud Run service has a unique endpoint and autoscales containers.
Type
CRD
Group
cloudrun.gcp.upbound.io
Version
v1beta1
apiVersion: cloudrun.gcp.upbound.io/v1beta1
kind: Service
ServiceSpec defines the desired state of Service
No description provided.
Optional metadata for this Revision, including labels and annotations. Name will be generated by the Configuration. To set minimum instances for this revision, use the "autoscaling.knative.dev/minScale" annotation key. To set maximum instances for this revision, use the "autoscaling.knative.dev/maxScale" annotation key. To set Cloud SQL connections for the revision, use the "run.googleapis.com/cloudsql-instances" annotation key. Structure is documented below.
Reference to a Project in cloudplatform to populate namespace.
Policies for referencing.
Selector for a Project in cloudplatform to populate namespace.
Policies for selection.
template holds the latest specification for the Revision to be stamped out. The template references the container image, and may also include labels and annotations that should be attached to the Revision. To correlate a Revision, and/or to force a Revision to be created when the spec doesn't otherwise change, a nonce label may be provided in the template metadata. For more details, see: https://github.com/knative/serving/blob/main/docs/client-conventions.md#associate-modifications-with-revisions Cloud Run does not currently support referencing a build that is responsible for materializing the container image from source. Structure is documented below.
Optional metadata for this Revision, including labels and annotations. Name will be generated by the Configuration. To set minimum instances for this revision, use the "autoscaling.knative.dev/minScale" annotation key. To set maximum instances for this revision, use the "autoscaling.knative.dev/maxScale" annotation key. To set Cloud SQL connections for the revision, use the "run.googleapis.com/cloudsql-instances" annotation key. Structure is documented below.
RevisionSpec holds the desired state of the Revision (from the client). Structure is documented below.
Containers defines the unit of execution for this Revision. Structure is documented below.
Arguments to the entrypoint. The docker image's CMD is used if this is not provided.
Entrypoint array. Not executed within a shell. The docker image's ENTRYPOINT is used if this is not provided.
List of environment variables to set in the container. Structure is documented below.
Source for the environment variable's value. Only supports secret_key_ref. Structure is documented below.
Selects a key (version) of a secret in Secret Manager. Structure is documented below.
Reference to a Secret in secretmanager to populate name.
Policies for referencing.
Selector for a Secret in secretmanager to populate name.
Policies for selection.
List of sources to populate environment variables in the container. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Structure is documented below.
The ConfigMap to select from. Structure is documented below.
The Secret to select from. Structure is documented below.
The Secret to select from. Structure is documented below.
The Secret to select from. Structure is documented below.
Periodic probe of container liveness. Container will be restarted if the probe fails. Structure is documented below.
HttpGet specifies the http request to perform. Structure is documented below.
List of open ports in the container. Structure is documented below.
Startup probe of application within the container. All other probes are disabled if a startup probe is provided, until it succeeds. Container will not be added to service endpoints if the probe fails. Structure is documented below.
HttpGet specifies the http request to perform. Structure is documented below.
TcpSocket specifies an action involving a TCP port. Structure is documented below.
Volume represents a named volume in a container. Structure is documented below.
The secret's value will be presented as the content of a file whose name is defined in the item path. If no items are defined, the name of the file is the secret_name. Structure is documented below.
If unspecified, the volume will expose a file whose name is the secret_name. If specified, the key will be used as the version to fetch from Cloud Secret Manager and the path will be the name of the file exposed in the volume. When items are defined, they must specify a key and a path. Structure is documented below.
Reference to a Secret in secretmanager to populate secretName.
Policies for referencing.
Selector for a Secret in secretmanager to populate secretName.
Policies for selection.
(Output) Traffic specifies how to distribute traffic over a collection of Knative Revisions and Configurations Structure is documented below.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
Optional metadata for this Revision, including labels and annotations. Name will be generated by the Configuration. To set minimum instances for this revision, use the "autoscaling.knative.dev/minScale" annotation key. To set maximum instances for this revision, use the "autoscaling.knative.dev/maxScale" annotation key. To set Cloud SQL connections for the revision, use the "run.googleapis.com/cloudsql-instances" annotation key. Structure is documented below.
Reference to a Project in cloudplatform to populate namespace.
Policies for referencing.
Selector for a Project in cloudplatform to populate namespace.
Policies for selection.
template holds the latest specification for the Revision to be stamped out. The template references the container image, and may also include labels and annotations that should be attached to the Revision. To correlate a Revision, and/or to force a Revision to be created when the spec doesn't otherwise change, a nonce label may be provided in the template metadata. For more details, see: https://github.com/knative/serving/blob/main/docs/client-conventions.md#associate-modifications-with-revisions Cloud Run does not currently support referencing a build that is responsible for materializing the container image from source. Structure is documented below.
Optional metadata for this Revision, including labels and annotations. Name will be generated by the Configuration. To set minimum instances for this revision, use the "autoscaling.knative.dev/minScale" annotation key. To set maximum instances for this revision, use the "autoscaling.knative.dev/maxScale" annotation key. To set Cloud SQL connections for the revision, use the "run.googleapis.com/cloudsql-instances" annotation key. Structure is documented below.
RevisionSpec holds the desired state of the Revision (from the client). Structure is documented below.
Containers defines the unit of execution for this Revision. Structure is documented below.
Arguments to the entrypoint. The docker image's CMD is used if this is not provided.
Entrypoint array. Not executed within a shell. The docker image's ENTRYPOINT is used if this is not provided.
List of environment variables to set in the container. Structure is documented below.
Source for the environment variable's value. Only supports secret_key_ref. Structure is documented below.
Selects a key (version) of a secret in Secret Manager. Structure is documented below.
Reference to a Secret in secretmanager to populate name.
Policies for referencing.
Selector for a Secret in secretmanager to populate name.
Policies for selection.
List of sources to populate environment variables in the container. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Structure is documented below.
The ConfigMap to select from. Structure is documented below.
The Secret to select from. Structure is documented below.
The Secret to select from. Structure is documented below.
The Secret to select from. Structure is documented below.
Periodic probe of container liveness. Container will be restarted if the probe fails. Structure is documented below.
HttpGet specifies the http request to perform. Structure is documented below.
List of open ports in the container. Structure is documented below.
Startup probe of application within the container. All other probes are disabled if a startup probe is provided, until it succeeds. Container will not be added to service endpoints if the probe fails. Structure is documented below.
HttpGet specifies the http request to perform. Structure is documented below.
TcpSocket specifies an action involving a TCP port. Structure is documented below.
Volume represents a named volume in a container. Structure is documented below.
The secret's value will be presented as the content of a file whose name is defined in the item path. If no items are defined, the name of the file is the secret_name. Structure is documented below.
If unspecified, the volume will expose a file whose name is the secret_name. If specified, the key will be used as the version to fetch from Cloud Secret Manager and the path will be the name of the file exposed in the volume. When items are defined, they must specify a key and a path. Structure is documented below.
Reference to a Secret in secretmanager to populate secretName.
Policies for referencing.
Selector for a Secret in secretmanager to populate secretName.
Policies for selection.
(Output) Traffic specifies how to distribute traffic over a collection of Knative Revisions and Configurations Structure is documented below.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
ServiceStatus defines the observed state of Service.
No description provided.
Optional metadata for this Revision, including labels and annotations. Name will be generated by the Configuration. To set minimum instances for this revision, use the "autoscaling.knative.dev/minScale" annotation key. To set maximum instances for this revision, use the "autoscaling.knative.dev/maxScale" annotation key. To set Cloud SQL connections for the revision, use the "run.googleapis.com/cloudsql-instances" annotation key. Structure is documented below.
The current status of the Service. Structure is documented below.
(Output) Traffic specifies how to distribute traffic over a collection of Knative Revisions and Configurations Structure is documented below.
template holds the latest specification for the Revision to be stamped out. The template references the container image, and may also include labels and annotations that should be attached to the Revision. To correlate a Revision, and/or to force a Revision to be created when the spec doesn't otherwise change, a nonce label may be provided in the template metadata. For more details, see: https://github.com/knative/serving/blob/main/docs/client-conventions.md#associate-modifications-with-revisions Cloud Run does not currently support referencing a build that is responsible for materializing the container image from source. Structure is documented below.
Optional metadata for this Revision, including labels and annotations. Name will be generated by the Configuration. To set minimum instances for this revision, use the "autoscaling.knative.dev/minScale" annotation key. To set maximum instances for this revision, use the "autoscaling.knative.dev/maxScale" annotation key. To set Cloud SQL connections for the revision, use the "run.googleapis.com/cloudsql-instances" annotation key. Structure is documented below.
RevisionSpec holds the desired state of the Revision (from the client). Structure is documented below.
Containers defines the unit of execution for this Revision. Structure is documented below.
Arguments to the entrypoint. The docker image's CMD is used if this is not provided.
Entrypoint array. Not executed within a shell. The docker image's ENTRYPOINT is used if this is not provided.
List of environment variables to set in the container. Structure is documented below.
List of sources to populate environment variables in the container. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Structure is documented below.
The ConfigMap to select from. Structure is documented below.
The Secret to select from. Structure is documented below.
The Secret to select from. Structure is documented below.
The Secret to select from. Structure is documented below.
Periodic probe of container liveness. Container will be restarted if the probe fails. Structure is documented below.
HttpGet specifies the http request to perform. Structure is documented below.
List of open ports in the container. Structure is documented below.
Startup probe of application within the container. All other probes are disabled if a startup probe is provided, until it succeeds. Container will not be added to service endpoints if the probe fails. Structure is documented below.
HttpGet specifies the http request to perform. Structure is documented below.
TcpSocket specifies an action involving a TCP port. Structure is documented below.
Volume represents a named volume in a container. Structure is documented below.
The secret's value will be presented as the content of a file whose name is defined in the item path. If no items are defined, the name of the file is the secret_name. Structure is documented below.
If unspecified, the volume will expose a file whose name is the secret_name. If specified, the key will be used as the version to fetch from Cloud Secret Manager and the path will be the name of the file exposed in the volume. When items are defined, they must specify a key and a path. Structure is documented below.
(Output) Traffic specifies how to distribute traffic over a collection of Knative Revisions and Configurations Structure is documented below.
Conditions of the resource.
default-svc
apiVersion: cloudrun.gcp.upbound.io/v1beta1
kind: Service
metadata:
annotations:
meta.upbound.io/example-id: cloudrun/v1beta1/domainmapping
labels:
testing.upbound.io/example-name: default-svc
name: default-svc
spec:
forProvider:
location: us-central1
metadata:
- namespace: official-provider-testing
template:
- spec:
- containers:
- image: us-docker.pkg.dev/cloudrun/container/hello
cloudrun-service
apiVersion: cloudrun.gcp.upbound.io/v1beta1
kind: Service
metadata:
annotations:
meta.upbound.io/example-id: cloudrun/v1beta1/service
labels:
testing.upbound.io/example-name: cloudrun-service
name: cloudrun-service
spec:
forProvider:
location: us-central1
template:
- spec:
- containers:
- image: us-docker.pkg.dev/cloudrun/container/hello
traffic:
- latestRevision: true
percent: 100
trigger
apiVersion: cloudrun.gcp.upbound.io/v1beta1
kind: Service
metadata:
annotations:
meta.upbound.io/example-id: eventarc/v1beta1/trigger
labels:
testing.upbound.io/example-name: trigger
name: trigger
spec:
forProvider:
location: us-central1
template:
- spec:
- containers:
- image: us-docker.pkg.dev/cloudrun/container/hello
traffic:
- latestRevision: true
percent: 100
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.