Skip to content

Support for TransitGatewayAttachment resource #1865

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

Open
mattzech opened this issue Jul 31, 2023 · 7 comments
Open

Support for TransitGatewayAttachment resource #1865

mattzech opened this issue Jul 31, 2023 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. service/ec2 Indicates issues or PRs that are related to ec2-controller. target/q2-2025 Issues scheduled for Q2 in 2025

Comments

@mattzech
Copy link

mattzech commented Jul 31, 2023

What is the URL of the document?

Go docs

Also, ACK tutorials

Which section(s) is the issue in?

TransitGateway creation in the VPC tutorial

What needs fixing?

It is very unclear how to attach a TransitGateway to a subnet/vpc using a TransitGatewayAttachment. Since the TGA resource is not an object, it cannot be created in the same way as a TransitGateway in Golang. This doc request is also a question of how this is supposed to be handled.

Additional context

I am wondering what resources are required in order to properly attach a Transit Gateway to a VPC. I am also wondering if there is a reason the TransitGatewayAttachment is not an object in Go.

Thanks!

@a-hilaly a-hilaly added service/ec2 Indicates issues or PRs that are related to ec2-controller. kind/feature Categorizes issue or PR as related to a new feature. labels Jul 31, 2023
@a-hilaly
Copy link
Member

/cc @aws-controllers-k8s/ec2-maintainer

@ack-bot
Copy link
Collaborator

ack-bot commented Jan 27, 2024

Issues go stale after 180d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 60d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale

@ack-prow ack-prow bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 27, 2024
@a-hilaly a-hilaly removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 28, 2024
@laiminhtrung1997
Copy link

Is there any news on this? How can I create Transit Gateway Attachment with ACK?

@ack-bot
Copy link
Collaborator

ack-bot commented Dec 24, 2024

Issues go stale after 180d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 60d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale

@ack-prow ack-prow bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 24, 2024
@a-hilaly a-hilaly removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 2, 2025
@a-hilaly
Copy link
Member

a-hilaly commented Jan 2, 2025

For the ec2 controller we have documentation for all the supported resources here, PTAL https://aws-controllers-k8s.github.io/community/reference/ec2/v1alpha1/transitgateway/

@eqe-aws eqe-aws added target/q1-2025 Issues scheduled for Q1 in 2025 q2-205 and removed target/q1-2025 Issues scheduled for Q1 in 2025 labels Mar 12, 2025
@jlbutler jlbutler added target/q2-2025 Issues scheduled for Q2 in 2025 and removed q2-205 labels Mar 18, 2025
@jlbutler jlbutler changed the title Need clear TransitGatewayAttachment docs Support for TransitGatewayAttachment resource Mar 18, 2025
@jlbutler
Copy link
Contributor

This issue was tracking docs gap, but we need a resource for TransitGatewayAttachment

@michaelhtm
Copy link
Member

Hello! After looking into this further, Would it be a better UX to not create a new resource, but instead define which VPCs you would want to attach to a transitGateway?
This would mean we would add a new field, maybe name it attachments. Here's an example:

apiVersion: ec2.services.k8s.aws/v1alpha1
kind: TransitGateway
metadata:
  name: $TGW_NAME
spec:
  attachments:
  - vpcID: $VPC_ID
    options:
      applianceModeSupport: enable
      dnsSupport: enable
      ipv6Support: enable
      dnsSupport: enable
      securityGroupReferencingSupport: enable
    subnetIDs:
    - $SUBNET_ID
  tags:
    - key: $TAG_KEY
      value: $TAG_VALUE

The drawbacks of this solution would be, you can't tag a specific transitgateway attachment..
but on the plus side, there would be less resources to manage..

cc: @jas-nik @laiminhtrung1997 @mattzech @jlbutler @a-hilaly @rushmash91

ack-prow bot pushed a commit to aws-controllers-k8s/ec2-controller that referenced this issue Mar 28, 2025
Issue [#1865](aws-controllers-k8s/community#1865)

Description of changes:
With these changes we are supporting TransitGatewayVPCAttachment resources.
This resource can reference TrasitGatewayID, VPCID, and SubnetID by their resource 
name. Also adding e2e tests.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. service/ec2 Indicates issues or PRs that are related to ec2-controller. target/q2-2025 Issues scheduled for Q2 in 2025
Projects
None yet
Development

No branches or pull requests

7 participants