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.
Information about the CloudWatch alarms. See below.
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.
Reference to a LBTargetGroup in elbv2 to populate targetGroupArn.
Policies for referencing.
Selector for a LBTargetGroup in elbv2 to populate targetGroupArn.
Policies for selection.
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.
The ECS Service Connect configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. See below.
The log configuration for the container. See below.
The list of Service Connect service objects. See below.
Service discovery registries for the service. The maximum number of service_registries blocks is 1. See below.
Reference to a TaskDefinition to populate taskDefinition.
Policies for referencing.
Selector for a TaskDefinition to populate taskDefinition.
Policies for selection.
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.
Information about the CloudWatch alarms. See below.
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.
Reference to a LBTargetGroup in elbv2 to populate targetGroupArn.
Policies for referencing.
Selector for a LBTargetGroup in elbv2 to populate targetGroupArn.
Policies for selection.
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.
The ECS Service Connect configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. See below.
The log configuration for the container. See below.
The list of Service Connect service objects. See below.
Service discovery registries for the service. The maximum number of service_registries blocks is 1. See below.
Reference to a TaskDefinition to populate taskDefinition.
Policies for referencing.
Selector for a TaskDefinition to populate taskDefinition.
Policies for selection.
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.
Information about the CloudWatch alarms. See below.
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.
Configuration block for deployment controller configuration. See below.
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.
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.
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.
The ECS Service Connect configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. See below.
The log configuration for the container. See below.
The list of Service Connect service objects. See below.
Service discovery registries for the service. The maximum number of service_registries blocks is 1. See below.
Conditions of the resource.
example-service
apiVersion: ecs.aws.upbound.io/v1beta1
kind: Service
metadata:
annotations:
meta.upbound.io/example-id: ecs/v1beta1/service-static-cluster
upjet.upbound.io/manual-intervention: Resource stuck in update loop, see
https://github.com/upbound/provider-aws/issues/585
labels:
testing.upbound.io/example-name: example-service
name: example-service
spec:
forProvider:
cluster: example-cluster-service
launchType: EC2
propagateTags: TASK_DEFINITION
region: us-west-1
taskDefinitionSelector:
matchLabels:
testing.upbound.io/example-name: example-service-definition
sample-service
apiVersion: ecs.aws.upbound.io/v1beta1
kind: Service
metadata:
annotations:
meta.upbound.io/example-id: ecs/v1beta1/service
upjet.upbound.io/manual-intervention: Resourrce stuck in update loop
name: sample-service
spec:
forProvider:
clusterSelector:
matchLabels:
testing.upbound.io/example-name: example-cluster
launchType: EC2
propagateTags: TASK_DEFINITION
region: us-west-1
taskDefinitionSelector:
matchLabels:
testing.upbound.io/example-name: example-definition
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.