8000 Endpoints for custom cluster domains only show http even if https is available · Issue #850 · rancher/rio · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Sep 5, 2024. It is now read-only.
8000

Endpoints for custom cluster domains only show http even if https is available #850

Closed
rancher-max opened this issue Nov 21, 2019 · 3 comments
Closed

Endpoints for custom cluster domains only show http even if https is available #850

rancher-max opened this issue Nov 21, 2019 · 3 comments
Assignees
@StrongMonkey
Labels
bug Something isn't working
Milestone
v0.7.0

Comments

@rancher-max
Copy link
Member
rancher-max commented Nov 21, 2019 •
edited by davidnuzik
Loading

Both the http and https endpoints should be available when using custom cluster domains and specifying both. It should default to showing https in the cli.

Current state does not show the https endpoint at all, and it's not in the manifest when using rio inspect to get endpoints.

Reference: #700
@rancher-max rancher-max added enhancement New enhancement to an existing feature or request to enhance a feature [zube]: To Triage labels Nov 21, 2019
@davidnuzik davidnuzik added bug Something isn't working and removed enhancement New enhancement to an existing feature or request to enhance a feature labels Nov 22, 2019
@davidnuzik davidnuzik added this to the v0.6.x milestone Nov 22, 2019
@davidnuzik davidnuzik modified the milestones: v0.6.x, v0.7.0 Nov 26, 2019
@StrongMonkey StrongMonkey mentioned this issue Dec 9, 2019
Merged
@rancher-max
Copy link
Member Author

https is shown when it is specified and a secret is supplied. When a secret is not supplied, https is not supported and then only http is shown.

@mbarlow
Copy link
mbarlow commented Jan 9, 2020

@rancher-max can you give more details for: https is shown when it is specified and a secret is supplied? How is https specified and how is secret supplied? I followed the instructions here: https://github.com/rancher/rio/blob/master/docs/faq.md at bottom creating a clusterdomain with the entry secretName set to my wildcard tls secret and rio info still shows (false) for my wildcard and deploying a workload w/ rio still only shows http for endpoint when doing rio ps or rio inspect. I am using v0.7.0.

@rancher-max
Copy link
Member Author

@mbarlow We did some investigating on this. Following the steps from here: #700 (comment) if you just do a bare rio install OR rio install --disable-features rdns it should work. I'm noticing that for some reason it does not work when we disable letsencrypt as it appears to only set ClusterDomain to https inside the LE controller.

Will use #990 to enhance this functionality.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@StrongMonkey StrongMonkey

Labels
bug Something isn't working
Projects
None yet
Milestone
v0.7.0
Development

No branches or pull requests
4 participants
@mbarlow @StrongMonkey @davidnuzik @rancher-max
0