Skip to content

[ec2-controller] CapacityReservation: availabilityZoneID differs on every reconcile #3165

Open

Description

@gobos12

Describe the bug

Unset availabilityZoneID differs from AWS on every reconcile. Found by capacity-reservation, in its controller logs.

Observed: with availabilityZoneID unset, every reconcile's diff includes Spec.AvailabilityZoneID: A: null, B: usw2-az2, and calls ModifyCapacityReservation.

Cause: the field is read back, and generator.yaml doesn't late-initialize it.

Open aws-controllers-k8s/ec2-controller#377 late-initializes the field.

Steps to reproduce

Create a CapacityReservation without availabilityZoneID, then update it. Each reconcile logs the diff in the controller's logs.

Expected outcome

Once created, a CapacityReservation without availabilityZoneID shows no diff.

Environment

  • Kubernetes version: 1.35
  • Using EKS (yes/no), if so version? Yes, 1.35
  • AWS service targeted (S3, RDS, etc.): EC2
  • ec2-controller v1.24.0, ACK runtime v0.68.0, us-west-2

Activity

  1. github-actions commented on Nov 12, 2026

    @github-actions

    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.

  2. added
    kind/bugCategorizes issue or PR as related to a bug.
    service/ec2Indicates issues or PRs that are related to ec2-controller.
    on Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/drift-remediationIssues or PRs related to drift remediation.kind/bugCategorizes issue or PR as related to a bug.service/ec2Indicates issues or PRs that are related to ec2-controller.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions