Bug 1270492
| Summary: | [fork][platformmanagement_522] Can not access the services via API proxy for example sample-app | ||
|---|---|---|---|
| Product: | OKD | Reporter: | weiwei jiang <wjiang> |
| Component: | Pod | Assignee: | Jordan Liggitt <jliggitt> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jianwei Hou <jhou> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.x | CC: | aos-bugs, jliggitt, mmccomas, wsun |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-23 21:15:31 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
weiwei jiang
2015-10-10 10:57:53 UTC
Proxying to a service port requires the name of the port. `new-app` happens to generate names with `<port>-<protocol>`, but the sti template sets its own custom names. I think you need to use "https://127.0.0.1:8443/api/v1/proxy/namespaces/default/services/http:frontend:web/" Also, https will only work if the backend is actually serving https, which I don't think the sample app is. (In reply to Jordan Liggitt from comment #1) > Proxying to a service port requires the name of the port. `new-app` happens > to generate names with `<port>-<protocol>`, but the sti template sets its > own custom names. > > I think you need to use > "https://127.0.0.1:8443/api/v1/proxy/namespaces/default/services/http: > frontend:web/" > > Also, https will only work if the backend is actually serving https, which I > don't think the sample app is. Rechecked with /http:frontend:web/ and found this is not an issue now. |