-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Document design: features and annotations #1
Comments
Also for reference the proposal mail to the kubernetes-dev mailing list: https://groups.google.com/forum/#!searchin/kubernetes-dev/external$20dns%7Csort:relevance/kubernetes-dev/2wGQUB0fUuE/9OXz01i2BgAJ |
simultaneously we may create issues for open questions we have to kick off discussion regarding the issues/solutions. For example, how to resolve the case of two ingress requesting same hostname. We might also do it in design doc PR. Thoughts? |
kick-off: #4 |
@justinsb documented |
@linki anything you want to add ? |
@ideahitme no, I'm fine. |
* set RecordType at source * add comments for linting
…netes-sigs#248) * set RecordType at source * add comments for linting
Integrate PR kubernetes-sigs#687 from kubernetes-incubator/external-dns kubernetes-sigs#687
fixed an issue with handling multiple oci zones
Group equal DNS names into same endpoint
…eletion Fix alias records harder
To run: provide token HETZNER_TOKEN in ENV set command line parameter --provider=hetzner
Ibmcloud provider
Currently we may want to allow cahnges to the index manifest format. The current approach can break users that are on old versions.
Change variable type and description
…zflycloud-provider Feature/add bizflycloud provider
Update README.md with Efficient IP Provider
chore(github-actions): added scorecard github action
First thing to do for this new Incubator project: create a design doc (
docs/design
folder as @justinsb proposed) with all planned features and the interface to the user (annotations and Ingress resource).We can use the contents of the "External DNS" Google Doc as a start.
The text was updated successfully, but these errors were encountered: