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

[Feature]: Allow to reuse parts of existing infrastructure #381

Open
pli01 opened this issue Oct 25, 2024 · 1 comment
Open

[Feature]: Allow to reuse parts of existing infrastructure #381

pli01 opened this issue Oct 25, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@pli01
Copy link

pli01 commented Oct 25, 2024

Explain problem to solve

Need to reuse part of existing pre deployed infrastructure with cluster-api Outscale deployment:

  • reuse infrastructure resources (VPC, LB, subnet, nat, igw, public IP, bastion ..)
  • to improve deployment time
  • to reduce cost

Describe the solution you would like

Cluster-api provider outscale need to support the following:
reuse infrastructure parts, with ID or TAG

  • preexisting VPC
  • preexisting subnet (public or private)
  • preexisting NAT or IGW
  • preexisting LB
  • preexisting bastion

Additional context

We need to deploy with multiple providers and predefined topology

for example, others cluster-api provider support it :

Environment

- Kubernetes version: (use `kubectl version`):
- OS (e.g. from `/etc/os-release`):
- Kernel (e.g. `uname -a`):
- cluster-api-provider-outscale version:
- cluster-api version:
- Install tools:
- Kubernetes Distribution:
- Kubernetes Diestribution version:
@pli01 pli01 added the enhancement New feature or request label Oct 25, 2024
@alistarle
Copy link

Hi ! I also definitely need this feature. I see in the CRD we can pass resourceId in many object (net/subnet/igw...), have you tested it ?

I'm planning to do it in the following days so I will keep you updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants