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.

Sign up for GitHub

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

Convert HTTP route to HTTPS #41

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Convert HTTP route to HTTPS #41

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
def2f37
Convert HTTP route to HTTPS
fjcloud Jun 12, 2023
e362f33
More explanation for route config
fjcloud Jun 13, 2023
3b9701c
Fix typo
fjcloud Jun 13, 2023
33b9438
add bash flag
fjcloud Jun 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion rosa-content/300-app/deploy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,6 +218,14 @@ You can also get the the URL for your application using the command line:
```bash
oc -n microsweeper-ex get route microsweeper-appservice -o jsonpath='{.spec.host}'
```
### Use HTTPS

As you can see application is accesible only by HTTP, to change configuration of route to use only HTTPS, run:

```bash
oc patch route microsweeper-appservice --patch '{"spec":{"tls":{"termination":"edge"}}}'
fjcloud marked this conversation as resolved.
Show resolved Hide resolved
oc patch route microsweeper-appservice --patch '{"spec":{"tls":{"insecureEdgeTerminationPolicy":"Redirect"}}}'
```

### Application IP
Let's take a quick look at what IP the application resolves to. Back in your Cloud Shell environment, run the following command:
Expand All @@ -239,4 +247,4 @@ Address: 40.117.143.193

Notice the IP address; can you guess where it comes from?

It comes from the ROSA Load Balancer. In this workshop, we are using a public cluster which means the load balancer is exposed to the Internet. If this was a private cluster, you would have to have connectivity to the VPC ROSA is running on. This could be via a VPN connection, AWS DirectConnect, or something else.
It comes from the ROSA Load Balancer. In this workshop, we are using a public cluster which means the load balancer is exposed to the Internet. If this was a private cluster, you would have to have connectivity to the VPC ROSA is running on. This could be via a VPN connection, AWS DirectConnect, or something else.