Package-level declarations
Types
Resource to hold the state and status of a user's domain mapping. To get more information about DomainMapping, see:
Resource to hold the state and status of a user's domain mapping. To get more information about DomainMapping, see:
Builder for DomainMappingArgs.
Builder for DomainMapping.
Three different resources help you manage your IAM policy for Cloud Run Service. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Cloud Run Service. Each of these resources serves a different use case:
Builder for IamBindingArgs.
Builder for IamBinding.
Three different resources help you manage your IAM policy for Cloud Run Service. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Cloud Run Service. Each of these resources serves a different use case:
Builder for IamMemberArgs.
Builder for IamMember.
Three different resources help you manage your IAM policy for Cloud Run Service. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Cloud Run Service. Each of these resources serves a different use case:
Builder for IamPolicyArgs.
Builder for IamPolicy.
Service acts as a top-level container that manages a set of Routes and Configurations 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). The Service's controller will track the statuses of its owned Configuration and Route, reflecting their statuses and conditions as its own. See also: https://github.com/knative/specs/blob/main/specs/serving/overview.md To get more information about Service, see:
Service acts as a top-level container that manages a set of Routes and Configurations 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). The Service's controller will track the statuses of its owned Configuration and Route, reflecting their statuses and conditions as its own. See also: https://github.com/knative/specs/blob/main/specs/serving/overview.md To get more information about Service, see:
Builder for ServiceArgs.
Builder for Service.