public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 12:38:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Quickstart docs and Adding Ingresses page for Rancher 2.6 (#3711)

Browse Source 
* Added step to tell users to add a port

* Updated Step 2, exposing the app via an ingress

* Added one step to the ingress nav

* Updated per feedback

* Updated per feedback

* Updated results sentence

* Update content/rancher/v2.6/en/quick-start-guide/workload/quickstart-deploy-workload-ingress/_index.md

Co-authored-by: Billy Tat <btat@suse.com>

* Update content/rancher/v2.6/en/quick-start-guide/workload/quickstart-deploy-workload-ingress/_index.md

Co-authored-by: Billy Tat <btat@suse.com>

* Update content/rancher/v2.6/en/quick-start-guide/workload/quickstart-deploy-workload-ingress/_index.md

Co-authored-by: Billy Tat <btat@suse.com>

Co-authored-by: Billy Tat <btat@suse.com>
This commit is contained in:
Jen Travinski
2021-12-07 10:10:04 -08:00
committed by GitHub
co-authored by Billy Tat
parent ee481cb498
commit 7f0a36adff
2 changed files with 15 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/ingress/_index.md
+1
View File
@@ -14,6 +14,7 @@ Ingresses can be added for workloads to provide load balancing, SSL termination
1. Enter a **Name** for the ingress.
1. Create ingress forwarding **Rules**. For help configuring the rules, refer to [this section.](#ingress-rule-configuration) If any of your ingress rules handle requests for encrypted ports, add a certificate to encrypt/decrypt communications.
1. **Optional:** click **Add Rule** to create additional ingress rules. For example, after you create ingress rules to direct requests for your hostname, you'll likely want to create a default backend to handle 404s.
1. Click **Create** at the bottom right.
**Result:** Your ingress is added to the project. The ingress begins enforcing your ingress rules.
content/rancher/v2.6/en/quick-start-guide/workload/quickstart-deploy-workload-ingress/_index.md
+14 -13
View File
@@ -13,13 +13,14 @@ You're ready to create your first Kubernetes [workload](https://kubernetes.io/do
For this workload, you'll be deploying the application Rancher Hello-World.
1. Click **☰ > Cluster Management**.
1. Click **☰ > Cluster Management**.
1. Go to the cluster that you created and click **Explore**.
1. Click **Workload**.
1. Click **Create**.
1. Click **Deployment**.
1. Enter a **Name** for your workload.
1. From the **Docker Image** field, enter `rancher/hello-world`. This field is case-sensitive.
1. Click **Add Port** and enter `80` in the **Private Container Port** field. Adding a port enables access to the application inside and outside of the cluster. For more information, see [Services]({{<baseurl>}}/rancher/v2.6/en/k8s-in-rancher/workloads/#services).
1. Click **Create**.
**Result:**
@@ -30,32 +31,32 @@ For this workload, you'll be deploying the application Rancher Hello-World.
<br/>
### 2. Expose The Application Via An Ingress
Now that the application is up and running it needs to be exposed so that other services can connect.
Now that the application is up and running, it needs to be exposed so that other services can connect.
1. Click **☰ > Cluster Management**.
1. Go to the cluster that you created and click **Explore**.
1. Go to the cluster that you created and click **Explore**.
2. From the main menu of the **Dashboard**, select **Projects**.
1. Click **Service Discovery > Ingresses**.
3. Open the **Default** project.
1. Click **Create.**
4. Click **Resources > Workloads > Load Balancing**. Click on the **Load Balancing** tab.
1. When choosing **Namespace**, ensure it is the same as the one used when you created your deployment. Otherwise, your deployment will not be available when you attempt to select **Target Service**, as in Step 8 below.
5. Click **Add Ingress**.
1. Enter a **Name**, such as **hello**.
6. Enter a name i.e. **hello**.
1. Specify your **Path**, such as `/hello`.
7. In the **Target** field, drop down the list and choose the name that you set for your service.
1. In the **Target Service** field, drop down the list and choose the name that you set for your service.
8. Enter `80` in the **Port** field.
1. In the **Port** field, drop down the list and select `80`.
9. Leave everything else as default and click **Save**.
1. Click **Create** at the bottom right.
**Result:** The application is assigned a `xip.io` address and exposed. It may take a minute or two to populate.
**Result:** The application is assigned a `sslip.io` address and exposed. It may take a minute or two to populate.
### View Your Application
From the **Load Balancing** page, click the target link, which will look something like `hello.default.xxx.xxx.xxx.xxx.xip.io > hello-world`.
From the **Deployments** page, find the **Endpoints** column for your deployment and click on an endpoint. The endpoints available will depend on how you configured the port you added to your deployment. For endpoints where you do not see a randomly assigned port, append the path you specified when creating the ingress to the IP address. For example, if your endpoint looks like `xxx.xxx.xxx.xxx` or `https://xxx.xxx.xxx.xxx` change it to `xxx.xxx.xxx.xxx/hello` or `https://xxx.xxx.xxx.xxx/hello`.
Your application will open in a separate window.