You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
time="2024-05-13T05:50:39Z" level=info msg="Instantiating new Kubernetes client"
time="2024-05-13T05:50:39Z" level=info msg="Using inCluster-config based on serviceaccount-token"
time="2024-05-13T05:50:39Z" level=info msg="Created Kubernetes client https://10.254.0.1:443"
time="2024-05-13T05:50:39Z" level=info msg="Using OpenStack Keystone at https://srv01.loutres.internal:5000/v3/"
time="2024-05-13T05:50:39Z" level=info msg="Found OpenStack Designate service at https://srv01.loutres.internal:9001/"
time="2024-05-13T05:50:40Z" level=fatal msg="Failed to do run once: Get \"http://srv01.loutres.internal:9001/v2/zones/08e92a01-2b7b-4a5f-8df1-e4b44b822093/recordsets?marker=0dc33cbd-857f-4434-a341-0b625fe48b25\": EOF"
What you expected to happen:
As the endpoint of Designate is registered like below, It should be connected via HTTPS, not HTTP.
$ openstack endpoint list --service dns
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------------------+
| ID | Region | Service Name | Service Type | Enabled | Interface | URL |
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------------------+
| 00b0cff7e316490d957a1a7cf94b6f71 | RegionOne | designate | dns | True | admin | https://srv01.loutres.internal:9001/ |
| d4be7d840d07441e99dc6dfa3ed788b8 | RegionOne | designate | dns | True | internal | https://srv01.loutres.internal:9001/ |
| f8404f3df5b6447e9cb7724dbf020218 | RegionOne | designate | dns | True | public | https://srv01.loutres.internal:9001/ |
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------------------+
Anything else we need to know?:
I checked that it surely tries to connect with HTTP using WireShark.
By the way, the connection to get the zones was HTTPS without any problem, only the connection to get the recordsets was tried to connected via HTTP.
Environment:
External-DNS version: v0.14.1
DNS provider: Designate
Others:
Kubernetes: v1.28.9
OpenStack: Caracal
I am not a native, so sorry for my bad English.
The text was updated successfully, but these errors were encountered:
Sorry, that was my fault.
The next page url coming back from the Designate was http due to the SSL proxy in between.
I disabled the SSL proxy and set up SSL in Designate and it fixed it.
I hope this helps someone.
What happened:
I am getting the error below:
What you expected to happen:
As the endpoint of Designate is registered like below, It should be connected via HTTPS, not HTTP.
Anything else we need to know?:
I checked that it surely tries to connect with HTTP using WireShark.
By the way, the connection to get the zones was HTTPS without any problem, only the connection to get the recordsets was tried to connected via HTTP.
Environment:
I am not a native, so sorry for my bad English.
The text was updated successfully, but these errors were encountered: