Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It tries to connect to an HTTPS Designate endpoint via HTTP. #4466

Closed
otter06 opened this issue May 13, 2024 · 1 comment
Closed

It tries to connect to an HTTPS Designate endpoint via HTTP. #4466

otter06 opened this issue May 13, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@otter06
Copy link

otter06 commented May 13, 2024

What happened:
I am getting the error below:

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.
image
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.

@otter06 otter06 added the kind/bug Categorizes issue or PR as related to a bug. label May 13, 2024
@otter06
Copy link
Author

otter06 commented May 18, 2024

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.

@otter06 otter06 closed this as completed May 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant