-
Notifications
You must be signed in to change notification settings - Fork 267
ACK EC2 Controller VPCEndpoint doesn't modify the aws object based on spec definition #2296
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
ACK EC2 Controller VPCEndpoint doesn't modify the aws object based on spec definition #2296
Comments
Thank you for reporting this issue! To help investigate further, could you please provide a few details:
|
Reconcile default resync seconds: 600
Same thing happened for the interface one. I retested today
|
|
Thank you for the details! I see that the controller will need custom update to handle the ModifyVpcEndpoint. I will bring this to the teams attention and get back to you. |
Hi @stefanescualexandrumihai, just updated the method for Next release for the controller will address the issue. |
…yVpcEndpoint` calls (#240) fixes aws-controllers-k8s/community#2296 Description of changes: Handle updates that require the `ModifyVpcEndpoint` API. Ensure that when fields such as `SubnetIDs`, `RouteTableIDs`, `PolicyDocument`, `PrivateDNSEnabled`, `SecurityGroupIDs`, `DNSOptions`, or `IPAddressType` change, the controller constructs and sends the corresponding Modify calls to AWS. By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Hi @stefanescualexandrumihai , The |
Thx so much! |
Uh oh!
There was an error while loading. Please reload this page.
AWS ACK EC2 Controller version : 1.3.1
The ec2 controller has featureGates.ResourceAdoption value set to true.
Kubernetes version v1.29.6
After the object adoption using the following manifest:
The spec was populated with this:
I did the same thing for a vpcendpoint of gateway type.
I removed the annotations:
services.k8s.aws/adoption-fields
andservices.k8s.aws/adoption-policy
.Afterwards, I tried to modify the subnetIDs by deleting one of them. The controller logged the following messages:
desired resource state has changed
andupdated resource
. However, in the aws console, the modification was not reflected. The same behaviour for a vpcendpoint of gateway type ( trying to delete one of the routetableIDs entries).Logs for the gateway type:
kubectl logs -n ack-ec2-controller ack-ec2-controller-5bc4889db9-m64m6 | grep astef8-sbx-va6-s3
I also tried to delete a routetableid/subnetid from aws console that was present in the object's spec, but the controller didn't add it back ( checked the aws console after a while )
The text was updated successfully, but these errors were encountered: