apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T07:14:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 0e4fa577-f0ac-436c-b15a-0856e03ee95a
    resourceVersion: "68444"
    uid: 2092af34-16fe-4369-a15c-5baa1483ee2d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdxgf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T07:22:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.755µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:04:01Z"
    - latency: 1.131792ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:03:01Z"
    - latency: 1.073626ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:02:01Z"
    - latency: 803.715µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:01:01Z"
    - latency: 1.054048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:00:01Z"
    - latency: 1.014476ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:59:01Z"
    - latency: 1.314965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:58:01Z"
    - latency: 1.207465ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:57:01Z"
    - latency: 974.605µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:56:01Z"
    - latency: 1.397025ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:55:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T07:14:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 0e4fa577-f0ac-436c-b15a-0856e03ee95a
    resourceVersion: "67370"
    uid: 8d193e4a-5aed-4d00-a68e-81b0e8535c07
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdxgf
    targetEndpoint: a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T07:21:01Z"
      message: 'load-balancer-api-external: tcp connection to a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.969328ms
      message: 'load-balancer-api-external: tcp connection to a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:03:01Z"
    - latency: 10.16305ms
      message: 'load-balancer-api-external: resolved host name a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T08:03:01Z"
    - latency: 5.075035ms
      message: 'load-balancer-api-external: tcp connection to a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:02:01Z"
    - latency: 14.961008ms
      message: 'load-balancer-api-external: resolved host name a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T08:02:01Z"
    - latency: 4.684948ms
      message: 'load-balancer-api-external: tcp connection to a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:01:01Z"
    - latency: 16.363635ms
      message: 'load-balancer-api-external: resolved host name a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T08:01:01Z"
    - latency: 4.966342ms
      message: 'load-balancer-api-external: tcp connection to a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:00:01Z"
    - latency: 6.838472ms
      message: 'load-balancer-api-external: resolved host name a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T08:00:01Z"
    - latency: 4.013902ms
      message: 'load-balancer-api-external: tcp connection to a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:59:01Z"
    - latency: 9.566535ms
      message: 'load-balancer-api-external: resolved host name a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T07:59:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T07:14:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 0e4fa577-f0ac-436c-b15a-0856e03ee95a
    resourceVersion: "67371"
    uid: 00145a02-cf67-465b-a1f0-e4c9c705ae18
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdxgf
    targetEndpoint: a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T07:21:01Z"
      message: 'load-balancer-api-internal: tcp connection to a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.990706ms
      message: 'load-balancer-api-internal: tcp connection to a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:03:01Z"
    - latency: 10.226108ms
      message: 'load-balancer-api-internal: resolved host name a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T08:03:01Z"
    - latency: 5.396323ms
      message: 'load-balancer-api-internal: tcp connection to a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:02:01Z"
    - latency: 15.033609ms
      message: 'load-balancer-api-internal: resolved host name a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T08:02:01Z"
    - latency: 4.494737ms
      message: 'load-balancer-api-internal: tcp connection to a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:01:01Z"
    - latency: 16.431441ms
      message: 'load-balancer-api-internal: resolved host name a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T08:01:01Z"
    - latency: 4.977767ms
      message: 'load-balancer-api-internal: tcp connection to a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:00:01Z"
    - latency: 6.802746ms
      message: 'load-balancer-api-internal: resolved host name a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T08:00:01Z"
    - latency: 4.080032ms
      message: 'load-balancer-api-internal: tcp connection to a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:59:01Z"
    - latency: 9.601001ms
      message: 'load-balancer-api-internal: resolved host name a9da45d7df20743068d75df834e7c1b4-1eb1271135f68c1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T07:59:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T07:14:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-network-check-target-ip-10-0-135-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 0e4fa577-f0ac-436c-b15a-0856e03ee95a
    resourceVersion: "68443"
    uid: 96c3e4a5-7385-41da-a0d1-0d273da67c92
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdxgf
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T07:22:01Z"
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.227677ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:04:01Z"
    - latency: 2.134113ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:03:01Z"
    - latency: 2.263221ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:02:01Z"
    - latency: 2.345518ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:01:01Z"
    - latency: 2.092388ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:00:01Z"
    - latency: 2.27381ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:59:01Z"
    - latency: 2.449139ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:58:01Z"
    - latency: 1.868956ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:57:01Z"
    - latency: 1.986574ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:56:01Z"
    - latency: 1.924947ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:55:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T07:14:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-network-check-target-ip-10-0-138-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 0e4fa577-f0ac-436c-b15a-0856e03ee95a
    resourceVersion: "68441"
    uid: 57bbee38-7937-4fbe-aa81-0ec6c283a3c0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdxgf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T07:22:01Z"
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.075684ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:04:01Z"
    - latency: 1.352192ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:03:01Z"
    - latency: 1.030526ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:02:01Z"
    - latency: 1.426651ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:01:01Z"
    - latency: 1.61749ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:00:01Z"
    - latency: 991.331µs
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:59:01Z"
    - latency: 1.049175ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:58:01Z"
    - latency: 995.052µs
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:57:01Z"
    - latency: 932.951µs
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:56:01Z"
    - latency: 1.222091ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:55:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T07:14:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-network-check-target-ip-10-0-138-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 0e4fa577-f0ac-436c-b15a-0856e03ee95a
    resourceVersion: "68442"
    uid: e014da30-7749-4dbe-bc2b-51f26b306838
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdxgf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T07:22:01Z"
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.446164ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:04:01Z"
    - latency: 2.2573ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:03:01Z"
    - latency: 2.110876ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:02:01Z"
    - latency: 2.039177ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:01:01Z"
    - latency: 2.328997ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:00:01Z"
    - latency: 2.203482ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:59:01Z"
    - latency: 2.196206ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:58:01Z"
    - latency: 2.29022ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:57:01Z"
    - latency: 2.071321ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:56:01Z"
    - latency: 2.388908ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:55:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T07:14:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 0e4fa577-f0ac-436c-b15a-0856e03ee95a
    resourceVersion: "67369"
    uid: 1ab07e3e-eb1f-4ff8-b7b0-da380fbf7cb1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdxgf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T07:21:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 805.822µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:03:01Z"
    - latency: 1.822164ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T08:03:01Z"
    - latency: 889.778µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:02:01Z"
    - latency: 2.31816ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T08:02:01Z"
    - latency: 1.098022ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:01:01Z"
    - latency: 2.124845ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T08:01:01Z"
    - latency: 931.877µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T08:00:01Z"
    - latency: 1.595183ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T08:00:01Z"
    - latency: 779.18µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T07:59:01Z"
    - latency: 1.941515ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T07:59:01Z"
kind: List
metadata:
  resourceVersion: ""