k8s-triage-robot
commented
1 month ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
What would you like to be added: i think we need the possibility to set different roules for domains
mydomain.com --> only for ingress --> exclude private.mydomain.com --> use azure-dns private.mydomain.com --> only for services --> with fqdn-template --> use azure-private-dns --> policy=sync private.mydomain.com --> only for services --> with different fqdn-template --> use azure-private-dns --> policy=sync --> only if specific annotation is set
Why is this needed: no need to run multiple external-dns instances with many minimal config differences doing "the same" --> minimize ressource consumtion....