Cloudflare DNS proxy leveraging

[simontechdev]

What is your feature idea?

Using cloudflare DNS does not allow me to set proxy,

Why is it needed?

This feature is a key reason we use CloudFlare for DNS CDN WAF DDOS attack mitigation

Is this missing feature preventing you from using kubefirst?

• Yes

Code of Conduct

• I agree to follow this project's Code of Conduct

[simontechdev]

After kubefirst has brilliantly assigned a URL to a specific ingress endpoint and cluster and cert manager has provisioned a certificate using lets-encrypt, I want to turn on proxy for the particular URL but kubefirst will revert it to DNS only after a few seconds.
The proxy is a required feature, as it is key to why I would be using CloudFlare in the first place.
I don't see a way to change a configuration on this, am I missing something or is this missing as a feature?

[johndietz]

we use cloudflare dns with proxy turned on with some regularity in our testing environments and it works well for us. we don't natively configure/manage this in your cloudflare zone, but if proxy were turned on it would be used and our expectation is that it works well. we don't use proxy for the reasons you're mentioning, so i may just have a disconnect with your use case.
can you provide the specific details of what action you're conducting to "turn on proxy" for the particular url?

[simontechdev]

@johndietz Ok, so I see my DNS change as expected to the DNS only when provsioning or changing host in my gitops app registry values.yaml.
Then I often go and turn on Proxy for that URL

A few seconds later it changes right back

[simontechdev]

@johndietz so maybe it's a bug?
Or is there a place in the gitops to configure this ?
Since you have this working, what would this look like in gitops for Metaphor as an example application?