apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:43:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-78-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-78.ec2.internal
      uid: a9398b04-a952-4011-ae13-13d24973b1a0
    resourceVersion: "61001"
    uid: d3a573d6-1f8d-49f3-a84b-6bb76311b175
  spec:
    sourcePod: network-check-source-7cbc45fddc-nd8ht
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:50:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.034474ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:11:31Z"
    - latency: 789.414µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:10:31Z"
    - latency: 1.889548ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:09:31Z"
    - latency: 1.031254ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:08:31Z"
    - latency: 860.384µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:07:31Z"
    - latency: 996.248µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:06:31Z"
    - latency: 875.333µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:05:31Z"
    - latency: 924.994µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:04:31Z"
    - latency: 1.124625ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:03:31Z"
    - latency: 1.029117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:02:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:43:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-78-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-78.ec2.internal
      uid: a9398b04-a952-4011-ae13-13d24973b1a0
    resourceVersion: "62507"
    uid: ed419433-0fc3-40f7-bd92-e1a2a1b275ef
  spec:
    sourcePod: network-check-source-7cbc45fddc-nd8ht
    targetEndpoint: aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:49:31Z"
      message: 'load-balancer-api-external: tcp connection to aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.241664ms
      message: 'load-balancer-api-external: tcp connection to aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:13:31Z"
    - latency: 8.969236ms
      message: 'load-balancer-api-external: resolved host name aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:13:31Z"
    - latency: 5.224489ms
      message: 'load-balancer-api-external: tcp connection to aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:12:31Z"
    - latency: 8.980487ms
      message: 'load-balancer-api-external: resolved host name aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:12:31Z"
    - latency: 5.20531ms
      message: 'load-balancer-api-external: tcp connection to aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:11:31Z"
    - latency: 9.363139ms
      message: 'load-balancer-api-external: resolved host name aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:11:31Z"
    - latency: 5.360042ms
      message: 'load-balancer-api-external: tcp connection to aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:10:31Z"
    - latency: 5.850764ms
      message: 'load-balancer-api-external: resolved host name aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:10:31Z"
    - latency: 7.158685ms
      message: 'load-balancer-api-external: tcp connection to aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:09:31Z"
    - latency: 10.66043ms
      message: 'load-balancer-api-external: resolved host name aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:09:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:43:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-78-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-78.ec2.internal
      uid: a9398b04-a952-4011-ae13-13d24973b1a0
    resourceVersion: "62506"
    uid: cadba8e1-f02c-45d0-b4a4-279524f444c9
  spec:
    sourcePod: network-check-source-7cbc45fddc-nd8ht
    targetEndpoint: aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:49:31Z"
      message: 'load-balancer-api-internal: tcp connection to aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.284362ms
      message: 'load-balancer-api-internal: tcp connection to aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:13:31Z"
    - latency: 8.905761ms
      message: 'load-balancer-api-internal: resolved host name aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:13:31Z"
    - latency: 5.226932ms
      message: 'load-balancer-api-internal: tcp connection to aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:12:31Z"
    - latency: 8.955621ms
      message: 'load-balancer-api-internal: resolved host name aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:12:31Z"
    - latency: 5.248257ms
      message: 'load-balancer-api-internal: tcp connection to aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:11:31Z"
    - latency: 9.304304ms
      message: 'load-balancer-api-internal: resolved host name aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:11:31Z"
    - latency: 5.375057ms
      message: 'load-balancer-api-internal: tcp connection to aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:10:31Z"
    - latency: 5.767338ms
      message: 'load-balancer-api-internal: resolved host name aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:10:31Z"
    - latency: 4.386051ms
      message: 'load-balancer-api-internal: tcp connection to aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:09:31Z"
    - latency: 10.507261ms
      message: 'load-balancer-api-internal: resolved host name aedecae88d2dd4de4a3f469bc81ec0b0-6f70e93a4e8d7f96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:09:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:43:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-78-to-network-check-target-ip-10-0-130-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-78.ec2.internal
      uid: a9398b04-a952-4011-ae13-13d24973b1a0
    resourceVersion: "60999"
    uid: 90b2f25d-d0b1-4c56-aadf-4248ecc54751
  spec:
    sourcePod: network-check-source-7cbc45fddc-nd8ht
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:50:31Z"
      message: 'network-check-target-ip-10-0-130-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.205592ms
      message: 'network-check-target-ip-10-0-130-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:11:31Z"
    - latency: 2.311381ms
      message: 'network-check-target-ip-10-0-130-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:10:31Z"
    - latency: 2.517985ms
      message: 'network-check-target-ip-10-0-130-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:09:31Z"
    - latency: 2.456414ms
      message: 'network-check-target-ip-10-0-130-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:08:31Z"
    - latency: 2.468208ms
      message: 'network-check-target-ip-10-0-130-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:07:31Z"
    - latency: 2.353997ms
      message: 'network-check-target-ip-10-0-130-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:06:31Z"
    - latency: 2.285424ms
      message: 'network-check-target-ip-10-0-130-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:05:31Z"
    - latency: 1.79864ms
      message: 'network-check-target-ip-10-0-130-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:04:31Z"
    - latency: 1.920034ms
      message: 'network-check-target-ip-10-0-130-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:03:31Z"
    - latency: 2.45336ms
      message: 'network-check-target-ip-10-0-130-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:02:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:43:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-78-to-network-check-target-ip-10-0-130-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-78.ec2.internal
      uid: a9398b04-a952-4011-ae13-13d24973b1a0
    resourceVersion: "60997"
    uid: d66d2ad4-79d3-480b-81c8-0c91409dce99
  spec:
    sourcePod: network-check-source-7cbc45fddc-nd8ht
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:50:31Z"
      message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 813.657µs
      message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:11:31Z"
    - latency: 1.072347ms
      message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:10:31Z"
    - latency: 1.99465ms
      message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:09:31Z"
    - latency: 1.2453ms
      message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:08:31Z"
    - latency: 1.398722ms
      message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:07:31Z"
    - latency: 957.365µs
      message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:06:31Z"
    - latency: 1.221787ms
      message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:05:31Z"
    - latency: 929.446µs
      message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:04:31Z"
    - latency: 1.380946ms
      message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:03:31Z"
    - latency: 1.037357ms
      message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:02:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:43:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-78-to-network-check-target-ip-10-0-132-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-78.ec2.internal
      uid: a9398b04-a952-4011-ae13-13d24973b1a0
    resourceVersion: "60998"
    uid: f4c07f8d-ef41-4afa-b1a7-82d57680f3b9
  spec:
    sourcePod: network-check-source-7cbc45fddc-nd8ht
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:50:31Z"
      message: 'network-check-target-ip-10-0-132-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.259625ms
      message: 'network-check-target-ip-10-0-132-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:11:31Z"
    - latency: 2.218902ms
      message: 'network-check-target-ip-10-0-132-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:10:31Z"
    - latency: 2.741323ms
      message: 'network-check-target-ip-10-0-132-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:09:31Z"
    - latency: 2.522089ms
      message: 'network-check-target-ip-10-0-132-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:08:31Z"
    - latency: 2.247647ms
      message: 'network-check-target-ip-10-0-132-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:07:31Z"
    - latency: 2.368345ms
      message: 'network-check-target-ip-10-0-132-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:06:31Z"
    - latency: 2.177262ms
      message: 'network-check-target-ip-10-0-132-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:05:31Z"
    - latency: 1.903273ms
      message: 'network-check-target-ip-10-0-132-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:04:31Z"
    - latency: 2.318659ms
      message: 'network-check-target-ip-10-0-132-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:03:31Z"
    - latency: 2.27181ms
      message: 'network-check-target-ip-10-0-132-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:02:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:43:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-78-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-78.ec2.internal
      uid: a9398b04-a952-4011-ae13-13d24973b1a0
    resourceVersion: "62504"
    uid: 4e843a21-550f-440b-bdd9-91d1a1f12b93
  spec:
    sourcePod: network-check-source-7cbc45fddc-nd8ht
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:49:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.866µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:13:31Z"
    - latency: 2.365269ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:13:31Z"
    - latency: 1.117222ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:12:31Z"
    - latency: 1.871455ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:12:31Z"
    - latency: 891.026µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:11:31Z"
    - latency: 2.183551ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:11:31Z"
    - latency: 1.130553ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:10:31Z"
    - latency: 1.749029ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:10:31Z"
    - latency: 897.373µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:09:31Z"
    - latency: 1.903313ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:09:31Z"
kind: List
metadata:
  resourceVersion: ""