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]: can't get lbtargetgroups in v1.17.0 due to v1beta1/v1beta2 issue #1580

Open
1 task done
charlesmelby opened this issue Nov 29, 2024 · 1 comment
Open
1 task done
Labels

Comments

@charlesmelby
Copy link

charlesmelby commented Nov 29, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Affected Resource(s)

  • elbv2.aws.upbound.io/v1beta1 - LBTargetGroup
  • elbv2.aws.upbound.io/v1beta2 - LBTargetGroup

Resource MRs required to reproduce the bug

apiVersion: elbv2.aws.upbound.io/v1beta1
kind: LBTargetGroup
metadata:
name: proxy-ingress
spec:
providerConfigRef:
name: aws
forProvider:
name: proxy-ingress
region: ap-northeast-1
port: 443
protocol: HTTPS
targetType: instance
vpcId: ************

Steps to Reproduce

kubectl get lbtargetgroups

What happened?

It can't fetch the targets groups (or individual records) due to conversion webhook failure.

Relevant Error Output Snippet

Error from server: conversion webhook for elbv2.aws.upbound.io/v1beta1, Kind=LBTargetGroup failed: cannot convert from the spoke version "v1beta1" to the hub version "v1beta2": cannot apply the PavedConversion for the "aws_lb_target_group" object: failed to convert the source map in mode "toEmbeddedObject" with source API version "*", target API version "v1beta2": value at the field path stickiness must be []any, not "map[string]interface {}"

Crossplane Version

1.18.0

Provider Version

1.17.0

Kubernetes Version

v1.28.9+rke2r1

Kubernetes Distribution

rke2

Additional Info

The AWS target group IS successfully created. However,

  • I can't get the target group information or status
  • targetGroupArnRef in LBTargetGroupAttachment never gets filled in, so I had to manually copy targetGroupArn from AWS instead
@charlesmelby charlesmelby added bug Something isn't working needs:triage labels Nov 29, 2024
@turkenf
Copy link
Collaborator

turkenf commented Nov 30, 2024

Hi @charlesmelby,

I could not reproduce the issue. Do you encounter this issue constantly or sporadically? Could you please restart the relevant pod and check again?

> k get lbtargetgroup.v1beta1.elbv2.aws.upbound.io/test
NAME   SYNCED   READY   EXTERNAL-NAME                                                                                    AGE
test   True     True    arn:aws:elasticloadbalancing:us-west-1:153891904029:targetgroup/proxy-ingress/6047e967428e9f70   64s
> k get lbtargetgroup.v1beta2.elbv2.aws.upbound.io/test
NAME   SYNCED   READY   EXTERNAL-NAME                                                                                    AGE
test   True     True    arn:aws:elasticloadbalancing:us-west-1:153891904029:targetgroup/proxy-ingress/6047e967428e9f70   70s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants