apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 37775daa-0faf-434a-beb0-e40b36be90f5
    resourceVersion: "27427"
    uid: 2aafeda7-8aaa-4467-8fa2-c53eddf329b1
  spec:
    sourcePod: network-check-source-7cbc45fddc-lcmjp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:27:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.1165ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:00Z"
    - latency: 901.062µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:00Z"
    - latency: 951.964µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:00Z"
    - latency: 1.082508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:00Z"
    - latency: 1.231981ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:00Z"
    - latency: 946.807µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:57:00Z"
    - latency: 973.476µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:56:00Z"
    - latency: 2.086084ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:55:00Z"
    - latency: 1.119937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:54:00Z"
    - latency: 869.053µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:53:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 37775daa-0faf-434a-beb0-e40b36be90f5
    resourceVersion: "27428"
    uid: 5096f431-dddd-4ac1-8baa-edbd4ef0edf6
  spec:
    sourcePod: network-check-source-7cbc45fddc-lcmjp
    targetEndpoint: a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:26:00Z"
      message: 'load-balancer-api-external: tcp connection to a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.200584ms
      message: 'load-balancer-api-external: tcp connection to a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:00Z"
    - latency: 7.180751ms
      message: 'load-balancer-api-external: resolved host name a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:02:00Z"
    - latency: 5.28603ms
      message: 'load-balancer-api-external: tcp connection to a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:00Z"
    - latency: 6.825235ms
      message: 'load-balancer-api-external: resolved host name a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:01:00Z"
    - latency: 4.953852ms
      message: 'load-balancer-api-external: tcp connection to a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:00Z"
    - latency: 7.014853ms
      message: 'load-balancer-api-external: resolved host name a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:00:00Z"
    - latency: 4.508894ms
      message: 'load-balancer-api-external: tcp connection to a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:00Z"
    - latency: 6.758709ms
      message: 'load-balancer-api-external: resolved host name a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:59:00Z"
    - latency: 3.790052ms
      message: 'load-balancer-api-external: tcp connection to a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:00Z"
    - latency: 7.60777ms
      message: 'load-balancer-api-external: resolved host name a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:58:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 37775daa-0faf-434a-beb0-e40b36be90f5
    resourceVersion: "27429"
    uid: 35c99e8a-9161-4dd6-973a-7ef115622d95
  spec:
    sourcePod: network-check-source-7cbc45fddc-lcmjp
    targetEndpoint: a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:26:00Z"
      message: 'load-balancer-api-internal: tcp connection to a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 10.852136ms
      message: 'load-balancer-api-internal: tcp connection to a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:00Z"
    - latency: 7.105433ms
      message: 'load-balancer-api-internal: resolved host name a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:02:00Z"
    - latency: 5.333231ms
      message: 'load-balancer-api-internal: tcp connection to a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:00Z"
    - latency: 6.749413ms
      message: 'load-balancer-api-internal: resolved host name a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:01:00Z"
    - latency: 4.915916ms
      message: 'load-balancer-api-internal: tcp connection to a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:00Z"
    - latency: 7.082104ms
      message: 'load-balancer-api-internal: resolved host name a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:00:00Z"
    - latency: 4.562008ms
      message: 'load-balancer-api-internal: tcp connection to a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:00Z"
    - latency: 6.692269ms
      message: 'load-balancer-api-internal: resolved host name a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:59:00Z"
    - latency: 5.079877ms
      message: 'load-balancer-api-internal: tcp connection to a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:00Z"
    - latency: 7.495953ms
      message: 'load-balancer-api-internal: resolved host name a1afdb880dbab4dc2948dad861f9dd20-4600d37d7b894b06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:58:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-network-check-target-ip-10-0-129-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 37775daa-0faf-434a-beb0-e40b36be90f5
    resourceVersion: "27424"
    uid: 3914ff85-0ece-4bc3-aa9c-fce43fc11891
  spec:
    sourcePod: network-check-source-7cbc45fddc-lcmjp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:27:00Z"
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.020521ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:00Z"
    - latency: 1.914376ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:00Z"
    - latency: 2.043959ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:00Z"
    - latency: 2.073164ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:00Z"
    - latency: 1.803457ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:00Z"
    - latency: 1.978062ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:57:00Z"
    - latency: 1.952059ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:56:00Z"
    - latency: 2.064254ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:55:00Z"
    - latency: 2.102703ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:54:00Z"
    - latency: 1.854866ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:53:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-network-check-target-ip-10-0-140-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 37775daa-0faf-434a-beb0-e40b36be90f5
    resourceVersion: "27423"
    uid: 49b100e3-57c4-428d-92b7-890b2537e62d
  spec:
    sourcePod: network-check-source-7cbc45fddc-lcmjp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:27:00Z"
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.126948ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:00Z"
    - latency: 840.963µs
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:00Z"
    - latency: 757.049µs
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:00Z"
    - latency: 1.045815ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:00Z"
    - latency: 1.377397ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:00Z"
    - latency: 778.76µs
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:57:00Z"
    - latency: 891.256µs
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:56:00Z"
    - latency: 1.149407ms
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:55:00Z"
    - latency: 855.58µs
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:54:00Z"
    - latency: 897.831µs
      message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:53:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-network-check-target-ip-10-0-143-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 37775daa-0faf-434a-beb0-e40b36be90f5
    resourceVersion: "27426"
    uid: 9d81e9bd-9a3d-404c-bf51-72f203e44c0d
  spec:
    sourcePod: network-check-source-7cbc45fddc-lcmjp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:27:00Z"
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.400383ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:00Z"
    - latency: 2.082649ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:00Z"
    - latency: 2.114669ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:00Z"
    - latency: 2.224648ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:00Z"
    - latency: 2.112308ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:00Z"
    - latency: 2.360775ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:57:00Z"
    - latency: 2.36262ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:56:00Z"
    - latency: 2.408876ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:55:00Z"
    - latency: 2.091098ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:54:00Z"
    - latency: 1.866473ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:53:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-94-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-94.ec2.internal
      uid: 37775daa-0faf-434a-beb0-e40b36be90f5
    resourceVersion: "27425"
    uid: 696df127-ef7c-4976-b7de-2a700733827a
  spec:
    sourcePod: network-check-source-7cbc45fddc-lcmjp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:26:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.118325ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:00Z"
    - latency: 2.01706ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:02:00Z"
    - latency: 914.042µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:00Z"
    - latency: 1.523658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:01:00Z"
    - latency: 803.327µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:00Z"
    - latency: 1.684119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:00:00Z"
    - latency: 995.852µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:00Z"
    - latency: 1.855634ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:59:00Z"
    - latency: 1.058463ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:00Z"
    - latency: 2.270406ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:58:00Z"
kind: List
metadata:
  resourceVersion: ""