Simple Log Service:Create and use an event center

ACK cluster

If you use an ACK cluster, you need to only deploy the ack-node-problem-detector component because the component is integrated with the features of the kube-eventer and node-problem-detector components. For more information, see Event monitoring. If you use an ACK Serverless cluster, you must deploy the kube-eventer component.

NPD works with third-party plug-ins to detect node exceptions and generate cluster events. A Kubernetes cluster also generates events when the status of the cluster changes. For example, when a pod is evicted or an image pull operation fails, a related event is generated. The Kubernetes event center of Simple Log Service collects, stores, and visualizes cluster events. It allows you to query and analyze these events, and configure alerts. You can sink cluster events to the Kubernetes event center of Simple Log Service by using the following methods.

• If you have selected Install node-problem-detector and Create Event Center when you create the cluster, proceed to Step 2 to view the Kubernetes event center. For more information about how to install the ack-node-problem-detector component when you create a cluster, see Create an ACK managed cluster.

• If you did not select Install node-problem-detector and Create Event Center when you create the cluster, perform the following steps to manually install it.

  1. Log on to the ACK console.

  2. On the Clusters page, find the cluster that you want to manage and click its name. In the left-side navigation pane, choose Operations > Add-ons.

  3. On the Logging and Monitoring tab, find and install ack-node-problem-detector.

Other Kubernetes cluster

1. Deploy the kube-eventer component.

   1. Install the kubectl tool. For more information, see Connect to an ACK cluster by using kubectl.

   2. Create a configuration file named eventer.yaml by using the following sample code:

      apiVersion: apps/v1
      kind: Deployment
      metadata:
        labels:
          name: kube-eventer
        name: kube-eventer
        namespace: kube-system
      spec:
        replicas: 1
        selector:
          matchLabels:
            app: kube-eventer
        template:
          metadata:
            labels:
              app: kube-eventer
            annotations:
              scheduler.alpha.kubernetes.io/critical-pod: ''
          spec:
            dnsPolicy: ClusterFirstWithHostNet
            serviceAccount: kube-eventer
            containers:
              - image: registry.cn-hangzhou.aliyuncs.com/acs/kube-eventer:v1.2.5-cc7ec54-aliyun
                name: kube-eventer
                command:
                  - "/kube-eventer"
                  - "--source=kubernetes:https://kubernetes.default"
                  ## .send to sls
                  ## --sink=sls:https://{endpoint}?project={project}&logStore=k8s-event&regionId={region-id}&internal=false&accessKeyId={accessKeyId}&accessKeySecret={accessKeySecret}
                  - --sink=sls:https://cn-beijing.log.aliyuncs.com?project=k8s-xxxx&logStore=k8s-event&regionId=cn-beijing&internal=false&accessKeyId=xxx&accessKeySecret=xxx
                env:
                  # If TZ is assigned, set the TZ value as the time zone
                  - name: TZ
                    value: "Asia/Shanghai"
                volumeMounts:
                  - name: localtime
                    mountPath: /etc/localtime
                    readOnly: true
                  - name: zoneinfo
                    mountPath: /usr/share/zoneinfo
                    readOnly: true
                resources:
                  requests:
                    cpu: 10m
                    memory: 50Mi
                  limits:
                    cpu: 500m
                    memory: 250Mi
            volumes:
              - name: localtime
                hostPath:
                  path: /etc/localtime
              - name: zoneinfo
                hostPath:
                  path: /usr/share/zoneinfo
      ---
      apiVersion: rbac.authorization.k8s.io/v1
      kind: ClusterRole
      metadata:
        name: kube-eventer
      rules:
        - apiGroups:
            - ""
          resources:
            - events
          verbs:
            - get
            - list
            - watch
      ---
      apiVersion: rbac.authorization.k8s.io/v1
      kind: ClusterRoleBinding
      metadata:
        name: kube-eventer
      roleRef:
        apiGroup: rbac.authorization.k8s.io
        kind: ClusterRole
        name: kube-eventer
      subjects:
        - kind: ServiceAccount
          name: kube-eventer
          namespace: kube-system
      ---
      apiVersion: v1
      kind: ServiceAccount
      metadata:
        name: kube-eventer
        namespace: kube-system

      Parameter	Type	Required	Description
      endpoint	string	Yes	The Simple Log Service endpoint. For more information, see Endpoints.
      project	string	Yes	The Simple Log Service project.
      logStore	string	Yes	The Simple Log Service Logstore.
      internal	string	Yes for self-managed Kubernetes clusters	If you use a self-managed Kubernetes cluster, set the value to false.
      regionId	string	Yes for self-managed Kubernetes clusters	The ID of the region where the Simple Log Service project resides. For more information, see Endpoints.
      accessKeyId	string	Yes for self-managed Kubernetes clusters	The AccessKey ID. We recommend that you use the AccessKey ID of a Resource Access Management (RAM) user. For more information, see AccessKey pair.
      accessKeySecret	string	Yes for self-managed Kubernetes clusters	The AccessKey secret. We recommend that you use the AccessKey secret of a RAM user. For more information, see AccessKey pair.

   3. Run the following command to apply the eventer.yaml configuration file to your cluster:

      kubectl apply -f eventer.yaml

      Expected output:

      deployment.apps/kube-eventer created
      clusterrole.rbac.authorization.k8s.io/kube-eventer created
      clusterrolebinding.rbac.authorization.k8s.io/kube-eventer created
      serviceaccount/kube-eventer created

2. Deploy the node-problem-detector component.

   For more information, visit GitHub.