Container > NHN Container Service(NCS) > User Guide

Template

Template is a service that defines resources, such as Containers, Networks, etc., which needed to run Workload.

Create Template

You have to create Template before you can use NHN Container Service (NCS). Go to Container > NHN Container Service (NCS) page, click Template tab, and then click Create Template button. The following items are required to create Template.

Items Descriptions
Template Name Template Name, you can only enter the name of Template, lowercase letters within maximum 32 characters, numbers, and '-' .
Template Description Template Description
Containers Name Containers Name. You can enter lowercase letters, numbers, and '-' within maximum 253 characters.
Container Type Type of container
  • General: Containers that must remain running
  • Init: Containers that must be completed before running a normal container
Container Registry Registry of Container Image
  • For how to use NHN Container Registry (NCR), refer to NCR Usage Guide.
  • When using Docker Hub or other Registry, you have to select Registry Type.
Registry Type You can select from type of Registry, Public or Private.
Image URL Information about Container image, can be entered maximum 255 characters of alphabetic characters and numbers, only (-, _, ., , /, @, and :.
Registry ID ID used for Private Registry authentication
Registry Password Password used for Private Registry authentication
Memory Memory to assigned to Container
Port Ports used in Containers
CPU Enter the number of CPUs that you want to assign to Container, the number can be entered in units of 0.25 and between 0.25 and 16.
Whether to use GPU Decides whether the container uses a GPU.
GPU Type Decides the type of GPU to assign to a container.
Order Commands to be executed when Container is started, override ENTRYPPOINT specified in the image.
Argument Arguments to be passed when the container is started. Overrides the CMD specified in the image.
Task Directory Task Directory of Container takes precedence over the WORKDIR specified in the image.
Environment Variables Environment variables to set in Container
Life Cycle Hook You can set commands to run when the container is created and terminated.
If the command entered immediately after creation fails, the container is restarted.
If the container exits before the command runs, the command might not run.
  • The GracePeriodSeconds for the workload job is 30 seconds.
Immediately after creation (postStart) Example) bash,-c,curl $URL/postStart
Just before exit (preStop) Example) bash,-c,curl $URL/preStop
ConfigMap Files uploaded to Object Storage are available by mounting them in the container directory.
  • Appkey: Enter the appkey for the Object Storage service in your project that will use the file data.
  • User Access Key: Enter the user access key of the user accessing the Object Storage service. You can create and check the User Access Key on the Account > API Security Settings page of NHN Cloud Console.
  • User Secret Key: Enter the secret access key of the user accessing the Object Storage service. You can create and check the Secret Access Key on the Account > API Security Settings page of NHN Cloud Console.
  • Object URL: Enter the URL to download the object.
  • Container mount path: Enter the mount path for the container.
    • The file will be mounted at the path you entered.
Secret You can use the confidential data files you store in Secure Key Manager by mounting them in a container directory.
  • Key ID: Enter the ID of the confidential data type for the Secret Key Manager service.
  • Container mount path: Enter the mount path for the container.
    • The file will be mounted at the path you entered.
Connecting NAS storage Enter the NAS storage you want to connect to the container.
  • Name: Storage Name, which can be entered lowercase letters, numbers, and '-' maximum 63 characters.
  • NAS connection path: Enter the connection information of the NAS storage.
    • If you're using NAS storage, go to Storage > NAS page, enter the connection information for the NAS storage you want to connect to. For instructions, see the NAS User Guide.
    • If you're using a separately deployed NFSv3 server, enter the mount point of the NFS server.
  • Container connection path: Enter the mount path for the container.
    • Mounted to $container connection path/$storage name.
Only NAS storage that uses the same VPC as the template can be used.
Health Check You can configure commands to check the health of a container.
  • Activated or not (LivenessProbe): Determines whether the container is working.
  • Started or not (startupProbe): Determines whether the application inside the container has started.
If the health check fails, the container is restarted.
Execution timeout Only init containers can set execution timeout.
If not set, it is automatically set to 30 seconds.
If the execution timeout is exceeded, the workload changes to the Failed state.
Network Subnets defined in VPC that connect to workload
Template version name Template version name, you can only enter the name of Template, lowercase letters within maximum 16 characters, numbers, and -.
Template version description Description of the template version, which can be no more than 255 characters.
DNS Set the DNS servers used by the workload.
If not set, use 8.8.8.8.
If you need Private DNS integration, enter the Private DNS Server IP.
HostAliases Set the hostname to the IP address.

Enter the required information and click Create Template button to create Template.

[Caution] When a container (task) is restarted due to an NCS environment check or a temporary error, the created logs and data inside the container are initialized. For data that must be maintained after restart, use NAS storage.

[Note] Temporary shared storage between containers is providedin the path /var/${workload name}.

[Note] You can add only one port of the same protocol to Template. TCP and HTTP, HTTPS, and TERMINATED_HTTPS cannot use the same port. Using the HTTP and TERMINATED_HTTPS protocols adds an X-Forwarded-For Header that allows the load balancer to identify the Client IP.

[Note] Each container is provided with 20 GB of ephemeral storage. If you exceed the provided usage, the container is restarted and the ephemeral storage is reset.

[Note] The Configmaps and secrets use the information from when the template was created. If the original file or secret data is modified, the information in the already created template is not affected. Files are only accessible to the project Object Storage within the same organization. Confidential data utilizes Secure Key Manager in the same project. To use confidential data, you must first enable the Secure Key Manager service.

[Note] Init containers can only use TCP, UDP protocols. Init containers cannot use lifecycle hooks, health checks. Init containers are not included in load balancers.

Retrieve Template

You can retrieve Templates you created on Template tab of page Container > NHN Container Service (NCS). List of Templates displays the number of workloads in use, the latest template version, and the number of template versions.

Basic Information

You can check specific Template to view details from Basic Information tab.

Items Descriptions
Name Template name and ID
Descriptions Template description
Container The number of containers defined in the latest version of the template.
CPU The CPU count of the containers defined in the latest version of the template plus the number of CPUs
GPU The number of GPUs in the containers defined in the latest version of the template plus the number of GPUs
Date of Creation Creation date of Template
VPC VPC set to Template
Subnet Subnet set to Template
DNS DNS server information set in the template
HostAliases Information on HostAliases set in the template
Latest template version The latest version created in the template
Number of template versions Number of versions created for the template
Number of workloads in use Number of workloads using the template

Workloads in use

You can see a list of workloads that are using the template by clicking a specific template and then going to the Workload in use tab.

Delete Template

Select the template you want to delete and click Delete Template button to delete it.

[Note] You cannot delete Template if there is a workload using the template.

Create Version

In the list of templates, click View Version, and then click Create Version. The differences between creating a template and creating a version are shown below.

Items Descriptions
Template version Select the new version of the baseline template.
Modify Container The information set in the baseline template version is automatically added. For the AppKey, User Access Key, and User Secret Key information for registry accounts and configmaps, you can choose to use existing information or not.
Immediate deployment You can choose whether to apply the new version of the template immediately to workloads that are using the baseline template version. If you enable immediate deployment, the template on the workload changes on a rolling update basis.
Network You can't select the subnet to connect to your workload in Create Version; it uses the subnet you selected in Create Template.

View Version

You can view the version list by clicking View Versionin the template list. The version list shows the total number of container resources.

Basic Information

You can click a specific version to view details from the Basic Information tab.

Container

After clicking a specific version, you can go to Container tab to check the list of Containers have added to the version. You can select a specific container from the container list to check its details.

Items Descriptions
Containers Name Container Name
Type Container Type
Image URL Container Image Information
Memory Memory assigned to Container
CPU Number of CPU assigned to Container
GPU Information on GPU assigned to Container
Port Ports used in Containers
Command Command to run when container starts
Argument Arguments to be passed when the container is started
Task Directory Task Directory of Container
Environment Variables Environment variables set in Container
Storage Storage connected to Container
Life Cycle Hook Lifecycle hooks set on a container
ConfigMap Object files and mount paths associated with the container
Secret Confidential data associated with a container and its mount path
Health Check Check on the health of a container

Workloads in use

You can click a specific version and then go to the Workload in Use tab to see a list of workloads that are using that version.

Delete Version

Select the version you want to delete and click Delete Version button to delete it.

[Note] You cannot delete a version if there is a workload using the version.

Workload

Service that executes containers using the Template that you defined.

Create Workload

Go to Container > NHN Container Service (NCS) page, click Workload tab, and then click Create Workload button. The following items are required to create workloads.

Items Descriptions
Template Template Name
  • Click Select Template button to select from Templates created.
  • Click Select Template Version button to select from versions created in the template.
  • Click Manage Template to create a new template.
Name Workload Name, you can only enter lowercase letters, numbers, and '-' withi maximum 32 characters.
Descriptions Description of Workload. You can enter maximum 255 characters.
Number of tasks requested. Number of templates to run, you can enter values between 1 and 100.
Deployment controller You can select a deployment controller for the workload job.
  • Deployment: In a stateless manner, container IPs are fluid and tasks run in parallel.
  • StatefulSet: In a stateful manner, container IPs are fixed and tasks run sequentially.
Scheduled execution You can set up time-based schedules to schedule workload execution.
  • Base time: Specify the timezone for the scheduled task time.
  • Cron expression: You can enter the scheduled repeat cycle as a cron expression.
  • Number of scheduled execution histories: Enter the maximum number of archived ended scheduled tasks. Archived tasks can check logs, events, and container information.
  • Concurrency policy: Specify a concurrency policy for tasks generated by task repeat cycles.
    • Forbid: Do not run a new task unless the existing task completes.
    • Replace: The existing task is replaced with a new task. When replaced, no history of the existing task is left behind.
When you schedule workloads, the number of task request is 1 and the deployment controller is fixed as deployment,
If the workload execution interval is 10 minutes or less, you cannot enable the load balancer.
Schedule Termination You can set a scheduled termination time for your workloads.
  • Base time: Specify the timezone for the scheduled termination time of the task.
  • End date: You can enter a time when the task is terminated.
At the scheduled termination time, all tasks are terminated and all resources, including FIPs and domains, are deleted.
Load Balancer The Enable button is enabled only if a port is specified in the template's container information.
  • Floating IP: To use floating IP, Internet Gateway have to be connected to the configured Subnet.
    • To access your container from the outside, you need to use a floating IP. Using a floating IP adds a domain URL.
  • Health check: The load balancer attempts to check the health of the workload.
  • IP access control groups: You can apply access control groups to the load balancer.
  • If your container uses the TERMINATED_HTTPS protocol, you must register an SSL certificate.
  • The load balancer's ports and protocols use the ports and protocols defined in the template's container.
Load Balancers are not available in Legacy network environments.
Internal Load Balancer You can use communicable load balancers only within NCS. The Enable button is enabled only if a port is specified in the container information of the template.
  • IP: Specify the IP of the load balancer.
    • Auto-assigned: Use an IP assigned from the workload's subnet.
    • Specify: Use a specific IP. If you enter an IP that is in use by another resource, the workload cannot integrate with the other resource with that IP.
  • The internal load balancer only supports TCP, UDP protocols. If HTTP, HTTPS, or TERMINATED_HTTPS is specified, it is created after being changed to TCP.
Private DNS You can use any accessible domain within the VPC.
  • Private DNS Zone: Select the zone for which you want to create the recordset.
  • TTL: Enter the update period by the unit of second for record set information on the name server.
Security Group You can specify a security group for your workloads.
If you selected a workload security group, you must create security rules for the container ports.
If you do not select a workload security group, the security group created by NCS is applied and the security rules for the container ports are automatically created.

Enter the required information and click Create Workload button to create Workload.

[Note] The meaning of each field in cron expression (* * * * *) for the scheduled execution is as follows.

Field name Acceptable range of values Allowed special characters
Minute 0-59 * / , -
Hour 0-23 * / , -
Day 1-31 * / , ?
Month 1-12
JAN-DEC
* / , -
Day of the week 0-6
SUN-SAT
* / , ?

[Note] Local communication to the internal load balancer IP is not possible.

[Caution] If you delete a Private DNS Zone or Private DNS record set that is being used by a workload, domain association will not work within the VPC.

Retrieve Workload

You can check Workloads you create on Workloads tab on Container > NHN Container Service (NCS).

Basic Information

You can click on specific Workload to view details from the Basic Information tab.

Items Descriptions
Name Workload name and ID
Descriptions Workload description
Template Name of template used
Deployment controller Deployment controller for workload
Number of tasks requested. Number of Templates to run
Number of tasks executed Number of Templates executed
Date of Creation Date of Workload creation
VPC VPCs set to Workload
Subnet Subnet set to Workload
Security Group Name of Security Group set to Workload
Private DNS Private DNS information set up for workload
Load Balancer Load balancer information
Internal Load Balancer Internal load balancer information

[Note] Workload status is determined by considering condition of all Containers and Load Balancers included. You can see the status of individual Containers on Running Container tab.

Running Container

You can view Container details by clicking a specific workload and then clicking Container on Running Container tab.

Items Descriptions
Containers Name Container Name
Type Container Type
Image URL Container Image Information
IP IP assigned to Container
Status Status of Container
The number of Restart The number of time that Container restarted.
Memory Memory assigned to Container
CPU Number of CPU assigned to Container
GPU Information on GPU assigned to Container
Port Ports used in Containers
Command Command to run when container starts
Argument Arguments to be passed when the container is started
Task Directory Task Directory of Container
Environment Variables Environment variables set in Container
Storage Storage connected to Container
Life Cycle Hook Lifecycle hooks set on a container
ConfigMap Object files and mount paths associated with the container
Secret Confidential data associated with a container and its mount path
Health Check Check on the health of a container
Date of Restart Date Container restarted

Monitoring

After clicking a specific workload, you can find the resource usage of containers on the Monitoring tab. Container metrics are collected every 15 seconds and kept for up to 1 year. Items provided with monitoring are as follows.

Items Unit Descriptions
CPU Usage % Usage is provided based on CPU assigned to containers.
Memory Usage % Usage is provided based on Memory assigned to containers.
Network Data Trasmission bps Network data trasmission information is provided based on workload operation
Network Data Reception bps Network data reception information is provided based on workload operation
Disk Usage % Usage of NAS storage added to the container is provided.
Ephemeral Storage Usage % Temporary storage utilization is provided on a per-job basis for workloads.
GPU Usage % GPU usage assigned to the container is provided.
GPU Memory Usage % GPU memory usage allocated to the container is provided.
GPU Power Usage mW GPU power usage allocated to containers is provided.
GPU Temperature GPU temperature assigned to the container is provided.

Event

After clicking on specific Workload, you can view Event information from Container on Event tab. You can view events by status of Events by clicking Select Event Status.

Items Descriptions
Status Status of Event
Type Type of Event
Descriptions Event Description
Date of first occurrence of event Date of first occurrence of event
Date of last occurrence of event Date of last occurrence of event
Number of occurrences Number of times event occurred

[Note] Events are only kept for maximum 30 days, so information older than 30 days cannot be checked. Detailed reasons for the current and last state of the container can also be found in the events.

Log

After clicking a specific workload, you can view logs in Container from Log tab. If you do not specify time, the log is retrieved 5 minutes before the current time. If a lot of logs occurred during the time you want to view, you might only see some of them. If you don't see all the logs, reduce the time range and try again.

[Note] Logs are kept for 2 months.

Workload Execution History

You can check the progress and history of changes to the workload template in the Workload Execution History tab by selecting the workload for which you want to view the workload execution history.

Items Descriptions
Template Name Template name that workload is using
Execution time Deployment start time for workloads using the template
Termination Time Termination time for workload using the template
Status Deployment status
succeeded: Deployment completed
pending: Deploying
terminated: Ended workload

You can view the Details of workload execution history by clicking the retrieved history information.

[Note] The history of the running workload does not show a termination time and the status remains succeeded. [Caution] You cannot check the workload execution history after deleting the workload.

Scheduled Execution History

You can check the list of executed tasks in the Scheduled Execution History tab by selecting the workload for which you want to view the scheduled execution history.

Items Descriptions
Task ID Scheduled task ID that was executed
Execution time Execution time for scheduled task
Termination Time Termination time for scheduled task
Status Scheduled task status
waiting: Preparing schedule
running: Scheduled task running
completed: Scheduled task normally terminated
error: Scheduled task abnormally terminated

Change Workload

You can change the running workload by selecting a workload to change and clicking Change at the Basic Information tab.

Items Descriptions
Descriptions Workload Description
Template Change the template of a running workload
When changing the template, workload is deployed with zero downtime through the rolling update method.
Tasks are replaced one by one, so that during deployment, existing and new tasks can be executed at the same time.
You can see the results at the Workload Execution History tab.
Number of tasks requested. Change the number of tasks in a running workload
Increase tasks requested: Existing tasks are maintained and new tasks are created.
Decrease tasks requested: Tasks are terminated by the reduced number of tasks.
Schedule Termination Change the termination scheduling settings for a workload job
Scheduled execution Change scheduled execution information
The number of scheduled execution history is set from the time of change, and the number of history and setting values may not match until all tasks executed before the change are deleted.
Load Balancer Change whether a workload uses a load balancer, floating IP, health check, SSL certificate or not
Internal Load Balancer Change whether a workload uses an internal load balancer or not, and change IPs

[Caution] If you use a load balancer to make changes to the template while the workload is in service, downtime may occur.

[Note] If a workload is in the Pending, Suspended, or Terminated state, you cannot make changes to the load balancer. If the workload change fails (for example, an image error), the change attempt is terminated and no job replacement occurs.

Stop/Restart Workload

If you stop a workload, all tasks in the workload will be terminated.

If you restart a workload, load balancer IP is changed.

[Note] Depending on your deployment controller, running a workload stop/restart might cause the container IP to change.

[Caution] Logs, events, and ephemeral storage are initialized when the workload is stopped. Even if you stop the workload, the scheduled execution history is deleted during the task repeat cycle.

Delete Workload

Select a workload you want to delete and click Delete Workload button to proceed with the deletion.

Roles for NCS

You can set roles to control which roles can access NCS service and resources.

Modify NCS Roles

Set the role to execute NCS in the NHN Cloud Console screen. 1. Select Manage Member in the Project screen. 2. Select the member whose role you want to change. 3. Click Modify Role to add roles for each service. * Select the basic infrastructure service in the left area, then select the role in the right area. 4. Click Complete to apply the changed roles to the project members.

For more information about roles, see Manage members.

Details of Roles

To use NCS, you need the following roles.

Role Permission
Infrastructure MEMBER Basic Infrastructure Service Read
Infrastructure NCS ADMIN Create/Read/Update/Delete NCS
Infrastructure Security Group ADMIN Create/Read/Update/Delete Load Balancer
Infrastructure Load Balancer ADMIN Create, Read, Update, Delete Security Group

[Note] The Infrastructure NCS ADMIN, Infrastructure Load Balancer ADMIN, and Infrastructure Security Group ADMIN roles include the Infrastructure MEMBER role. Infrastructure ADMIN includes all roles in the underlying infrastructure services.

Assign Minimum Roles for NCS

In a production environment, it is recommended to add only the roles you need. The minimum roles to use the NCS service are as follows.

Features Infrastructure MEMBER Infrastructure NCS ADMIN Infrastructure Security Group ADMIN Infrastructure Load Balancer ADMIN
Retrieve Template O
Create Template O O
Delete Template O O
Retrieve Workload O
Create and Change Workload O O O
Delete Workload O O O

[Note] Infrastructure NCS ADMIN and Infrastructure Security Group ADMIN permissions are required to create templates. Infrastructure NCS ADMIN permissions alone are only for viewing.

Other considerations

Region

  • NCS service is only available in Korea (Pangyo) and Korea (Gwangju) regions.

Resource Provision Policy

Template/Container

  • Containers described in Template must be configured to use different container ports.
  • If you connect directly to Container Port, make sure that Security Group is well set up.
  • You cannot create Load Balancer if you use Template that does not specify Container Port.
  • You can create containers by utilizing Container images that exist in the following Private Registry.
  • Containers can be created by using container images that exist in private registries. The supported source registry types, URLs, Access IDs, and Access Secrets are as follows.
Source Registry Type Access ID Access Secret
Azure Container Registry Access Key User Name Access Key Password
Google Cloud Container Registry _json_key Private key of service account (JSON type)
Docker Hub Username Password
Harbor Username Password
Quay json_file {
"account_name": "$User account",
"docker_cli_password": "Encrypted Password generated by $Quay"
}
  • Within Container image, you must match Container Port in the Template with the Port that the Container decides to use for service.
    • If you use default nginx Container image that is designated to serve 80 ports, you have to specify 80 for the Container Port. If you change the content of Container image and set it up to serve another Port, you have to specify that Port number.
  • Configmaps and secrets use the information from when the template was created. If the original file or confidential data is modified, the information in the already created template is not affected.
    • To update the contents of Configmaps and secrets and reflect those changes, you need to create a new template or version and run the workload.

GPU

Category Type Name RAM Number of GPUs MIG Profile Name
Graphics Optimized ncs1 ncs1.g1m5 5GB 1 MIG 1g.5gb
Graphics Optimized ncs1 ncs1.g2m10 10GB 2 MIG 2g.10gb

Guide to Problem Solving

Explain how to solve various problems that may occur while using the NCS service

Workload

  • A container event with FailedCreatePodSandBox/CNITimedOutWaitingForVIFs type occurs when the workload is created normally, and the container is running properly
    • This event occurs when Network Interface for use in NCS is not created. This is a temporary event that occurs when a workload is created immediately after template creation or when a workload is created in bulk. The event does not occur after a certain amount of time has elapsed.
  • A container event with IpAddressGenerationFailure type occurs when the workload is pending
    • This event occurs when there are no more IP addresses available in the specified subnet. You must create Template by changing the CIDR of the subnet or using other subnet.
  • Workloads remain pending after changing the workload template
    • You can check the Event of the added task to find why the container is not running.
  • An event where creating workloads fails due to insufficient resources
Error Message Descriptions
{{.Resource}} Could not create a workload due to insufficient resources. Could not create a workload due to insufficient resources for NCS environment.
Try again after a while or contact the Customer Center.
Exceeded the number of {{.Resource}} that can be created. Please contact the Customer Center to increase the limit. Exceeded the NCS quota for the project.
For more details, refer to NHN Container Service(NCS) Resource Provision Policy.

Integrate with NHN Cloud Service

Integrate with Log & Crash Search Service

When workloads are deleted or restarted, logs are deleted and cannot be viewed. To back up important logs or to search and view specific logs, you can integrate with the Log & Crash Search (L&C) service.

The following describes how to create a logging agent (FluentBit, Logstash) as a sidecar container and integrate it with L&C.

For more information about FluentBit, see Fluent Bit: Official Manual. For more information about Logstash, see Logstash Reference. To learn how to use Log & Crash Search, see the Log & Crash Search Console User Guide.

[Note] We've described how to create logs as a file on temporary shared storage between containers. If you generate container logs as files, you cannot view them in the Logs tab of the workload.

Integration through FluentBit

  • In order for FluentBit to work with L&C, you need to create a configuration file. Create a configuration file as shown below and upload it to Object Storage.
[SERVICE]
    Flush 1
    Daemon Off
    Log_Level warn
    Parsers_File parsers.conf
    Plugins_File plugins.conf
    HTTP_Server Off

[INPUT].
    Name tail
    Path /var/{workload name}/{log file name}

[OUTPUT]
    Name http
    Match * Β
    Host api-logncrash.cloud.toast.com
    Port 443
    URI /v2/log
    Format json
    Log_response_payload false
    Tls On
    Tls.verify Off

[FILTER]
    Name modify
    Match * Β
    Rename log body
    Add host ${HOSTNAME}
    Add projectName {L&C AppKey}
    Add projectVersion {Customized project version}
    Add logVersion {log format version}
    Add logType {log type}
    Add logSource {Log Source}
    Add logLevel {Log Level}
  • Create by adding a container to the template as shown below.
Items alpine (create log) fluentbit (send og)
Containers Name alpine fluentbit
Image URL alpine:latest fluent/fluent-bit:2.2.1
Order To write the log to a file, enter as follows.
  • sh,-c,while true; do echo "hello world" >> /var/{workload name}/{log file name}; sleep 1; done
ConfigMap Add information to import the fluentbit configuration file that you uploaded to Object Storage.
Enter the container mount path as follows.
  • /fluent-bit/etc/fluent-bit.conf
  • When you create a workload with that template, the logs generated by alpine can be searched and viewed in L&C.

Integration through Logstash

  • In order for Logstash to work with L&C, you need to create a configuration file. Create a configuration file as shown below and upload it to Object Storage.
input {
  file {
    path => "/var/{workload name}/{log filename}
    start_position => "beginning"
    ignore_older => 0
  }
}

filter {
  mutate {
    remove_field => [ "@version", "@timestamp", "path", "tags" ]
    rename => {
      "message" => "body"
      "host" => "host"
    }
    add_field => {
      "projectName" => "{L&C AppKey}"
      "projectVersion" => "{Customized project version}"
      "logVersion" => "{Log format version}"
      "logType" => "{Log Type}"
      "logSource" => "{Log Source}"
      "logLevel" => "{Log Level}"
    }
  }
}

output {
  http {
    url => "https://api-logncrash.cloud.toast.com/v2/log"
    http_method => "post"
    format => "json"
    ssl_verification_mode => "none"
  }
}
  • Create by adding a container to the template as shown below.
Items alpine (create log) logstash (send log)
Containers Name alpine logstash
Image URL alpine:latest logstash:8.11.0
Memory 256 1024
Order To write the log to a file, enter as follows.
  • sh,-c,while true; do echo "hello world" >> /var/{workload name}/{log file name}; sleep 1; done
Environment Variables XPACK_MONITORING_ENABLED : false
ConfigMap Add information to import the logstash configuration file that you uploaded to Object Storage.
Enter the container mount path as follows.
  • /usr/share/logstash/pipeline/logstash.conf
  • When you create a workload with that template, the logs generated by alpine can be searched and viewed in L&C.
TOP