Open enobil opened 2 months ago
@enobil
We currently don't support to partially manage a LB resource.
The --external-managed-tags=custom-managed
commandLine flag is for another feature, where the controller will keep the AWS tag custom-managed
on AWS resources it created, otherwise it will reconcile all tags on AWS resources.
/kind feature Support to partially manage an LB resource.
Describe the bug My purpose is creating some additional NLB listener on port 22 on an NLB created by AWS LB ingress controller. I'm using
external-managed-tags
configuration to avoid reconciliation deleting this additional NLB listener.I'm using external-managed-tags configuration such as
--external-managed-tags=custom-managed
. I verified the arguments are specified to the pod successfully:I made sure my custom NLB listener has a tag with name "custom-managed" with value "true". However the ingress controller reconciliation still deletes the custom NLB listener. I can see the pod log like this from the ingress controller pod log:
Steps to reproduce Install aws load balancer ingress controller via
aws-load-balancer-controller
helm chartPlease pay attention to
--set "externalManagedTags[0]=custom-managed" \
part. I also tried as--set "externalManagedTags=custom-managed" \
that gives the same result too. I also reduced sync period to 10 minutes to not wait for 10 hours everytime I test.Then create a NLB by creating a service like below
So this NLB by default will only have listeners for port 80 and port 443.
Then create the additional listener on port 22. I use CloudFormation like below but it doesn't matter how it is created, it can be created with AWS CLI or AWS console too:
After this CFN deployment I run a small AWS CLI script similar to below essentially
Then I verified the tag is properly set on the port 22 listener:
Wait for 10-20 minutes, until the next time reconciliation happens.
Port 22 listener will be gone.
Expected outcome Port 22 listener in the reproduction steps shouldn't be deleted as per documentation, as per the purpose of this
external-managed-tags
configuration feature.Environment
Additional Context: