forked from Azure/kubernetes-hackfest
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
srodenhuis
committed
Apr 6, 2022
1 parent
68b6111
commit 89be487
Showing
3 changed files
with
33 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# Lab 6 | ||
|
||
In this lab we are going to activate Knative and create a new Knative service using Otomi Console. | ||
|
||
## Instructions | ||
|
||
1. Go to the Apps section under `Platform` and Drag and Drop `Knative` from the `Disabled apps` to the `Enabled apps` and `Deploy changes`. | ||
|
||
2. Select your team in the top bar, click `Services` under your team in the right menu and click on `Create Service`. | ||
|
||
You might notice that in the `Service type` section there are now 2 extra options: | ||
|
||
- Existing knative service: to map a pre-deployed knative service to Otomi | ||
- New knative service: to create a new knative service using Otomi | ||
|
||
3. Provide a name for your service | ||
|
||
4. Select `New knative service` and use the following values: | ||
|
||
- Run As User: 1001 | ||
- Repository: nginxinc/nginx-unprivileged | ||
- Tag: stable | ||
- Limits: CPU=200m, Memory=128Mi | ||
- Requests: CPU=100m, Memory=64Mi | ||
- Exposure: Public | ||
|
||
5. Now click `submit` and `Deploy changes. | ||
|
||
6. The new service and the Hostname are now shown in the list of services. Wait until the Drone pipeline has finished and click on the hostname. | ||
|