会启动两个event记录器,v1beta1、corev1,调度器记录pod调度失败或成功用的是betav1:
kube-scheduler记录的leader选举的event,lastTimestamp和firstTimestamp不为null,managedFields中为corev1版本的event
- apiVersion: v1count: 1eventTime: nullfirstTimestamp: "2020-07-30T06:42:40Z"involvedObject:apiVersion: v1kind: Endpointsname: kube-schedulernamespace: kube-systemresourceVersion: "115903"uid: 75a27c53-d056-4537-98fa-b597d8e10b7ckind: EventlastTimestamp: "2020-07-30T06:42:40Z"message: liabio_8678aab6-5a90-4c9d-930c-e555b37b0d94 became leadermetadata:creationTimestamp: "2020-07-30T06:42:40Z"managedFields:- apiVersion: v1fieldsType: FieldsV1fieldsV1:f:count: {}f:firstTimestamp: {}f:involvedObject:f:apiVersion: {}f:kind: {}f:name: {}f:namespace: {}f:resourceVersion: {}f:uid: {}f:lastTimestamp: {}f:message: {}f:reason: {}f:source:f:component: {}f:type: {}manager: kube-scheduleroperation: Updatetime: "2020-07-30T06:42:40Z"name: kube-scheduler.162674a2ae483d50namespace: kube-systemresourceVersion: "115905"selfLink: /api/v1/namespaces/kube-system/events/kube-scheduler.162674a2ae483d50uid: a0fa7122-1cf9-411d-8e37-de146c5c8192reason: LeaderElectionreportingComponent: ""reportingInstance: ""source:component: default-schedulertype: Normal
kube-scheduler记录的调度pod失败的event,lastTimestamp和firstTimestamp为null,managedFields中为v1beta1版本的event:
- action: SchedulingapiVersion: v1eventTime: "2020-07-30T04:00:59.833687Z"firstTimestamp: nullinvolvedObject:apiVersion: v1kind: Podname: coredns-66bff467f8-2qctwnamespace: kube-systemresourceVersion: "85531"uid: 8bfca0dd-6fdb-4893-ad3d-62d037d6dafakind: EventlastTimestamp: nullmessage: '0/1 nodes are available: 1 node(s) were unschedulable.'metadata:creationTimestamp: "2020-07-30T04:00:59Z"managedFields:- apiVersion: events.k8s.io/v1beta1fieldsType: FieldsV1fieldsV1:f:action: {}f:deprecatedSource:f:component: {}f:eventTime: {}f:note: {}f:reason: {}f:regarding:f:apiVersion: {}f:kind: {}f:name: {}f:namespace: {}f:resourceVersion: {}f:uid: {}f:reportingController: {}f:reportingInstance: {}f:series:.: {}f:count: {}f:lastObservedTime: {}f:state: {}f:type: {}manager: kube-scheduleroperation: Updatetime: "2020-07-30T06:30:43Z"name: coredns-66bff467f8-2qctw.16266bd02ee73afenamespace: kube-systemresourceVersion: "114343"selfLink: /api/v1/namespaces/kube-system/events/coredns-66bff467f8-2qctw.16266bd02ee73afeuid: 7863f604-9b8e-4ed8-bd04-a150451fc528reason: FailedSchedulingreportingComponent: default-schedulerreportingInstance: default-scheduler-liabioseries:count: 99lastObservedTime: "2020-07-30T06:29:29.921206Z"source:component: default-schedulertype: Warning
bind成功的event:lastTimestamp和firstTimestamp为null,managedFields中为v1beta1版本的event:
- action: BindingapiVersion: v1eventTime: "2020-07-30T06:45:54.316058Z"firstTimestamp: nullinvolvedObject:apiVersion: v1kind: Podname: coredns-66bff467f8-2qctwnamespace: kube-systemresourceVersion: "116337"uid: 8bfca0dd-6fdb-4893-ad3d-62d037d6dafakind: EventlastTimestamp: nullmessage: Successfully assigned kube-system/coredns-66bff467f8-2qctw to liabiometadata:creationTimestamp: "2020-07-30T06:45:54Z"managedFields:- apiVersion: events.k8s.io/v1beta1fieldsType: FieldsV1fieldsV1:f:action: {}f:deprecatedSource:f:component: {}f:eventTime: {}f:note: {}f:reason: {}f:regarding:f:apiVersion: {}f:kind: {}f:name: {}f:namespace: {}f:resourceVersion: {}f:uid: {}f:reportingController: {}f:reportingInstance: {}f:type: {}manager: kube-scheduleroperation: Updatetime: "2020-07-30T06:45:54Z"name: coredns-66bff467f8-2qctw.162674cfec0294fcnamespace: kube-systemresourceVersion: "116340"selfLink: /api/v1/namespaces/kube-system/events/coredns-66bff467f8-2qctw.162674cfec0294fcuid: a2bb6ee3-a6fb-4d98-985e-eb15b0202b96reason: ScheduledreportingComponent: default-schedulerreportingInstance: default-scheduler-liabiosource:component: default-schedulertype: Normal
