apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-222.ec2.internal
      uid: 52e6620b-63a2-45df-818f-11839ee5ffde
    resourceVersion: "68668"
    uid: 4f00872c-ed83-4cce-a8d9-eedaa37cfa2f
  spec:
    sourcePod: network-check-source-7cbc45fddc-5bgrm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:16:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.457393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:38Z"
    - latency: 999.352µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:38Z"
    - latency: 1.226789ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:38Z"
    - latency: 1.204552ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:38Z"
    - latency: 1.105112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:38Z"
    - latency: 1.213164ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:38Z"
    - latency: 1.688634ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:38Z"
    - latency: 932.107µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:37:38Z"
    - latency: 1.078136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:36:38Z"
    - latency: 1.141016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-222.ec2.internal
      uid: 52e6620b-63a2-45df-818f-11839ee5ffde
    resourceVersion: "69691"
    uid: 79c701a3-97f3-4f8a-b76a-89a5aa1c848e
  spec:
    sourcePod: network-check-source-7cbc45fddc-5bgrm
    targetEndpoint: a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:15:38Z"
      message: 'load-balancer-api-external: tcp connection to a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.103744ms
      message: 'load-balancer-api-external: tcp connection to a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:45:38Z"
    - latency: 8.933654ms
      message: 'load-balancer-api-external: resolved host name a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:45:38Z"
    - latency: 5.258485ms
      message: 'load-balancer-api-external: tcp connection to a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:38Z"
    - latency: 7.64628ms
      message: 'load-balancer-api-external: resolved host name a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:44:38Z"
    - latency: 4.231302ms
      message: 'load-balancer-api-external: tcp connection to a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:38Z"
    - latency: 11.16762ms
      message: 'load-balancer-api-external: resolved host name a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:43:38Z"
    - latency: 6.05628ms
      message: 'load-balancer-api-external: tcp connection to a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:38Z"
    - latency: 9.822144ms
      message: 'load-balancer-api-external: resolved host name a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:42:38Z"
    - latency: 6.253266ms
      message: 'load-balancer-api-external: tcp connection to a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:38Z"
    - latency: 10.397453ms
      message: 'load-balancer-api-external: resolved host name a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:41:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-222.ec2.internal
      uid: 52e6620b-63a2-45df-818f-11839ee5ffde
    resourceVersion: "69690"
    uid: 2a6e6540-2cce-4a72-afb0-dbcc1f620c62
  spec:
    sourcePod: network-check-source-7cbc45fddc-5bgrm
    targetEndpoint: a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:15:38Z"
      message: 'load-balancer-api-internal: tcp connection to a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.8237ms
      message: 'load-balancer-api-internal: tcp connection to a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:45:38Z"
    - latency: 9.032164ms
      message: 'load-balancer-api-internal: resolved host name a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:45:38Z"
    - latency: 5.186873ms
      message: 'load-balancer-api-internal: tcp connection to a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:38Z"
    - latency: 7.691703ms
      message: 'load-balancer-api-internal: resolved host name a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:44:38Z"
    - latency: 4.119536ms
      message: 'load-balancer-api-internal: tcp connection to a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:38Z"
    - latency: 11.200145ms
      message: 'load-balancer-api-internal: resolved host name a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:43:38Z"
    - latency: 6.047632ms
      message: 'load-balancer-api-internal: tcp connection to a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:38Z"
    - latency: 9.848592ms
      message: 'load-balancer-api-internal: resolved host name a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:42:38Z"
    - latency: 6.232482ms
      message: 'load-balancer-api-internal: tcp connection to a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:38Z"
    - latency: 10.451967ms
      message: 'load-balancer-api-internal: resolved host name a11852cb51c4f4241bc7f6b3135d5bce-9abf1e137e4aab89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:41:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-222-to-network-check-target-ip-10-0-133-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-222.ec2.internal
      uid: 52e6620b-63a2-45df-818f-11839ee5ffde
    resourceVersion: "68665"
    uid: 159213c2-9d5d-4d8b-ab1b-96f206424c3a
  spec:
    sourcePod: network-check-source-7cbc45fddc-5bgrm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:16:38Z"
      message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.432802ms
      message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:38Z"
    - latency: 1.429585ms
      message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:38Z"
    - latency: 961.785µs
      message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:38Z"
    - latency: 1.000551ms
      message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:38Z"
    - latency: 1.406779ms
      message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:38Z"
    - latency: 1.551396ms
      message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:38Z"
    - latency: 943.039µs
      message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:38Z"
    - latency: 1.023433ms
      message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:37:38Z"
    - latency: 1.196338ms
      message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:36:38Z"
    - latency: 1.027744ms
      message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-222-to-network-check-target-ip-10-0-140-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-222.ec2.internal
      uid: 52e6620b-63a2-45df-818f-11839ee5ffde
    resourceVersion: "68666"
    uid: fb437e9d-af0d-49f4-9731-a600d9e856d2
  spec:
    sourcePod: network-check-source-7cbc45fddc-5bgrm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:16:38Z"
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.448713ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:38Z"
    - latency: 2.266962ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:38Z"
    - latency: 2.344475ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:38Z"
    - latency: 2.447217ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:38Z"
    - latency: 2.502462ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:38Z"
    - latency: 2.418345ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:38Z"
    - latency: 2.28148ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:38Z"
    - latency: 2.416226ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:37:38Z"
    - latency: 2.275443ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:36:38Z"
    - latency: 2.425571ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-222-to-network-check-target-ip-10-0-141-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-222.ec2.internal
      uid: 52e6620b-63a2-45df-818f-11839ee5ffde
    resourceVersion: "68667"
    uid: fc5b1338-c996-4e38-843f-b7e34d676529
  spec:
    sourcePod: network-check-source-7cbc45fddc-5bgrm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:16:38Z"
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.47044ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:38Z"
    - latency: 2.288509ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:38Z"
    - latency: 2.394108ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:38Z"
    - latency: 2.548303ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:38Z"
    - latency: 2.651405ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:38Z"
    - latency: 2.543029ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:38Z"
    - latency: 2.220446ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:38Z"
    - latency: 2.437547ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:37:38Z"
    - latency: 2.254103ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:36:38Z"
    - latency: 2.438948ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-222.ec2.internal
      uid: 52e6620b-63a2-45df-818f-11839ee5ffde
    resourceVersion: "69689"
    uid: 7e9a61ce-8e14-4e7f-aa79-558bd1b3877b
  spec:
    sourcePod: network-check-source-7cbc45fddc-5bgrm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:15:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.067573ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:45:38Z"
    - latency: 1.78251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:45:38Z"
    - latency: 906.052µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:38Z"
    - latency: 2.427593ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:44:38Z"
    - latency: 1.342834ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:38Z"
    - latency: 1.653496ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:43:38Z"
    - latency: 895.605µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:38Z"
    - latency: 1.917874ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:42:38Z"
    - latency: 816.389µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:38Z"
    - latency: 1.918115ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:41:38Z"
kind: List
metadata:
  resourceVersion: ""