Adds ExternalDNS Operator Enhancement Proposal #456
Conversation
openshift-ci-robot
requested review from
frobware,
knrc,
mcurry-rh and
sgreene570
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: danehans The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
|
||
| ### Non-Goals | ||
|
|
||
| * Replace the functionality of existing operators. __Note:__ The ExternalDNS Operator intends to replace external DNS |
There was a problem hiding this comment.
Could you be a bit more specific here? If the ExternalDNS Operator will later down the road replace the external DNS features provided by the Ingress Operator, than what existing functionality won't be replaced? Perhaps replacing the external DNS management available via the ingress operator should be listed as a goal here to avoid confusion?
|
|
||
| This enhancement proposal is for adding an operator to manage | ||
| [ExternalDNS](https://github.com/kubernetes-sigs/external-dns). ExternalDNS has been chosen for managing external DNS | ||
| requirements of OpenShift clusters. Initially, the operator will focus on managing external DNS record(s) of OpenShift |
There was a problem hiding this comment.
Could you elaborate more on the benefits of bringing external DNS to OpenShift in any capacity? Are there any use cases besides the initial challenge of managing external DNS for Routes?
|
|
||
| #### Story 1 | ||
|
|
||
| As a developer, I need the ability to manage DNS records for OpenShift routes. |
There was a problem hiding this comment.
This story seems a little vague. How about instead:
As a developer, I want to manage DNS records for OpenShift Routes via my OpenShift cluster, so that I do not have to spend time manually configuring my cloud provider's DNS.
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci-robot
added
the
lifecycle/stale
|
I didn't see this feature explicitly called out, so I'm adding this feature request (it's probably already assumed). I would like for the external DNS operator to track a service, like a loadbalancer service. For example, I would like to create a service of type loadbalancer, named "foo", which creates an LB in the cloud with an IP. I would like to create an externdns "dnsrecord" CRD that says "this service should have DNS record of "foo" that points to the IP of the loadblancer". I don't want to have to specify the actual IP, just the service it should "track". This would make these records super useful for config management systems so the admin doesn't need to do any sort of logic to get the IP first. |
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci-robot
added
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This commit contains the original external-DNS operator enhancement proposal create by Daneyon as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original external-DNS operator enhancement proposal create by Daneyon as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original external-DNS operator enhancement proposal create by Daneyon as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original externalDNS operator enhancement proposal create by Daneyon Hansen as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original externalDNS operator enhancement proposal create by Daneyon Hansen as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original externalDNS operator enhancement proposal create by Daneyon Hansen as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original externalDNS operator enhancement proposal create by Daneyon Hansen as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original externalDNS operator enhancement proposal create by Daneyon Hansen as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original externalDNS operator enhancement proposal create by Daneyon Hansen as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original externalDNS operator enhancement proposal create by Daneyon Hansen as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original externalDNS operator enhancement proposal create by Daneyon Hansen as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original externalDNS operator enhancement proposal create by Daneyon Hansen as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original externalDNS operator enhancement proposal create by Daneyon Hansen as a part of openshift#456 (which was closed due to inactivity).
This commit contains the original externalDNS operator enhancement proposal create by Daneyon Hansen as a part of openshift#456 (which was closed due to inactivity).
Adds an enhancement proposal for an operator to manage ExternalDNS.
/assign @knobunc @Miciah
/cc @frobware @sgreene570 @mcurry-rh @knrc
Supports NE-303