Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: LBTargetGroupAttachment to use matchlabelSelector for targetId #1643

Open
1 task done
sterziev88 opened this issue Jan 17, 2025 · 0 comments
Open
1 task done
Labels
bug Something isn't working needs:triage

Comments

@sterziev88
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Affected Resource(s)

elbv2.aws.upbound.io/v1beta1 - LBTargetGroupAttachment

Resource MRs required to reproduce the bug

apiVersion: elbv2.aws.upbound.io/v1beta1
kind: LBTargetGroupAttachment
metadata:
labels:
test: test
name: test
spec:
forProvider:
port: 80
region: eu-west-1
targetGroupArnSelector:
matchLabels:
trg: test
targetId: xxxxxxx

Steps to Reproduce

Create an ec2 with alb ( + target-group and listener ) and then attach the ec2 to the target-group through LBTargetGroupAttachment.

What happened?

I want to be able to attach the ec2 with matchlabelSelector because otherwise I have to wait my instance to start and obtain it ID. What if I want to change something in my ec2. Every time with every change I have to change the code? Will be great if we can use matchlabelSelector and crosspplane to be able to obtain that new instance and replace the old one .

Relevant Error Output Snippet

None

Crossplane Version

1.14.2

Provider Version

1.18.3

Kubernetes Version

1.31

Kubernetes Distribution

EKS

Additional Info

No response

@sterziev88 sterziev88 added bug Something isn't working needs:triage labels Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs:triage
Projects
None yet
Development

No branches or pull requests

1 participant