Joao C Costa

Thanks. However, it seems the CLI is only able to receive a hostname:port (at least, looking at the validation code) so prob that would also need to change to accomodate...

Hi. Is there any update on this? We are also receiving this from a deployment running on ACI (running this in plain docker seems to generate redirect to https:// instead...

I believe this could alternatively be addressed by https://github.com/aws/aws-sdk/issues/748 (trusting OS certificates), but there was no answer to this either yet.

Yes. Mounting manually in the host worked fine.

It seems some people simply use `kubectl_manifest` and disable the yaml schema validation Example from a fine module for cert-manager: https://github.com/terraform-iaac/terraform-kubernetes-cert-manager/blob/9082a84de3969780c7acfe91f88601349028be33/main.tf#L42 ``` kubectl_manifest" "cluster_issuer" { count = var.cluster_issuer_create ? 1...

You may also add ``` echo "StrictHostKeyChecking no" >> /etc/ssh/ssh_config``` instead

Similar behaviour reported here https://github.com/kubernetes-sigs/external-dns/issues/3948, but this ticket is prob more generic and focusing on consistency across providers.

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale