rancher: Rancher Global DNS cloudflare record cannot be proxied
What kind of request is this (question/bug/enhancement/feature request): Rancher Global DNS (cloudflare DNS record cannot be proxied)
Steps to reproduce (least amount of steps as possible):
- Create Rancher HA 2.1.7 ( from rke 0.2.0 ) update rancher to 2.2.0 (by helm)
- create Global DNS Provider cloudflare
- make dns record on project
Result: log from rancher-external-dns
time="2019-03-28T17:17:50Z" level=error msg="failed to update record: error from makeRequest: HTTP status 400: content \"{\\\"success\\\":false,\\\"errors\\\":[{\\\"code\\\":1004,\\\"message\\\":\\\"DNS Validation Error\\\",\\\"error_chain\\\":[{\\\"code\\\":9041,\\\"message\\\":\\\"This DNS record cannot be proxied - click the cloud icon to turn it gray to proceed\\\"}]}],\\\"messages\\\":[],\\\"result\\\":null}\"" action=UPDATE record=SECURE.DOMAIN.COMPANY ttl=120 type=A zone=9426cb70f936d46d0fd705d38661b6a8
time="2019-03-28T17:17:50Z" level=info msg="Changing record." action=UPDATE record=SECURE.DOMAIN.COMPANY ttl=1 type=TXT zone=9426cb70f936d46d0fd705d38661b6a8
Other details that may be helpful:
Ufter upgrade app systemapp-service-discovery
cloudflare.proxied=false
helps for a while
After some time, the application is updated and deletes the key cloudflare.proxied
Environment information
- Rancher version (
rancher/rancher/rancher/serverimage tag or shown bottom left in the UI): 2.2.0 - Installation option (single install/HA): HA
Cluster information
- Cluster type (Hosted/Infrastructure Provider/Custom/Imported): OpenShift
- Machine type (cloud/VM/metal) and specifications (CPU/memory): 3VM (4cpu 8gb)
- Kubernetes version (use
kubectl version):
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:30:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
- Docker version (use
docker version):
Client:
Version: 18.09.4
API version: 1.39
Go version: go1.10.8
Git commit: d14af54266
Built: Wed Mar 27 18:35:44 2019
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 18.09.4
API version: 1.39 (minimum version 1.12)
Go version: go1.10.8
Git commit: d14af54
Built: Wed Mar 27 18:01:48 2019
OS/Arch: linux/amd64
Experimental: false
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (7 by maintainers)
@sangeethah This issue still exists on rancher
v2.4.5. I created a provider with Proxy settings set tonoand the record generated still hadproxy orange cloud. I tried toggling the settings and nothing happens.The issue is coming from multiple providers that I have. I have 2 Global providers, one with proxy enabled and another disabled on the same root domain.
However, the entries are correctly mapped to the appropriate provider and yet the record is created with the provider that was created first.
Records are being updated from the same container
The above records are mapped to different providers, so should not be updated from the same container.
What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):
noEnvironment information
rancher/rancher/rancher/serverimage tag or shown bottom left in the UI): 2.4.5Cluster information
kubectl version):docker version):@prachidamle Great, waiting for the update!
@prachidamle No, it’s because I don’t want my traffic to go through a cloudflare proxy, I want my requests to go straight to my servers