Simple Log Service:Collect Kubernetes events

Alibaba Cloud Kubernetes

For an ACK cluster, the ack-node-problem-detector component integrates the features of kube-eventer and node-problem-detector. You only need to deploy this component. For more information, see Event monitoring. For an ACK serverless cluster, you need to 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 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 Container Service Management Console . In the navigation pane on the left, 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 kubectl. For more information, see Obtain the kubeconfig file of a cluster and use kubectl to connect to the cluster.

   2. Create a configuration file named eventer.yaml 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

      Configuration	Type	Required	Description
      endpoint	string	Required	The endpoint of SLS. For more information, see Endpoints.
      project	string	Required	The project of SLS.
      logStore	string	Required	The logstore of SLS.
      internal	string	Self-managed Kubernetes cluster: Yes.	For a self-managed Kubernetes cluster, you must set this parameter to false.
      regionId	string	Self-managed Kubernetes cluster: Yes.	The ID of the region where SLS resides. For more information, see Endpoints.
      accessKeyId	string	Self-managed Kubernetes cluster: Yes.	The AccessKey ID. Use the AccessKey pair of a RAM user. For more information, see AccessKey pair.
      accessKeySecret	string	Self-managed Kubernetes cluster: Yes.	The AccessKey secret. Use the AccessKey pair of a RAM user. For more information, see AccessKey pair.

   3. Run the following command to apply the configurations from 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 the project on GitHub.