Michael Nairn

This doesn't really do what was asked for in #551, and you have gone a different route of checking the eventual target IP(s) are reachable. This may or may not...

Presumably you mean secrets here? If Certificates aren't being removed then it's a bug. re. secret removal, you can configure certmanager to do this see https://cert-manager.io/v1.1-docs/usage/certificate/#cleaning-up-secrets-when-certificates-are-deleted Since TLSPolicy doesn't create...

https://github.com/Kuadrant/kuadrant-operator/pull/961

Closing this, re-open with steps to reproduce if it's still an issue. If cert-manager was never installed this should never be possible [since]( https://github.com/Kuadrant/kuadrant-operator/pull/715/files#diff-38477e498c938e91320e277fd9be8bb1abfcbb26abc2af86c309865d49f19a3cR205), as the controller that adds the...

@didierofrivia re. https://github.com/Kuadrant/kuadrant-operator/issues/241, why do we want to trigger this job on pull requests?

This should be fixed as part of the managed zone removal https://github.com/Kuadrant/dns-operator/pull/203

> This should be fixed as part of the managed zone removal [Kuadrant/dns-operator#203](https://github.com/Kuadrant/dns-operator/pull/203) Will be looked into after [Kuadrant/dns-operator#203](https://github.com/Kuadrant/dns-operator/pull/203) as we will probably mark the `rootHost ` filed as immutable...

I believe this should have been resolved by https://github.com/Kuadrant/kuadrant-operator/pull/715, cc @KevFan

Closing since we do now watch Issuers,ClusterIssuers and Certifcates

With the current implementation of the DNSRecord status update I'd say this is expected. In order to facilitate multiple records and therefore multiple clusters sharing a hostname, a mechanism by...