Comments (9)
We're interested in this, or similar, in cert-manager.
Right now we bake in support for various DNS providers into cert-manager itself in order to update TXT records in order to solve ACME challenges. If we could somehow define a TXT record without directly calling out to DNS provider APIs ourself, it'd be a great addition and simplify our codebase considerably.
Generally speaking, a 'DNS controller' that is not bound to services or ingress would also be very useful.
We have a simple model for managing a similar problem in cert-manager:
A user can define a Certificate resource (our own CRD), which allows for advanced customisation of certificates (e.g. explicit CN or special types of subject alt name). We also allow a user to add a simple annotation (kubernetes.io/tls-acme: "true"
) on ingress resources. We have a component that watches for Ingress resources with this label, and automatically creates and manages a corresponding Certificate resource in order to fulfil the Certificate. This solves the code duplication problem, and gives user a consistent way to debug validation problems.
This same model could be used to provide a migration/transition path from the current external-dns design to something powered by CRDs/custom resources.
More info on how we do this in cert-manager here: https://github.com/jetstack/cert-manager/tree/master/cmd/ingress-shim
from external-dns.
I would postpone this till we get some simple version running :)
from external-dns.
what is the need for that?
from external-dns.
Would just be an alternative way of defining DNS records from inside Kubernetes in a provider independent way.
from external-dns.
It would also be nice to be able to use kubectl get dns
or something like that to look at the DNS records that external-dns created :)
from external-dns.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
from external-dns.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
from external-dns.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
from external-dns.
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen
.
Mark the issue as fresh with/remove-lifecycle rotten
.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
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.
from external-dns.
Related Issues (20)
- Feat Request: Webhook Support for Endpoint Sources HOT 1
- Multi provider not working with helm chart
- External-DNS crash loop due to nil error in DNSEntry object
- Attaching Route53 Alias record to the existing ALB via Service or Istio VirtualService annotation.
- cannot create SRV type record to openstack-designate DNS HOT 1
- [AWS][Feature/Enhancement] Make suitableZones select only one Hosted Zone to create the Route53 records (even if it's public or private)
- add custom certificate
- Cloudflare: remote error: tls: handshake failure HOT 1
- It tries to connect to an HTTPS Designate endpoint via HTTP. HOT 1
- Allow custom provider annotations
- Allow for GatewayRoutes to support setting `dualstack` annotation
- Support Istio v1.22 with `v1` release of the `VirtualService` & `Gateway` CRDs
- Unable to specify SoftError for webhook providers HOT 3
- Helm chart release for v0.14.2 HOT 1
- DNSEndpoint CRD has had its approval annotation removed
- api-approved.kubernetes.io missing from CRD since 0.14.2 HOT 1
- Source Endpoints de-duplication (dedupSource) performed before AdjustEndpoints
- Digital Ocean provider doesn't delete record when ingress is deleted HOT 1
- Digital Ocean provider --ingress-class is ignored HOT 1
- Instagram bot
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from external-dns.