Skip to content
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

Add fully-private ACK pattern #1988

Closed
candonov opened this issue Aug 1, 2024 · 2 comments
Closed

Add fully-private ACK pattern #1988

candonov opened this issue Aug 1, 2024 · 2 comments

Comments

@candonov
Copy link
Contributor

candonov commented Aug 1, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

An ACK pattern showcasing how to install the ACK controllers in a fully private environment.

Describe the solution you would like

The pattern should include specifics on the fully private installation:

  1. Deploying an EKS cluster in a fully-private VPC
  2. Setting ECR pull trough cache to pull the ACK images trough a private ECR
  3. VPC endpoints for the services the controllers need to talk to
  4. Documentation on how controllers can communicate with global services that do not provide VPC endpoints such as IAM (setting a proxy and what controllers settings are needed to communicate trough the proxy)

Describe alternatives you have considered

None.

Additional context

This is one of 3 patterns for ACK
ack
├── basic
├── fully-private
└── cross-account

Copy link
Contributor

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Sep 26, 2024
Copy link
Contributor

github-actions bot commented Oct 6, 2024

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants