apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T10:52:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 6fa05fa9-6b09-458d-a112-a7e5cdf93e4a
    resourceVersion: "71810"
    uid: 17b56ccd-11fb-44de-9efb-d96efc449647
  spec:
    sourcePod: network-check-source-7d88cb55d8-5twc2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T10:59:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.419647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:41:33Z"
    - latency: 1.362849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:40:33Z"
    - latency: 1.137663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:39:33Z"
    - latency: 1.085905ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:38:33Z"
    - latency: 1.064916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:37:33Z"
    - latency: 1.23808ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:36:33Z"
    - latency: 1.346964ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:35:33Z"
    - latency: 994.19µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:34:33Z"
    - latency: 1.253335ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:33:33Z"
    - latency: 1.112756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:32:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T10:52:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 6fa05fa9-6b09-458d-a112-a7e5cdf93e4a
    resourceVersion: "80578"
    uid: 6ca4dc70-232f-4a05-be8b-29dbd7536e7e
  spec:
    sourcePod: network-check-source-7d88cb55d8-5twc2
    targetEndpoint: a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T10:58:33Z"
      message: 'load-balancer-api-external: tcp connection to a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.155316ms
      message: 'load-balancer-api-external: tcp connection to a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:46:33Z"
    - latency: 7.995022ms
      message: 'load-balancer-api-external: resolved host name a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:46:33Z"
    - latency: 4.106565ms
      message: 'load-balancer-api-external: tcp connection to a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:45:33Z"
    - latency: 7.116459ms
      message: 'load-balancer-api-external: resolved host name a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:45:33Z"
    - latency: 4.348186ms
      message: 'load-balancer-api-external: tcp connection to a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:44:33Z"
    - latency: 7.643699ms
      message: 'load-balancer-api-external: resolved host name a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:44:33Z"
    - latency: 4.636379ms
      message: 'load-balancer-api-external: tcp connection to a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:43:33Z"
    - latency: 6.935571ms
      message: 'load-balancer-api-external: resolved host name a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:43:33Z"
    - latency: 4.52385ms
      message: 'load-balancer-api-external: tcp connection to a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:42:33Z"
    - latency: 7.169309ms
      message: 'load-balancer-api-external: resolved host name a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:42:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T10:52:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 6fa05fa9-6b09-458d-a112-a7e5cdf93e4a
    resourceVersion: "80579"
    uid: ce3fa8e1-0dc5-47e3-9247-1ef0285ae391
  spec:
    sourcePod: network-check-source-7d88cb55d8-5twc2
    targetEndpoint: a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T10:58:33Z"
      message: 'load-balancer-api-internal: tcp connection to a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.876324ms
      message: 'load-balancer-api-internal: tcp connection to a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:46:33Z"
    - latency: 8.044918ms
      message: 'load-balancer-api-internal: resolved host name a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:46:33Z"
    - latency: 3.700864ms
      message: 'load-balancer-api-internal: tcp connection to a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:45:33Z"
    - latency: 7.165477ms
      message: 'load-balancer-api-internal: resolved host name a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:45:33Z"
    - latency: 4.118709ms
      message: 'load-balancer-api-internal: tcp connection to a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:44:33Z"
    - latency: 7.544285ms
      message: 'load-balancer-api-internal: resolved host name a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:44:33Z"
    - latency: 4.643048ms
      message: 'load-balancer-api-internal: tcp connection to a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:43:33Z"
    - latency: 6.836534ms
      message: 'load-balancer-api-internal: resolved host name a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:43:33Z"
    - latency: 4.553137ms
      message: 'load-balancer-api-internal: tcp connection to a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:42:33Z"
    - latency: 7.08455ms
      message: 'load-balancer-api-internal: resolved host name a45102776c5fd4ff2a90fd2faacb67ff-38ce229ce915a694.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:42:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T10:52:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-network-check-target-ip-10-0-128-243
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 6fa05fa9-6b09-458d-a112-a7e5cdf93e4a
    resourceVersion: "71808"
    uid: 63c82166-9935-402e-9335-2c1df1d512e7
  spec:
    sourcePod: network-check-source-7d88cb55d8-5twc2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T10:59:33Z"
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.205188ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:41:33Z"
    - latency: 2.332333ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:40:33Z"
    - latency: 2.12064ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:39:33Z"
    - latency: 2.212776ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:38:33Z"
    - latency: 2.123947ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:37:33Z"
    - latency: 2.153488ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:36:33Z"
    - latency: 2.321737ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:35:33Z"
    - latency: 2.200907ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:34:33Z"
    - latency: 2.208064ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:33:33Z"
    - latency: 2.076041ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:32:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T10:52:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-network-check-target-ip-10-0-134-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 6fa05fa9-6b09-458d-a112-a7e5cdf93e4a
    resourceVersion: "71809"
    uid: 353b8aa3-961a-4afd-ad28-3084c8a944ed
  spec:
    sourcePod: network-check-source-7d88cb55d8-5twc2
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T10:59:33Z"
      message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.675979ms
      message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:41:33Z"
    - latency: 2.484735ms
      message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:40:33Z"
    - latency: 2.334842ms
      message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:39:33Z"
    - latency: 2.243212ms
      message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:38:33Z"
    - latency: 2.467143ms
      message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:37:33Z"
    - latency: 2.449019ms
      message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:36:33Z"
    - latency: 2.470618ms
      message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:35:33Z"
    - latency: 2.466846ms
      message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:34:33Z"
    - latency: 2.40309ms
      message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:33:33Z"
    - latency: 2.122349ms
      message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:32:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T10:52:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-network-check-target-ip-10-0-138-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 6fa05fa9-6b09-458d-a112-a7e5cdf93e4a
    resourceVersion: "71807"
    uid: 4c5f9621-ce14-4b10-b6c4-42144bd093e2
  spec:
    sourcePod: network-check-source-7d88cb55d8-5twc2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T10:59:33Z"
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.149806ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:41:33Z"
    - latency: 982.592µs
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:40:33Z"
    - latency: 1.24358ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:39:33Z"
    - latency: 1.139297ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:38:33Z"
    - latency: 1.005275ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:37:33Z"
    - latency: 1.028568ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:36:33Z"
    - latency: 1.001882ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:35:33Z"
    - latency: 1.075577ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:34:33Z"
    - latency: 1.260507ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:33:33Z"
    - latency: 1.269962ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:32:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T10:52:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: 6fa05fa9-6b09-458d-a112-a7e5cdf93e4a
    resourceVersion: "80577"
    uid: bde57833-5411-4d59-9608-ee672caaebb2
  spec:
    sourcePod: network-check-source-7d88cb55d8-5twc2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T10:58:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.031865ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:46:33Z"
    - latency: 2.21926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:46:33Z"
    - latency: 1.331988ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:45:33Z"
    - latency: 1.938851ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:45:33Z"
    - latency: 931.547µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:44:33Z"
    - latency: 2.09146ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:44:33Z"
    - latency: 919.355µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:43:33Z"
    - latency: 1.770433ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:43:33Z"
    - latency: 946.509µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T11:42:33Z"
    - latency: 1.774747ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T11:42:33Z"
kind: List
metadata:
  resourceVersion: ""