Simple Log Service:Create and use a K8s Event Center

Alibaba Cloud Kubernetes

For an ACK cluster, the ack-node-problem-detector component already integrates the functionalities of eventer and node-problem-detector. You only need to deploy this component. For more information, see Event monitoring. For an ACK Serverless cluster, you must deploy the kube-eventer component.

NPD detects node problems or faults based on configurations and third-party plug-ins and then generates corresponding cluster events. The Kubernetes cluster also generates various events due to state transitions, such as pod evictions and image pull failures. The Kubernetes Event Center of Simple Log Service (SLS) aggregates all Kubernetes events in real time and provides storage, query, analysis, visualization, and alerting capabilities. The following steps describe how to send cluster events to the Kubernetes Event Center of SLS:

• If you selected Install node-problem-detector and Create Event Center when you created the cluster, proceed to Step 2 to view the Kubernetes Event Center. For more information about how to install the NPD component during cluster creation, see Create an ACK managed cluster.

• If you did not select Install node-problem-detector and Create Event Center when you created the cluster, you can install it manually.

  1. Log on to the ACK console. In the left navigation pane, click Clusters.

  2. On the Clusters page, click the name of the target cluster. In the left navigation pane, choose Operations Management > Components.

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

Other Kubernetes

1. Deploy kube-eventer.

   1. Install the kubectl tool. For more information, see Obtain a kubeconfig file and connect to a cluster by using kubectl.

   2. Create a file named eventer.yaml with the following content:

      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 endpoint of Simple Log Service. For more information, see Endpoints.
      project	string	Yes	The project in Simple Log Service.
      logStore	string	Yes	The Logstore in Simple Log Service. Note that the parameter is named logStore in the YAML file.
      internal	string	Required for self-managed Kubernetes.	Specifies whether to use an internal endpoint. Set this parameter to false for self-managed Kubernetes clusters.
      regionId	string	Required for self-managed Kubernetes.	The ID of the region where the Simple Log Service project resides. For more information, see Endpoints.
      accessKeyId	string	Required for self-managed Kubernetes.	The AccessKey ID. We recommend that you use the AccessKey pair of a RAM user. For more information, see AccessKey pair.
      accessKeySecret	string	Required for self-managed Kubernetes.	The AccessKey secret. We recommend that you use the AccessKey pair of a RAM user. For more information, see AccessKey pair.

   3. Run the following command to apply the configuration in eventer.yaml to the 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 node-problem-detector.

   For more information, see node-problem-detector on GitHub.