-
Bug
-
Resolution: Done
-
Major
-
DO280 - OCP4.10-en-1-20220520
-
None
-
ROLE
-
ja-JP (Japanese)
URL: https://rol.redhat.com/rol/app/courses/do280-4.10/pages/ch06s07
Reporter RHNID: wasim-rhls
Section: -
Language: ja-JP (Japanese)
Workaround:
Description: Ch06s07:
English version at Step 5: "Create a horizontal pod autoscaler named loadtest for the loadtest application that will scale from 2 pods to a maximum of 40 pods if CPU load exceeds 70%. You can test the horizontal pod autoscaler by accessing the following URL to trigger the load test actions."
Japanese Version at Step 5: "Create a 70% horizontal pod autoscaler for 40 applications that scale from loadtest pods up to 2 pods when the CPU load exceeds loadtest."
English version at Step 6: "As the admin user, implement a quota named review-quota on the schedule-review project. Limit the schedule-review project to a maximum of 1 full CPU, 2G of memory, and 20 pods."
Japanese Version at Step 6: "As the admin user, implement a quota called schedule-review in your review-quota project."
Ch08s07:
English version at Step 2: "Add htpasswd entries to the localusers secret for users named dba and tester using redhat as the password."
Japanese version at Step 2: "Use the htpasswd password to add a tester entry to the redhat secret for users named localusers and dba"
English version at Step 3: "Create a new app-team group that contains the developer and dba users."
Japanese version at Step 3: "Create a new dba group that contains the app-team and developer users."
English version at Step 4: "Create a new console-review project with a view role binding for the tester user and an edit role binding for the app-team group. Set a resource quota that limits the project to two pods."
Japanese version at Step 4: "Create a new console-review project and bind the tester role to the view user and the app-team role to the edit group."