Request Addition/Deletion of Fleet and Devspace in Kosmos
Prerequisite
You must have access to Kosmos . For more details on how to request access to Kosmos, please refer to Kosmos Account Request .
Tenant management approval in Kosmos for Samsung employees
I. Submit Knox approval request
To request a Fleet/Devspace, it is mandatory to submit a Knox Approval. Please submit a Knox Approval using the guideline below.
If you are a new or first-time user to Kosmos, please copy:
- Section 1: Kosmos account registration
- Section 2: Collection of personal information
into your Knox Approval Request format.
If you already have access, skip to:
- Section 3: Request to create new services (Fleet/s or Devspace/s) in Kosmos
- Section 4: Request to delete existing services (Fleet/s or Devspace/s) in Kosmos
These sections must be included in the body of the Knox Approval Request when the request is submitted.
Section 1: Kosmos account registration
| Field | Details |
|---|---|
| Project name | ※ ECOv2 registered name preferred |
| Project code | ※ For Distribution/Billing, please use the same code as IRP/PLM |
| Project purpose/scenario | ※ Example: Statistics for mobile application update service; Service admin runs query to get statistics for data analysis |
| Target service open date | ※ For testing purposes, fill in “Test Only” |
| Team & group | ※ Name of team & group owning the project |
| CCTR | ※ Cost Center Code (team code/부서코드) |
Section 2: Collection of personal information
□: I agree to the collection and use of personal information as notified by Kosmos.
Personal information collection and use agreement Samsung Electronics Samsung Private Cloud (for administrators)
Samsung Electronics Co., Ltd. (hereinafter referred to as the “Company”) collects the following personal information from users when they first sign up for membership or use the service.
Users have the right to not consent to the collection and use of ‘personal information other than the minimum necessary information’ when agreeing in accordance with this personal information collection and use agreement.
For detailed information on personal information processing, please refer to the ‘Personal Information Processing Policy’ published on the Kosmos website https://console.kosmos.spcplatform.com/ .
However, in case of any conflict with the contents of this agreement, the contents of this agreement shall take precedence.
Consent to collection and use of personal information (required)
You may refuse to consent to the collection and use of essential items, but this is information that is essential to provide services.
If you refuse consent, you will not be able to access the website and system.
When submitting a payment, you are deemed to have agreed to the collection and use of personal information below.
| Collection items | Collection purpose | Retention period |
|---|---|---|
| Account name set by user | 1. Membership management (a). User identification, confirmation of membership registration/withdrawal, (b). Preventing illegal use, handling complaints, (c). Delivery of notices 2. Service provided (a). Using and managing Samsung Private Cloud services 3. Service improvement and development (a). Analysis of service use (b). Improving existing services | Until account deletion date |
| Service provided | Using and managing Samsung Private Cloud services, service improvement and development, analysis of service use, improving existing services | Until account deletion |
| TagMemo | ||
| IP address | ||
| Cookie | ||
| Service usage records | ||
| Visit history |
Section 3: Request to create new services (Fleet/s or Devspace/s) in Kosmos
Note: For external customers in PROD environment, include this in your Knox request using the format below.
| Sr no | Property | Format | Comments |
|---|---|---|---|
| 1 | Project name | Project/Team name | Provide project/team information |
| 2 | Project purpose/scenario | Please fill this out if you are skipping Section 1 | Example: Statistics for mobile application update service; Service admin runs data analysis queries |
| 3 | Notification list | kosmospmo@joyent.com | Kosmos PMO team will be notified |
| 4 | Approval line | ||
| 5 | Requested Kosmos services | □ Fleet/s, □ Devspace/s | Specify requested Kosmos Service. |
| If you have more than 1 service requests | Repeat rows 6–10 for each request | ||
| 6 | ServiceName1 | FleetName1/DevspaceName1 Format: TeamName-ProjectName-ShortDesc (e.g., pmo-billingproject-billing) | Please provide the FleetName1/DevspaceName1 |
| 7 | Cluster information (for Devspace requests) | □ Devpool □ Sandbox | Please provide your preference of Devpool or Sandbox cluster configuration Sandbox: with higher security levels based on the domain-based outbound traffic control. DevPool: with lower security levels without the outbound traffic control |
| 8 | Primary user information | User name, Samsung email | Example: John Doe, john.doe@samsung.com |
| 9 | Secondary user information | Username/email list | Provide all user names/emails that will use ServiceName1 |
| 10 | Enable WAF (for Fleet requests only) | □ Yes □ No | Wallam Application Firewall (WAF) provides API Security capabilities to protect your entire portfolio of APIs. Provides protection from API Abuse, API Leaks, Web attacks, API Attacks, Bots and, Issues and misconfigurations. It combines API discovery, risk management, real-time protection, and testing with advanced API security capabilities. |
Section 4: Request to delete existing services (Fleet/s or Devspace/s) in Kosmos
Note: For external customers in PROD environment, include this in your Knox request using the format below.
| Sr no | Property | Format | Comments |
|---|---|---|---|
| 1 | Project name | Project/Team name | Provide project/team information |
| 2 | Notification list | kosmospmo@joyent.com | Kosmos PMO team will be notified |
| 3 | Requested Kosmos services | □ Fleet/s □ Devspace/s | Clarify requested service(s). |
| If you have more than 1 service deletion requests | Please repeat row 4 for every service deletion request | ||
| 4 | Existing ServiceName1 | Existing FleetName1/DevspaceName1 Format: TeamName-ProjectName-ShortDesc (e.g., pmo-billingproject-billing) | Please provide the existing FleetName1/DevspaceName1 |
Note: All users under the service mentioned above will be nominated for deletion. If any listed users have more than one active service, they will not be deleted by the operator.
Tenant management approval in Kosmos for internal customers
I. Submit a Jira request
For internal customers, please submit a Jira request for either creating or deleting Kosmos services. Follow the appropriate section below and copy-paste only the relevant one into your Jira request.
For ease of use, clone the already created SAMPLE Jira request .
Section 1: Request to create new services (Fleet/s or Devspace/s) in Kosmos
Note: For internal customers – include the following format and details in your Jira request.
| Sr no | Property | Format | Comments |
|---|---|---|---|
| 1 | Project name | Project/Team name | Provide your project or team information. |
| 2 | Project purpose/scenario | (Please fill this out if you are skipping Section 1) Example: Statistics for mobile application update service / Service admin run query to get statistics for data analysis | Describe the project’s purpose or usage scenario. |
| 3 | Notification list | kosmospmo@joyent.com | The Kosmos PMO team will be notified. |
| 4 | Approval line | N/A | N/A |
| 5 | Requested Kosmos services | □ Fleet/s □ Devspace/s | Clarify the requested Kosmos service. |
| If you have more than one service request | Repeat rows 6–9 for each request | ||
| 6 | ServiceName1 | FleetName1 / DevspaceName1 Example (external customers): pmo-billingproject-billing | Provide the fleet or devspace name. |
| 7 | Cluster information | □ Devpool □ Sandbox | Indicate your preferred Devpool or Sandbox cluster configuration. Sandbox: with higher security levels based on the domain-based outbound traffic control. DevPool: with lower security levels without the outbound traffic control |
| 8 | Primary user information for managing service-name-1 | User Name, Samsung Email Example: John Doe, john.doe@samsung.com | Provide the primary user’s name and email. |
| 9 | Secondary user information using service-name-1 | Username-1/Email-1 Username-2/Email-2 … | Provide all secondary users’ names and emails who need access. |
Section 2: Request to delete existing services (Fleet/s or Devspace/s) in Kosmos
Note: For internal customers – include the following format and details in your Jira request.
| Sr no | Property | Format | Comments |
|---|---|---|---|
| 1 | Project name | Project/Team name | Provide your project or team information. |
| 2 | Notification list | kosmospmo@joyent.com | The Kosmos PMO team will be notified. |
| 3 | Requested Kosmos services | □ Fleet/s □ Devspace/s | Clarify the requested Kosmos service. If you have more than one service deletion request, repeat row 4 for each request. |
| If you have more than one service deletion request | Repeat rows 4 for each service | ||
| 4 | Existing service name 1 | Existing FleetName1 / DevspaceName1 Example (external customers): pmo-billingproject-billing | Provide the existing fleet or devspace name. |
Note:
- By default, all users under the service mentioned above will be nominated for deletion.
- If any of the users listed for deletion have more than one active service, the user will not be deleted by the operator.