feat: adopt pre-created EIPs with specific tags

[lukasmrtvy]

Hi,
I would like to see support for adopting already created EIPs via EIP tags

apiVersion: kubestatic.quortex.io/v1alpha1
kind: ExternalIP
metadata:
  name: externalip-sample
spec:
  nodeName: ip-10-231-6-214.eu-west-1.compute.internal
  eipTags:
     team: red
     env: staging

and

kubestatic.quortex.io/externalip-auto-assign: true
kubestatic.quortex.io/externalip-auto-assign-tags: "team=red,env=staging"

Maybe even fallback solution would be an option ( when there is no pre-created IP with specific tag => create new one ), for example:

kubestatic.quortex.io/externalip-auto-assign-tags-fallback: true

Thanks

[vincentmrg]

Hello,

We're working on redisigning the association logic between Kubernetes resources (ExternalIP / FirewallRule) and cloud provider resources (ElasticIP / SecurityGroup).
Where this logic is currently managed in the status of custom resources, we've planned to use cloud-provider side tags instead.

I have the feeling that this could solve your problem (you'd just need to tag the resources correctly on the AWS side for kubestatic to appropriate them).