apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-86-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-86.ec2.internal
      uid: b69a8355-9802-4534-90c1-971037ba2973
    resourceVersion: "60707"
    uid: 1ae2789f-b7f7-4977-8dd7-0e08e90bfe38
  spec:
    sourcePod: network-check-source-6f78d59f99-nhgxp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:24: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.105256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:45:06Z"
    - latency: 1.398384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:44:06Z"
    - latency: 1.441987ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:43:06Z"
    - latency: 1.518909ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:42:06Z"
    - latency: 1.469367ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:41:06Z"
    - latency: 1.625431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:40:06Z"
    - latency: 1.077567ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:39:06Z"
    - latency: 1.252604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:38:06Z"
    - latency: 1.133903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:37:06Z"
    - latency: 1.190656ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:36:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-86-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-86.ec2.internal
      uid: b69a8355-9802-4534-90c1-971037ba2973
    resourceVersion: "63100"
    uid: a8c40557-ee91-4971-8e0e-693192013d81
  spec:
    sourcePod: network-check-source-6f78d59f99-nhgxp
    targetEndpoint: a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:23:06Z"
      message: 'load-balancer-api-external: tcp connection to a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.223442ms
      message: 'load-balancer-api-external: tcp connection to a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:47:06Z"
    - latency: 6.884429ms
      message: 'load-balancer-api-external: resolved host name a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:47:06Z"
    - latency: 18.814602ms
      message: 'load-balancer-api-external: tcp connection to a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:46:06Z"
    - latency: 11.107758ms
      message: 'load-balancer-api-external: resolved host name a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:46:06Z"
    - latency: 19.45912ms
      message: 'load-balancer-api-external: tcp connection to a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:45:06Z"
    - latency: 6.964053ms
      message: 'load-balancer-api-external: resolved host name a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:45:06Z"
    - latency: 19.004666ms
      message: 'load-balancer-api-external: tcp connection to a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:44:06Z"
    - latency: 7.435993ms
      message: 'load-balancer-api-external: resolved host name a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:44:06Z"
    - latency: 18.934303ms
      message: 'load-balancer-api-external: tcp connection to a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:43:06Z"
    - latency: 7.191659ms
      message: 'load-balancer-api-external: resolved host name a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:43:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-86-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-86.ec2.internal
      uid: b69a8355-9802-4534-90c1-971037ba2973
    resourceVersion: "63099"
    uid: c345107f-eb9a-462b-a99e-63c4170c2898
  spec:
    sourcePod: network-check-source-6f78d59f99-nhgxp
    targetEndpoint: a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:23:06Z"
      message: 'load-balancer-api-internal: tcp connection to a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.046746ms
      message: 'load-balancer-api-internal: tcp connection to a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:47:06Z"
    - latency: 6.792888ms
      message: 'load-balancer-api-internal: resolved host name a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:47:06Z"
    - latency: 18.033191ms
      message: 'load-balancer-api-internal: tcp connection to a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:46:06Z"
    - latency: 11.160888ms
      message: 'load-balancer-api-internal: resolved host name a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:46:06Z"
    - latency: 19.384422ms
      message: 'load-balancer-api-internal: tcp connection to a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:45:06Z"
    - latency: 6.868866ms
      message: 'load-balancer-api-internal: resolved host name a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:45:06Z"
    - latency: 16.517101ms
      message: 'load-balancer-api-internal: tcp connection to a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:44:06Z"
    - latency: 7.471778ms
      message: 'load-balancer-api-internal: resolved host name a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:44:06Z"
    - latency: 18.993905ms
      message: 'load-balancer-api-internal: tcp connection to a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:43:06Z"
    - latency: 7.152058ms
      message: 'load-balancer-api-internal: resolved host name a652e1dff22fb4b1682347fb8adf3ec0-fbff9162e07032f1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:43:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-86-to-network-check-target-ip-10-0-130-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-86.ec2.internal
      uid: b69a8355-9802-4534-90c1-971037ba2973
    resourceVersion: "60703"
    uid: 22f69a53-ca37-4cb9-bcc4-2c31433a2d47
  spec:
    sourcePod: network-check-source-6f78d59f99-nhgxp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:24:06Z"
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.025664ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:45:06Z"
    - latency: 1.064824ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:44:06Z"
    - latency: 1.633785ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:43:06Z"
    - latency: 1.758329ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:42:06Z"
    - latency: 3.853572ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:41:06Z"
    - latency: 1.067366ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:40:06Z"
    - latency: 1.050317ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:39:06Z"
    - latency: 1.362431ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:38:06Z"
    - latency: 1.020929ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:37:06Z"
    - latency: 1.331134ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:36:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-86-to-network-check-target-ip-10-0-138-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-86.ec2.internal
      uid: b69a8355-9802-4534-90c1-971037ba2973
    resourceVersion: "60705"
    uid: 853af228-ed84-4b89-a7ed-0f21c27743d9
  spec:
    sourcePod: network-check-source-6f78d59f99-nhgxp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:24:06Z"
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.418484ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:45:06Z"
    - latency: 2.779217ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:44:06Z"
    - latency: 2.510903ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:43:06Z"
    - latency: 2.484676ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:42:06Z"
    - latency: 2.254056ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:41:06Z"
    - latency: 2.415701ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:40:06Z"
    - latency: 2.672734ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:39:06Z"
    - latency: 2.326776ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:38:06Z"
    - latency: 2.118344ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:37:06Z"
    - latency: 2.335536ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:36:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-86-to-network-check-target-ip-10-0-139-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-86.ec2.internal
      uid: b69a8355-9802-4534-90c1-971037ba2973
    resourceVersion: "60704"
    uid: e86145f6-2b8f-49e2-bd2d-77aa65b843c9
  spec:
    sourcePod: network-check-source-6f78d59f99-nhgxp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:24:06Z"
      message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.55431ms
      message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:45:06Z"
    - latency: 2.424829ms
      message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:44:06Z"
    - latency: 2.499509ms
      message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:43:06Z"
    - latency: 2.778239ms
      message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:42:06Z"
    - latency: 2.80945ms
      message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:41:06Z"
    - latency: 2.571318ms
      message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:40:06Z"
    - latency: 2.816658ms
      message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:39:06Z"
    - latency: 2.554132ms
      message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:38:06Z"
    - latency: 2.833684ms
      message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:37:06Z"
    - latency: 2.582389ms
      message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:36:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-86-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-86.ec2.internal
      uid: b69a8355-9802-4534-90c1-971037ba2973
    resourceVersion: "63098"
    uid: 9b901c84-b599-41ae-9c73-456349134620
  spec:
    sourcePod: network-check-source-6f78d59f99-nhgxp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:23:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.100542ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:47:06Z"
    - latency: 1.999748ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:47:06Z"
    - latency: 1.222277ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:46:06Z"
    - latency: 5.358142ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:46:06Z"
    - latency: 1.228842ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:45:06Z"
    - latency: 1.866035ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:45:06Z"
    - latency: 988.925µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:44:06Z"
    - latency: 2.029093ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:44:06Z"
    - latency: 990.261µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:43:06Z"
    - latency: 1.776943ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:43:06Z"
kind: List
metadata:
  resourceVersion: ""