Simple Log Service:Create and use the K8s Event Center

Alibaba Cloud Kubernetes

For an ACK cluster, the ack-node-problem-detector component integrates kube-eventer and Node Problem Detector (NPD). Deploy only this component as described in Event monitoring. For an ACK Serverless cluster, deploy the kube-eventer component separately.

NPD uses configurations and third-party plug-ins to detect node issues and generate corresponding cluster events. A Kubernetes cluster also generates its own events during state transitions, such as pod evictions or image pull failures. The Kubernetes Event Center of Simple Log Service (SLS) centralizes all Kubernetes events in real time and provides storage, query, analysis, visualization, and alerting. To integrate your cluster events with the Kubernetes Event Center, follow these steps:

• If you selected Install node-problem-detector and Create Event Center during cluster creation, you can skip to Step 2 to view the Kubernetes Event Center. For 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 during cluster creation, follow these steps to 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-side navigation pane, choose Operations > Add-ons.

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

Other Kubernetes clusters

1. Deploy kube-eventer.

   1. Install kubectl by following Obtain the kubeconfig file of a cluster and use kubectl to connect to the cluster.

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

      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 SLS endpoint. Endpoints.
      Project	string	Yes	The SLS Project.
      Logstore	string	Yes	The SLS Logstore.
      internal	string	This parameter is required for self-managed Kubernetes clusters.	Set to false for self-managed Kubernetes clusters.
      region ID	string	This parameter is required for self-managed Kubernetes clusters.	The region ID of the SLS Project. Endpoints.
      AccessKey ID	string	This parameter is required for self-managed Kubernetes clusters.	The AccessKey ID. We recommend that you use a RAM user's AccessKey pair. AccessKey pair.
      AccessKey Secret	string	This parameter is required for self-managed Kubernetes clusters.	The AccessKey Secret. We recommend that you use a RAM user's AccessKey pair. AccessKey pair.

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

   node-problem-detector on GitHub.