apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:21:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-38-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-38.ec2.internal
      uid: fd2d0082-72b0-45b4-9d1d-32970df3e2a3
    resourceVersion: "68038"
    uid: abfb9b83-68ee-4ad9-bc73-0f746daa2b82
  spec:
    sourcePod: network-check-source-6f8b768455-gwsht
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:28:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:56:06Z"
    - latency: 1.227645ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:55:06Z"
    - latency: 944.705µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:54:06Z"
    - latency: 1.096456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:53:06Z"
    - latency: 1.340986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:52:06Z"
    - latency: 959.086µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:51:06Z"
    - latency: 939.182µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:50:06Z"
    - latency: 1.14628ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:49:06Z"
    - latency: 1.064343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:48:06Z"
    - latency: 1.21029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:47:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:21:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-38-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-38.ec2.internal
      uid: fd2d0082-72b0-45b4-9d1d-32970df3e2a3
    resourceVersion: "68920"
    uid: e1827c77-995b-451a-9a27-3167bec7167e
  spec:
    sourcePod: network-check-source-6f8b768455-gwsht
    targetEndpoint: a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:27:06Z"
      message: 'load-balancer-api-external: tcp connection to a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.970674ms
      message: 'load-balancer-api-external: tcp connection to a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:57:06Z"
    - latency: 8.209277ms
      message: 'load-balancer-api-external: resolved host name a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:57:06Z"
    - latency: 5.286696ms
      message: 'load-balancer-api-external: tcp connection to a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:56:06Z"
    - latency: 8.964168ms
      message: 'load-balancer-api-external: resolved host name a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:56:06Z"
    - latency: 3.686126ms
      message: 'load-balancer-api-external: tcp connection to a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:55:06Z"
    - latency: 7.965776ms
      message: 'load-balancer-api-external: resolved host name a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:55:06Z"
    - latency: 4.644155ms
      message: 'load-balancer-api-external: tcp connection to a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:54:06Z"
    - latency: 8.943123ms
      message: 'load-balancer-api-external: resolved host name a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:54:06Z"
    - latency: 4.342392ms
      message: 'load-balancer-api-external: tcp connection to a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:53:06Z"
    - latency: 8.131511ms
      message: 'load-balancer-api-external: resolved host name a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:53:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:21:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-38-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-38.ec2.internal
      uid: fd2d0082-72b0-45b4-9d1d-32970df3e2a3
    resourceVersion: "68919"
    uid: a0be0e55-19d7-43bf-a20a-a059f3bb3af8
  spec:
    sourcePod: network-check-source-6f8b768455-gwsht
    targetEndpoint: a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:27:06Z"
      message: 'load-balancer-api-internal: tcp connection to a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.034633ms
      message: 'load-balancer-api-internal: tcp connection to a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:57:06Z"
    - latency: 8.092671ms
      message: 'load-balancer-api-internal: resolved host name a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:57:06Z"
    - latency: 4.280395ms
      message: 'load-balancer-api-internal: tcp connection to a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:56:06Z"
    - latency: 8.998585ms
      message: 'load-balancer-api-internal: resolved host name a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:56:06Z"
    - latency: 3.714835ms
      message: 'load-balancer-api-internal: tcp connection to a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:55:06Z"
    - latency: 8.01439ms
      message: 'load-balancer-api-internal: resolved host name a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:55:06Z"
    - latency: 4.717435ms
      message: 'load-balancer-api-internal: tcp connection to a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:54:06Z"
    - latency: 8.918131ms
      message: 'load-balancer-api-internal: resolved host name a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:54:06Z"
    - latency: 4.424547ms
      message: 'load-balancer-api-internal: tcp connection to a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:53:06Z"
    - latency: 8.243074ms
      message: 'load-balancer-api-internal: resolved host name a51ab29e99c83438791a22fb5c763fdd-6bf2787d4d5f7b04.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:53:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:21:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-38-to-network-check-target-ip-10-0-130-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-38.ec2.internal
      uid: fd2d0082-72b0-45b4-9d1d-32970df3e2a3
    resourceVersion: "68037"
    uid: 4a5e7c11-3cd0-4c30-aadf-10471cac1bc0
  spec:
    sourcePod: network-check-source-6f8b768455-gwsht
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:28:06Z"
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.411342ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:56:06Z"
    - latency: 2.081521ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:55:06Z"
    - latency: 2.014057ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:54:06Z"
    - latency: 2.274131ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:53:06Z"
    - latency: 1.999651ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:52:06Z"
    - latency: 2.433089ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:51:06Z"
    - latency: 2.283106ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:50:06Z"
    - latency: 2.3201ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:49:06Z"
    - latency: 2.271843ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:48:06Z"
    - latency: 2.061742ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:47:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:21:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-38-to-network-check-target-ip-10-0-133-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-38.ec2.internal
      uid: fd2d0082-72b0-45b4-9d1d-32970df3e2a3
    resourceVersion: "68036"
    uid: b84cbc35-848a-4069-887e-01c89f79d0c2
  spec:
    sourcePod: network-check-source-6f8b768455-gwsht
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:28:06Z"
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.309787ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:56:06Z"
    - latency: 2.239974ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:55:06Z"
    - latency: 1.99358ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:54:06Z"
    - latency: 2.10561ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:53:06Z"
    - latency: 2.064724ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:52:06Z"
    - latency: 2.673524ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:51:06Z"
    - latency: 2.170661ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:50:06Z"
    - latency: 2.029942ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:49:06Z"
    - latency: 2.141375ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:48:06Z"
    - latency: 2.549541ms
      message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:47:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:21:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-38-to-network-check-target-ip-10-0-136-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-38.ec2.internal
      uid: fd2d0082-72b0-45b4-9d1d-32970df3e2a3
    resourceVersion: "68035"
    uid: 2a92f4fd-8705-49ef-9cf2-ef9822d7b0f5
  spec:
    sourcePod: network-check-source-6f8b768455-gwsht
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:28:06Z"
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.497146ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:56:06Z"
    - latency: 1.001209ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:55:06Z"
    - latency: 959.103µs
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:54:06Z"
    - latency: 799.511µs
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:53:06Z"
    - latency: 1.1806ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:52:06Z"
    - latency: 1.03529ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:51:06Z"
    - latency: 1.364396ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:50:06Z"
    - latency: 1.345467ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:49:06Z"
    - latency: 922.538µs
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:48:06Z"
    - latency: 1.042305ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:47:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:21:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-38-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-38.ec2.internal
      uid: fd2d0082-72b0-45b4-9d1d-32970df3e2a3
    resourceVersion: "68918"
    uid: 759454bb-cf71-454a-9d4a-6fedbaee7e4e
  spec:
    sourcePod: network-check-source-6f8b768455-gwsht
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:27:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.132352ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:57:06Z"
    - latency: 1.684364ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:57:06Z"
    - latency: 819.306µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:56:06Z"
    - latency: 1.698407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:56:06Z"
    - latency: 739.476µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:55:06Z"
    - latency: 1.834899ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:55:06Z"
    - latency: 896.734µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:54:06Z"
    - latency: 1.657622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:54:06Z"
    - latency: 1.018589ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:53:06Z"
    - latency: 1.818582ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:53:06Z"
kind: List
metadata:
  resourceVersion: ""