apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:33:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-246-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-246.ec2.internal
      uid: a385b157-d294-4585-80e0-7d3bdf67df2f
    resourceVersion: "55351"
    uid: d1c2aee6-2caa-40a2-aa0b-b4c2525d846b
  spec:
    sourcePod: network-check-source-869dcfcdcd-hr5tr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:40:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.777µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:08:31Z"
    - latency: 879.518µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:07:31Z"
    - latency: 998.79µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:06:31Z"
    - latency: 1.072484ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:05:31Z"
    - latency: 767.489µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:04:31Z"
    - latency: 1.115609ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:03:31Z"
    - latency: 1.397444ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:02:31Z"
    - latency: 953.007µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:01:31Z"
    - latency: 1.149911ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:00:31Z"
    - latency: 945.58µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:59:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:33:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-246-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-246.ec2.internal
      uid: a385b157-d294-4585-80e0-7d3bdf67df2f
    resourceVersion: "56369"
    uid: 10175ddd-2d87-40ea-bba0-84861f6bc845
  spec:
    sourcePod: network-check-source-869dcfcdcd-hr5tr
    targetEndpoint: aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:39:31Z"
      message: 'load-balancer-api-external: tcp connection to aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.894475ms
      message: 'load-balancer-api-external: tcp connection to aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:09:31Z"
    - latency: 7.538295ms
      message: 'load-balancer-api-external: resolved host name aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:09:31Z"
    - latency: 4.928132ms
      message: 'load-balancer-api-external: tcp connection to aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:08:31Z"
    - latency: 7.407352ms
      message: 'load-balancer-api-external: resolved host name aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:08:31Z"
    - latency: 4.71215ms
      message: 'load-balancer-api-external: tcp connection to aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:07:31Z"
    - latency: 6.424473ms
      message: 'load-balancer-api-external: resolved host name aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:07:31Z"
    - latency: 4.723308ms
      message: 'load-balancer-api-external: tcp connection to aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:06:31Z"
    - latency: 6.864066ms
      message: 'load-balancer-api-external: resolved host name aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:06:31Z"
    - latency: 5.917558ms
      message: 'load-balancer-api-external: tcp connection to aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:05:31Z"
    - latency: 7.399897ms
      message: 'load-balancer-api-external: resolved host name aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:05:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:33:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-246-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-246.ec2.internal
      uid: a385b157-d294-4585-80e0-7d3bdf67df2f
    resourceVersion: "56370"
    uid: d3ecb2f6-b0c8-4f18-9755-615ba2e0f258
  spec:
    sourcePod: network-check-source-869dcfcdcd-hr5tr
    targetEndpoint: aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:39:31Z"
      message: 'load-balancer-api-internal: tcp connection to aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.230094ms
      message: 'load-balancer-api-internal: tcp connection to aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:09:31Z"
    - latency: 7.633899ms
      message: 'load-balancer-api-internal: resolved host name aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:09:31Z"
    - latency: 4.937193ms
      message: 'load-balancer-api-internal: tcp connection to aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:08:31Z"
    - latency: 7.377877ms
      message: 'load-balancer-api-internal: resolved host name aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:08:31Z"
    - latency: 4.716402ms
      message: 'load-balancer-api-internal: tcp connection to aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:07:31Z"
    - latency: 6.546644ms
      message: 'load-balancer-api-internal: resolved host name aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:07:31Z"
    - latency: 4.692197ms
      message: 'load-balancer-api-internal: tcp connection to aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:06:31Z"
    - latency: 6.993265ms
      message: 'load-balancer-api-internal: resolved host name aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:06:31Z"
    - latency: 5.129374ms
      message: 'load-balancer-api-internal: tcp connection to aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:05:31Z"
    - latency: 7.344666ms
      message: 'load-balancer-api-internal: resolved host name aabb3f3da8428468ab640d354cf1605d-372ff61b7a379dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:05:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:33:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-246-to-network-check-target-ip-10-0-142-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-246.ec2.internal
      uid: a385b157-d294-4585-80e0-7d3bdf67df2f
    resourceVersion: "55350"
    uid: 095765bb-f4cb-4647-b94c-39aecfb2d43f
  spec:
    sourcePod: network-check-source-869dcfcdcd-hr5tr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:40:31Z"
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.344649ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:08:31Z"
    - latency: 2.352572ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:07:31Z"
    - latency: 2.255972ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:06:31Z"
    - latency: 2.226476ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:05:31Z"
    - latency: 1.808314ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:04:31Z"
    - latency: 2.286491ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:03:31Z"
    - latency: 2.522374ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:02:31Z"
    - latency: 2.63827ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:01:31Z"
    - latency: 2.266947ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:00:31Z"
    - latency: 2.367377ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:59:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:33:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-246-to-network-check-target-ip-10-0-142-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-246.ec2.internal
      uid: a385b157-d294-4585-80e0-7d3bdf67df2f
    resourceVersion: "55348"
    uid: bbb0511e-0b45-40d2-b15a-df9124dd59a2
  spec:
    sourcePod: network-check-source-869dcfcdcd-hr5tr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:40:31Z"
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.673728ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:08:31Z"
    - latency: 1.919755ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:07:31Z"
    - latency: 1.943038ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:06:31Z"
    - latency: 1.943606ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:05:31Z"
    - latency: 1.7519ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:04:31Z"
    - latency: 1.828147ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:03:31Z"
    - latency: 1.710239ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:02:31Z"
    - latency: 1.699823ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:01:31Z"
    - latency: 1.873568ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:00:31Z"
    - latency: 1.833982ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:59:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:33:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-246-to-network-check-target-ip-10-0-142-246
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-246.ec2.internal
      uid: a385b157-d294-4585-80e0-7d3bdf67df2f
    resourceVersion: "55349"
    uid: 8e0475f8-e98d-41f5-88a0-2e2dd0defe88
  spec:
    sourcePod: network-check-source-869dcfcdcd-hr5tr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:40:31Z"
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.619092ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:08:31Z"
    - latency: 1.139374ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:07:31Z"
    - latency: 899.07µs
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:06:31Z"
    - latency: 1.151906ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:05:31Z"
    - latency: 728.596µs
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:04:31Z"
    - latency: 1.355148ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:03:31Z"
    - latency: 1.190882ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:02:31Z"
    - latency: 1.176439ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:01:31Z"
    - latency: 761.016µs
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:00:31Z"
    - latency: 695.813µs
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:59:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:33:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-246-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-246.ec2.internal
      uid: a385b157-d294-4585-80e0-7d3bdf67df2f
    resourceVersion: "56368"
    uid: 151472fd-28f1-4f34-b818-a56ee2362d8c
  spec:
    sourcePod: network-check-source-869dcfcdcd-hr5tr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:39:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.248562ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:09:31Z"
    - latency: 1.702652ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:09:31Z"
    - latency: 1.244826ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:08:31Z"
    - latency: 1.810089ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:08:31Z"
    - latency: 1.17311ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:07:31Z"
    - latency: 1.893045ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:07:31Z"
    - latency: 1.080569ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:06:31Z"
    - latency: 1.68722ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:06:31Z"
    - latency: 1.141217ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:05:31Z"
    - latency: 1.907651ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:05:31Z"
kind: List
metadata:
  resourceVersion: ""