apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: a45d6f89-a4d3-4969-b41c-c3a5be5cf65b
    resourceVersion: "67104"
    uid: fa86ccfb-e112-40ef-9ed1-53b9ca0a69dd
  spec:
    sourcePod: network-check-source-7d88cb55d8-zszlp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:53:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 962.675µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:28:00Z"
    - latency: 1.252667ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:27:00Z"
    - latency: 828.728µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:00Z"
    - latency: 1.000375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:00Z"
    - latency: 1.18119ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:00Z"
    - latency: 955.854µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:00Z"
    - latency: 1.202893ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:00Z"
    - latency: 1.220578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:21:00Z"
    - latency: 1.065781ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:20:00Z"
    - latency: 728.09µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:19:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: a45d6f89-a4d3-4969-b41c-c3a5be5cf65b
    resourceVersion: "67105"
    uid: b9c0206d-7e34-453b-887c-760729f89813
  spec:
    sourcePod: network-check-source-7d88cb55d8-zszlp
    targetEndpoint: a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:52:00Z"
      message: 'load-balancer-api-external: tcp connection to a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.240106ms
      message: 'load-balancer-api-external: tcp connection to a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:28:00Z"
    - latency: 12.055254ms
      message: 'load-balancer-api-external: resolved host name a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:28:00Z"
    - latency: 3.878187ms
      message: 'load-balancer-api-external: tcp connection to a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:27:00Z"
    - latency: 7.075001ms
      message: 'load-balancer-api-external: resolved host name a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:27:00Z"
    - latency: 3.978605ms
      message: 'load-balancer-api-external: tcp connection to a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:00Z"
    - latency: 7.738455ms
      message: 'load-balancer-api-external: resolved host name a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:26:00Z"
    - latency: 4.200599ms
      message: 'load-balancer-api-external: tcp connection to a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:00Z"
    - latency: 8.830095ms
      message: 'load-balancer-api-external: resolved host name a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:25:00Z"
    - latency: 3.926914ms
      message: 'load-balancer-api-external: tcp connection to a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:00Z"
    - latency: 8.763217ms
      message: 'load-balancer-api-external: resolved host name a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:24:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: a45d6f89-a4d3-4969-b41c-c3a5be5cf65b
    resourceVersion: "67106"
    uid: b3a4f27e-71b4-4f23-a72d-ef4a7342c6b1
  spec:
    sourcePod: network-check-source-7d88cb55d8-zszlp
    targetEndpoint: a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:52:00Z"
      message: 'load-balancer-api-internal: tcp connection to a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.036776ms
      message: 'load-balancer-api-internal: tcp connection to a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:28:00Z"
    - latency: 12.086169ms
      message: 'load-balancer-api-internal: resolved host name a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:28:00Z"
    - latency: 3.862203ms
      message: 'load-balancer-api-internal: tcp connection to a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:27:00Z"
    - latency: 7.154865ms
      message: 'load-balancer-api-internal: resolved host name a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:27:00Z"
    - latency: 3.963218ms
      message: 'load-balancer-api-internal: tcp connection to a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:00Z"
    - latency: 7.759761ms
      message: 'load-balancer-api-internal: resolved host name a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:26:00Z"
    - latency: 4.852975ms
      message: 'load-balancer-api-internal: tcp connection to a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:00Z"
    - latency: 8.978313ms
      message: 'load-balancer-api-internal: resolved host name a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:25:00Z"
    - latency: 3.258618ms
      message: 'load-balancer-api-internal: tcp connection to a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:00Z"
    - latency: 8.74518ms
      message: 'load-balancer-api-internal: resolved host name a642ede31d6874973b4abcd5ac970406-fa080f20934e7440.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:24:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-network-check-target-ip-10-0-132-71
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: a45d6f89-a4d3-4969-b41c-c3a5be5cf65b
    resourceVersion: "67103"
    uid: 913abab5-cc94-47e2-b4b1-4d7523a6a8c1
  spec:
    sourcePod: network-check-source-7d88cb55d8-zszlp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:53:00Z"
      message: 'network-check-target-ip-10-0-132-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.996108ms
      message: 'network-check-target-ip-10-0-132-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:28:00Z"
    - latency: 2.351839ms
      message: 'network-check-target-ip-10-0-132-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:27:00Z"
    - latency: 2.184181ms
      message: 'network-check-target-ip-10-0-132-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:00Z"
    - latency: 2.274471ms
      message: 'network-check-target-ip-10-0-132-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:00Z"
    - latency: 2.268951ms
      message: 'network-check-target-ip-10-0-132-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:00Z"
    - latency: 2.675297ms
      message: 'network-check-target-ip-10-0-132-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:00Z"
    - latency: 2.355034ms
      message: 'network-check-target-ip-10-0-132-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:00Z"
    - latency: 2.579185ms
      message: 'network-check-target-ip-10-0-132-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:21:00Z"
    - latency: 2.161542ms
      message: 'network-check-target-ip-10-0-132-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:20:00Z"
    - latency: 2.059066ms
      message: 'network-check-target-ip-10-0-132-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:19:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-network-check-target-ip-10-0-137-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: a45d6f89-a4d3-4969-b41c-c3a5be5cf65b
    resourceVersion: "67102"
    uid: a20c74d7-5f77-4ea5-80fa-86ac6d59d1dd
  spec:
    sourcePod: network-check-source-7d88cb55d8-zszlp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:53:00Z"
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.960086ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:28:00Z"
    - latency: 2.252691ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:27:00Z"
    - latency: 2.227316ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:00Z"
    - latency: 2.053711ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:00Z"
    - latency: 2.134727ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:00Z"
    - latency: 2.00074ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:00Z"
    - latency: 1.937592ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:00Z"
    - latency: 2.279228ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:21:00Z"
    - latency: 1.796674ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:20:00Z"
    - latency: 1.991064ms
      message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:19:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-network-check-target-ip-10-0-141-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: a45d6f89-a4d3-4969-b41c-c3a5be5cf65b
    resourceVersion: "67100"
    uid: 715b0afb-6c54-4d11-a0e5-a55cff3656a9
  spec:
    sourcePod: network-check-source-7d88cb55d8-zszlp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:53:00Z"
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.075µs
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:28:00Z"
    - latency: 833.831µs
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:27:00Z"
    - latency: 1.012844ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:00Z"
    - latency: 993.986µs
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:00Z"
    - latency: 845.926µs
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:00Z"
    - latency: 1.515193ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:00Z"
    - latency: 1.543746ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:00Z"
    - latency: 1.730445ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:21:00Z"
    - latency: 1.143042ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:20:00Z"
    - latency: 895.284µs
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:19:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:45:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: a45d6f89-a4d3-4969-b41c-c3a5be5cf65b
    resourceVersion: "67101"
    uid: 68879e9b-9045-4792-8d65-a4b9701ec996
  spec:
    sourcePod: network-check-source-7d88cb55d8-zszlp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:52:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.117µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:28:00Z"
    - latency: 1.980738ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:28:00Z"
    - latency: 916.289µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:27:00Z"
    - latency: 1.615704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:27:00Z"
    - latency: 1.074954ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:00Z"
    - latency: 1.817375ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:26:00Z"
    - latency: 1.274625ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:00Z"
    - latency: 1.697377ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:25:00Z"
    - latency: 834.807µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:00Z"
    - latency: 1.664054ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:24:00Z"
kind: List
metadata:
  resourceVersion: ""