Skip to content

feat: manage hostname / ip address exposed by K8 LoadBalancer service #82

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

Closed
qdzlug opened this issue Feb 2, 2022 · 1 comment · Fixed by #167
Closed

feat: manage hostname / ip address exposed by K8 LoadBalancer service #82

qdzlug opened this issue Feb 2, 2022 · 1 comment · Fixed by #167
Labels
enhancement New feature or request

Comments

@qdzlug
Copy link
Contributor

qdzlug commented Feb 2, 2022

Is your feature request related to a problem? Please describe.
Within the ingress_controller project, we receive the hostname and/or IP address of the external IP that we are assigned based on the K8 LoadBalancer object. The hostname is key for the cert-manager function which handles the certificate issuance (to start with, we issue self-signed certs currently). However, some LoadBalancer implementations (such as metallb) only provide an IP address and no hostname. To get around this, we currently prompt for and use a FQDN, with the understanding that the user needs to either create a DNS record or update their hostfile to connect the FQDN with the IP address they are using.

Describe the solution you'd like
This should be seamless to the user, and should be able to follow logic that:

  1. Checks for the presence of a hostname associated with the IP address (if only an address is given).
  2. Provide instruction to the user as to what steps need to be taken if no FQDN is bound to the IP address.

Additionally, the logic should include a place where an outside DNS provider can be called from the stack to create a record linking the FQDN and the IP address. Note that we do not need to implement this, merely make sure we don't make any design decisions that prohibit this from being done.

Describe alternatives you've considered
None.

Additional context
None.

@qdzlug qdzlug mentioned this issue Mar 8, 2022
7 tasks
@qdzlug qdzlug added the enhancement New feature or request label Mar 15, 2022
@qdzlug
Copy link
Contributor Author

qdzlug commented Aug 12, 2022

#167 addresses DO, Linode in addition to AWS support. Additional support is WIP (for kubeconfig deploys)

@qdzlug qdzlug linked a pull request Aug 19, 2022 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant