clsDetail:
  ## If the log topic is created automatically, the names of logset and topic need to be specified at the same time.
  logsetName: test                    ## CLS logset name. Logset for the name will be created automatically if there is not any. If there is the logset, log topic will be created under it.
  topicName: test                     ## CLS log topic name. Log topic for the name will be created automatically if there is not any.

  # Select an existing logset and log topic. If the logset is specified but the log topic is not, a log topic will be created automatically.
  logsetId: xxxxxx-xx-xx-xx-xxxxxxxx  ## The ID of the CLS logset. The logset needs to be created in advance in CLS.
  topicId: xxxxxx-xx-xx-xx-xxxxxxxx       ## CLS log topic ID. The log topic needs to be created in CLS in advance and should not be occupied by other collection configurations.

  logType: json_log  ## Log collection format. json_log: json format. delimiter_log: separator-based format. minimalist_log: full text in a single line. multiline_log: full text in multi lines. fullregex_log: full regex format. Default value: minimalist_log
  logFormat: xxx                      ## Log formatting method
  period: 30                          ## Lifecycle in days. Value range: 1–3600. `3640` indicates permanent storage.
  partitionCount:                     ## The number (an integer) of log topic partitions. Default value: `1`. Maximum value: `10`.
  tags:                             ## Tag description list. This parameter is used to bind a tag to a log topic. Up to nine tag key-value pairs are supported, and a resource can be bound to only one tag key.
   - key: xxx                         ## Tag key
   value: xxx                       ## Tag value
  autoSplit: false                   ## Whether to enable automatic split (Boolean type). Default value: `true`.
  maxSplitPartitions:
  storageType: hot                 ## Log topic storage class. Valid values: `hot` (STANDARD); `cold` (STANDARD_IA). Default value: `hot`.
  excludePaths:                      ## Collection path blocklist
    - type: File                      ## Type. Valid values: `File`, `Path`. 
        value: /xx/xx/xx/xx.log            ## The value of `type`
  indexs:                            ## You can customize the indexing method and field when creating a topic. 
    - indexName:    ## When a key value or metafield index needs to be configured for a field, the metafield `Key` does not need to be prefixed with `__TAG__.` and is consistent with the one when logs are uploaded. `__TAG__.` will be prefixed automatically for display in the console.
        indexType:    ## Field type. Valid values: `long`, `text`, `double`
        tokenizer:    ## Field delimiter. Each character represents a delimiter. Only English symbols and \\n\\t\\r are supported. For `long` and `double` fields, leave it empty. For `text` fields, we recommend you use @&?|#()='",;:<>[]{}/ \\n\\t\\r\\ as the delimiter.
        sqlFlag:     ## Whether the analysis feature is enabled for the field (Boolean)
        containZH:  ## Whether Chinese characters are contained (Boolean)
  region: ap-xxx                      ## Topic region for cross-region shipping
  userDefineRule: xxxxxx              ## Custom collection rule, which is a serialized JSON string
  extractRule: {}                     ## Extraction and filter rule. If `ExtractRule` is set, `LogType` must be set.


inputDetail:
  type: container_stdout  ## Log collection type, including container_stdout (container standard output), container_file (container file), and host_file (host file)

  containerStdout:        ## Container standard output
    namespace: default    ## The Kubernetes namespace of the container to be collected. Separate multiple namespaces by comma, for example, `default,namespace`. If this field is not specified, it indicates all namespaces. Note that this field cannot be specified if `excludeNamespace` is specified.
    excludeNamespace: nm1,nm2  ## The Kubernetes namespace of the container to be excluded. Separate multiple namespaces by comma, for example, `nm1,nm2`. If this field is not specified, it indicates all namespaces. Note that this field cannot be specified if `namespace` is specified.
    nsLabelSelector: environment in (production),tier in (frontend) ## Filter namespaces by namespace label
    allContainers: false       ## Whether to collect the standard output of all containers in the specified namespace. Note that if `allContainers=true`, you cannot specify `workload`, `includeLabels`, and `excludeLabels` at the same time.
    container: xxx             ## Name of the container of which the logs will be collected. If the name is empty, it indicates the log names of all matching containers will be collected. 
    excludeLabels:  ## Pods with the specified labels will be excluded. This field cannot be specified if `workload`, `namespace`, and `excludeNamespace` are specified.
      key2: value2  ## Pods with multiple values of the same key can be matched. For example, if you enter `environment = production,qa`, Pods with the `production` or `qa` value of the `environment` key will be excluded. Separate multiple values by comma. If you also specify `includeLabels`, Pods in the intersection will be matched.

    includeLabels:  ## Pods with the specified labels will be collected. This field cannot be specified if `workload`, `namespace`, and `excludeNamespace` are specified.
      key: value1  ## The `metadata` will be carried in the log collected based on the collection rule and reported to the consumer. Pods with multiple values of the same key can be matched. For example, if you enter `environment = production,qa`, Pods with the `production` or `qa` value of the `environment` key will be matched. Separate multiple values by comma. If you also specify `excludeLabels`, Pods in the intersection will be matched.

    metadataLabels:           ## Specify the Pod labels to be collected as the metadata. If this field is not specified, all Pod labels will be collected as the metadata.
    - label1
    customLabels:             ## Custom metadata
      label: l1

    workloads:
    - container: xxx  ## Name of the container to collect. If this parameter is not specified, it indicates all containers in the workload Pod will be collected.
      kind: deployment  ## Workload type. Supported values include deployment, daemonset, statefulset, job, and cronjob.
      name: sample-app  ## Workload name
      namespace: prod  ## Workload namespace

  containerFile:  ## File in the container
    namespace: default      ## The Kubernetes namespace of the container to be collected. A namespace must be specified.
    excludeNamespace: nm1,nm2   ## The Kubernetes namespace of the container to be excluded. Separate multiple namespaces by comma, for example, `nm1,nm2`. If this field is not specified, it indicates all namespaces. Note that this field cannot be specified if `namespace` is specified.
    nsLabelSelector: environment in (production),tier in (frontend) ## Filter namespaces by namespace label
    container: xxx          ## The name of container of which the logs will be collected. The * indicates the log names of all matching containers will be collected.
    logPath: /var/logs      ## Log folder. Wildcards are not supported.
    filePattern: app_*.log  ## Log file name. It supports the wildcards "*" and "?". "*" matches multiple random characters, and "?" matches a single random character.
    customLabels:  ## Custom metadata
      key: value
    excludeLabels:  ## Pods with the specified labels will be excluded. This field cannot be specified if `workload` is specified.
      key2: value2  ## Pods with multiple values of the same key can be matched. For example, if you enter `environment = production,qa`, Pods with the `production` or `qa` value of the `environment` key will be excluded. Separate multiple values by comma. If you also specify `includeLabels`, Pods in the intersection will be matched.

    includeLabels:  ## Pods with the specified labels will be collected. This field cannot be specified if `workload` is specified.
      key: value1  ## The `metadata` will be carried in the log collected based on the collection rule and reported to the consumer. Pods with multiple values of the same key can be matched. For example, if you enter `environment = production,qa`, Pods with the `production` or `qa` value of the `environment` key will be matched. Separate multiple values by comma. If you also specify `excludeLabels`, Pods in the intersection will be matched.
    metadataLabels:      ## Specify the Pod labels to be collected as the metadata. If this field is not specified, all Pod labels will be collected as the metadata.
    - label1             ## Pod label
    workload:
      container: xxx    ## Name of the container to collect. If this parameter is not specified, it indicates all containers in the workload Pod will be collected.
      name: sample-app  ## Workload name

apiVersion: cls.cloud.tencent.com/v1
kind: LogConfig
spec:
   inputDetail:
     type: container_stdout
     containerStdout:
       namespace: default
       allContainers: true
 ...

apiVersion: cls.cloud.tencent.com/v1
kind: LogConfig
spec:
   inputDetail:
     type: container_stdout
     containerStdout:
       allContainers: false
       workloads:
       - namespace: production
         name: ingress-gateway
         kind: deployment
  ...

apiVersion: cls.cloud.tencent.com/v1
kind: LogConfig
spec:
   inputDetail:
     type: container_stdout
     containerStdout:
       namespace: production
       allContainers: false
       includeLabels:
         k8s-app: nginx
  ...

apiVersion: cls.cloud.tencent.com/v1
kind: LogConfig
spec:
   topicId: xxxxxx-xx-xx-xx-xxxxxxxx
   inputDetail:
     type: container_file
     containerFile:
       namespace: production
       workload:
         name: ingress-gateway
         type: deployment
       container: nginx
       logPath: /data/nginx/log
       filePattern: access.log
  ...

apiVersion: cls.cloud.tencent.com/v1
kind: LogConfig
spec:
   inputDetail:
     type: container_file
     containerFile:
       namespace: production
       includeLabels:
         k8s-app: ingress-gateway
       container: nginx
       logPath: /data/nginx/log
       filePattern: access.log
  ...