Closed daniel-maganto closed 1 month ago
Do you have any workarounds for this issue?
Yes, in the end instead of using MatchLabels we have added the names directly:
- base:
apiVersion: ecs.aws.upbound.io/v1beta1
kind: Service
spec:
managementPolicies: ["Observe", "Create", "Update", "Delete"]
forProvider:
cluster: ""
launchType: FARGATE
loadBalancer:
- containerName: ""
containerPort: 8080
targetGroupArn: ""
networkConfiguration:
- securityGroups:
- null
subnets: ""
propagateTags: TASK_DEFINITION
region: ""
taskDefinitionRef:
name: ""
initProvider: {}
name: service
patches:
- patchSetName: common-parameters
type: PatchSet
- fromFieldPath: spec.parameters.autoscaling.minCapacity
toFieldPath: spec.initProvider.desiredCount
type: FromCompositeFieldPath
- fromFieldPath: serviceSubnets
toFieldPath: spec.forProvider.networkConfiguration[0].subnets
type: FromEnvironmentFieldPath
- fromFieldPath: spec.parameters.family
toFieldPath: spec.forProvider.loadBalancer[0].containerName
type: FromCompositeFieldPath
- fromFieldPath: spec.parameters.family
toFieldPath: metadata.name
type: FromCompositeFieldPath
- patchSetName: manage-resource-name
type: PatchSet
- fromFieldPath: securityGroupECS
toFieldPath: spec.forProvider.networkConfiguration[0].securityGroups[0]
type: FromEnvironmentFieldPath
- combine:
strategy: string
string:
fmt: '%s-%s-%s'
variables:
- fromFieldPath: spec.parameters.family
- fromFieldPath: spec.resourceConfig.env
- fromFieldPath: spec.parameters.task_id
toFieldPath: spec.forProvider.taskDefinitionRef.name
type: CombineFromComposite
- fromFieldPath: status.targetGroupArn
policy:
fromFieldPath: Required
toFieldPath: spec.forProvider.loadBalancer[0].targetGroupArn
type: FromCompositeFieldPath
- combine:
strategy: string
string:
fmt: '%s-%s'
variables:
- fromFieldPath: spec.resourceConfig.tenant
- fromFieldPath: spec.parameters.clusterName
toFieldPath: spec.forProvider.cluster
type: CombineFromComposite
readinessChecks:
- matchCondition:
status: "True"
type: Ready
type: MatchCondition
- matchCondition:
status: "True"
type: Synced
type: MatchCondition
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale
. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
This issue is being closed since there has been no activity for 14 days since marking it as stale
. If you still need help, feel free to comment or reopen the issue!
Is there an existing issue for this?
Affected Resource(s)
ecs.aws.upbound.io/v1beta1 - Service
Resource MRs required to reproduce the bug
Steps to Reproduce
Using the above composition when it creates the resources Service it stuck in the following state:
What happened?
If I try to create the resource outside of composition, it works success:
Relevant Error Output Snippet
Crossplane Version
1.14.5
Provider Version
0.47.1
Kubernetes Version
v1.28.2
Kubernetes Distribution
EKS
Additional Info
No response