Ivan Ka
I'll try to find a solution for linter. We recently added few things, looks like a bug was introduced
A fix for this issue appears to be available in another pull request (https://github.com/kubernetes-sigs/external-dns/pull/5085/files). Hopefully, it will be reviewed and approved soon.
> > A fix for this issue appears to be available in another pull request (https://github.com/kubernetes-sigs/external-dns/pull/5085/files). Hopefully, it will be reviewed and approved soon. > > Ah I see.. Let's...
I'll throw some ideas - [ ] There is an issue, so worth to ask a requestor to share his setup, he may be able to point out or explain...
Np, I think I shared enough information to consider. Could be that I did not spend enough time to understand the original issue, and this is my understanding of client...
Without reproducable setup on local machine with mininkute or kind, this going to be on hold. As need to be proper smoke tested. Access to AWS via proxy and `rfc2136`...
Hey. It will not fixes the issue, but it relates. As the issue is more about HOW to, and not WHY something is not supported. The problem should be clear...
Worth adding to the header of the pull request a description
> For more context I am trying to solve the problem where one external dns instance can manage multiple aws hosted zones through role assumption. So ideally we wouldn't need...
Just few concerns - From a security standpoint, I have concerns about using a single external-dns instance to manage multiple accounts. This approach seems risky. While I understand there might...