
                    For gcp, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

The problem suddenly re-occured.. I think it has to do with the gpg-agent For the moment this solved it for me adding to .bashrc or similiar (I hava a .zshrc) 

sops Cannot decrypt with GPG 2.2.5 and SOPS 3.0.0

Actually I don't think this topic should be closed I was able to use external-dns with AWS Route53 and EKS cluster with a Traefik 1.7 Ingress resource 

external dns Is it possible to use external-dns with a Traefik 2.0 IngressRoute resource?

This is great it works perfectly Instead of targeting specific groups from external-dns i've standardized the way to exclude 

external dns Disable external-dns for specific ingresses

Hi @hickey I had faced the same error as you But later I figured out I made the mistake when putting the AWS credential 

external dns AWS API InvalidClientTokenId: The security token included in the request is invalid

I have a workaround until this feature is shipped While pondering #1654 

pulumi Resource Adoption

Same issue here but with NS.. time=2020-12-17T19:50:38Z level=error msg=Failed to extract targets for '<my>.<domain>.<tld>' with type 'NS'. 

external dns External-dns fails to extract targets for SRV records on Azure

@cabrinoob - If you are using the nginx-ingress helm chart look at


within the values.yaml 

external dns Ingress hosts are not getting DNS names created.

I tested it in our setup and it seems to work fine Here's what I did Let's assume we want to run ExternalDNS in account A managing records in account B 

external dns AWS cross account access with OIDC provider in EKS & externalDNS not working

Ah I see After making this modification it works Thanks so much for your help @elibixby For others' reference 

cloudml samples No instance key in output of canned estimator census sample

It's currently not possible to force using CNAME when ALIAS would also work as our expectations was that most people will want to use ALIAS in that case 

external dns External DNS always uses ALIAS for AWS ELBs, not CNAME (only A records are created in Route53)

Thanks for the clarifications and feedback I agree we can definitely work toward making the documentation clearer in the way you're describing Currently 

pulumi Python Outputs to string do not work as documented

Here is the draft of the forking plan:

Fork protocolbuffers/protobuf to Pulumi org (done): https://github.com/pulumi/protobuf
Checkout the latest stable tag (v3.13.0.1 as of today)