Service is the Schema for the Services API. Provides an ECS service.
Type
CRD
Group
ecs.aws.upbound.io
Version
v1beta1
apiVersion: ecs.aws.upbound.io/v1beta1
kind: Service
ServiceSpec defines the desired state of Service
No description provided.
Capacity provider strategies to use for the service. Can be one or more. These can be updated without destroying and recreating the service only if force_new_deployment = true and not changing from 0 capacity_provider_strategy blocks to greater than 0, or vice versa. See below.
Reference to a Cluster to populate cluster.
Policies for referencing.
Selector for a Cluster to populate cluster.
Policies for selection.
Configuration block for deployment controller configuration. See below.
Reference to a Role in iam to populate iamRole.
Policies for referencing.
Selector for a Role in iam to populate iamRole.
Policies for selection.
Configuration block for load balancers. See below.
Network configuration for the service. This parameter is required for task definitions that use the awsvpc network mode to receive their own Elastic Network Interface, and it is not supported for other network modes. See below.
References to SecurityGroup in ec2 to populate securityGroups.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate securityGroups.
Policies for selection.
Security groups associated with the task or service. If you do not specify a security group, the default security group for the VPC is used.
References to Subnet in ec2 to populate subnets.
Policies for referencing.
Selector for a list of Subnet in ec2 to populate subnets.
Policies for selection.
Subnets associated with the task or service.
Service level strategy rules that are taken into consideration during task placement. List from top to bottom in order of precedence. Updates to this configuration will take effect next task deployment unless force_new_deployment is enabled. The maximum number of ordered_placement_strategy blocks is 5. See below.
Rules that are taken into consideration during task placement. Updates to this configuration will take effect next task deployment unless force_new_deployment is enabled. Maximum number of placement_constraints is 10. See below.
Service discovery registries for the service. The maximum number of service_registries blocks is 1. See below.
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
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.
Conditions of the resource.
sample-service
apiVersion: ecs.aws.upbound.io/v1beta1
kind: Service
metadata:
annotations:
upjet.upbound.io/manual-intervention: This resource requires manual intervention
for adding task definition revision. Otherwise, resource will be updated
to use latest revision.
name: sample-service
spec:
forProvider:
cluster: example
launchType: EC2
propagateTags: TASK_DEFINITION
region: us-west-1
taskDefinition: sampleservice
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.