30.3. 멀티 테넌시 하위 도메인 이해

MASTER_NAME 매개변수에 의해 정의된 마스터 관리자 포털 경로:

<MASTER_NAME>.<WILDCARD_DOMAIN>

TENANT_NAME 매개변수에 의해 정의된 계정 관리자 포털 경로:

<TENANT_NAME>-admin.<WILDCARD_DOMAIN>

계정의 개발자 포털 경로:

<TENANT_NAME>.<WILDCARD_DOMAIN>

프로덕션 및 포함된 APIcast 게이트웨이를 스테이징하는 경로:

<API_NAME>-<TENANT_NAME>-apicast-staging.<WILDCARD_DOMAIN>
<API_NAME>-<TENANT_NAME>-apicast-production.<WILDCARD_DOMAIN>

This example illustrates the output users and routes of a standard multitenant deployment of 3scale:

----
--> Deploying template "3scale-project/3scale-api-management" for "amp.yml" to project project

3scale API Management
---------
3scale API Management main system

     Login on https://user-admin.3scale-project.example.com as admin/xXxXyz123
     ...
     * With parameters:
      * ADMIN_PASSWORD=xXxXyz123 # generated
      * ADMIN_USERNAME=admin
      * TENANT_NAME=user
      ...
      * MASTER_NAME=master
      * MASTER_USER=master
      * MASTER_PASSWORD=xXxXyz123 # generated
      ...
--> Success
    Access your application via route 'user-admin.3scale-project.example.com'
    Access your application via route 'master-admin.3scale-project.example.com'
    Access your application via route 'backend-user.3scale-project.example.com'
    Access your application via route 'user.3scale-project.example.com'
    Access your application via route 'api-user-apicast-staging.3scale-project.example.com'
    Access your application via route 'api-user-apicast-production.3scale-project.example.com'
    Access your application via route 'apicast-wildcard.3scale-project.example.com'
    ...
----