You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[ec2-controller] VPCPeeringConnection: options are read from the spec, not AWS #3171
Observed: an adopted CR has no accepterPeeringConnectionOptions, requesterPeeringConnectionOptions or peerVPCID, while AWS has both options set and returns the accepter VPC. Drift in the options is never detected.
Cause: the read hook builds both option sets from r.ko.Spec, not from the DescribeVpcPeeringConnections output. It also copies the accepter's AllowDNSResolutionFromRemoteVPC into AllowEgressFromLocalClassicLinkToRemoteVPC. Adoption backfills vpcID from RequesterVpcInfo, but not peerVPCID from AccepterVpcInfo.
Related: #2419 and #2480, closed: adoption failed on vpcID, fixed by the vpcID backfill.
Steps to reproduce
Create a peering connection with both options set and acceptRequest: true, then adopt it by ID with services.k8s.aws/adoption-policy: adopt and no spec.
Expected outcome
The options and peerVPCID are read from AWS, so the adopted spec has them and drift in the options is detected.
Hello @gobos12 👋 Thank you for opening an issue in ACK! A maintainer will triage this issue soon.
We encourage community contributions, so if you're interested in tackling this yourself or suggesting a solution, please check out our Contribution and Code of Conduct guidelines.
You can find more information about ACK on our website.
Activity
github-actions commentedon Nov 12, 2026
Hello @gobos12 👋 Thank you for opening an issue in ACK! A maintainer will triage this issue soon.
We encourage community contributions, so if you're interested in tackling this yourself or suggesting a solution, please check out our Contribution and Code of Conduct guidelines.
You can find more information about ACK on our website.