apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:21:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 0cd35e36-8e4f-45fc-bf1a-904842da39b5
    resourceVersion: "54731"
    uid: 22082f44-fe7e-4966-99ea-4a0272c48099
  spec:
    sourcePod: network-check-source-989f8b8dc-v6tk4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:28:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.516µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:49Z"
    - latency: 876.538µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:49Z"
    - latency: 1.51075ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:49Z"
    - latency: 1.00073ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:53:49Z"
    - latency: 1.337041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:52:49Z"
    - latency: 879.333µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:51:49Z"
    - latency: 1.303975ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:50:49Z"
    - latency: 972.617µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:49:49Z"
    - latency: 1.332138ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:48:49Z"
    - latency: 780.825µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:47:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:21:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 0cd35e36-8e4f-45fc-bf1a-904842da39b5
    resourceVersion: "55850"
    uid: 99058887-cf1a-4ebf-830a-9520d247afd6
  spec:
    sourcePod: network-check-source-989f8b8dc-v6tk4
    targetEndpoint: a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:27:49Z"
      message: 'load-balancer-api-external: tcp connection to a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.721509ms
      message: 'load-balancer-api-external: tcp connection to a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:57:49Z"
    - latency: 12.158914ms
      message: 'load-balancer-api-external: resolved host name a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:57:49Z"
    - latency: 3.896339ms
      message: 'load-balancer-api-external: tcp connection to a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:49Z"
    - latency: 7.710464ms
      message: 'load-balancer-api-external: resolved host name a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:56:49Z"
    - latency: 4.581024ms
      message: 'load-balancer-api-external: tcp connection to a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:49Z"
    - latency: 7.180805ms
      message: 'load-balancer-api-external: resolved host name a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:55:49Z"
    - latency: 5.247438ms
      message: 'load-balancer-api-external: tcp connection to a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:49Z"
    - latency: 7.273433ms
      message: 'load-balancer-api-external: resolved host name a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:54:49Z"
    - latency: 5.669367ms
      message: 'load-balancer-api-external: tcp connection to a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:53:49Z"
    - latency: 6.740598ms
      message: 'load-balancer-api-external: resolved host name a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:53:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:21:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 0cd35e36-8e4f-45fc-bf1a-904842da39b5
    resourceVersion: "55849"
    uid: 4b959e9c-aa59-49ff-92bc-f80611ffc613
  spec:
    sourcePod: network-check-source-989f8b8dc-v6tk4
    targetEndpoint: a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:27:49Z"
      message: 'load-balancer-api-internal: tcp connection to a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.737254ms
      message: 'load-balancer-api-internal: tcp connection to a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:57:49Z"
    - latency: 12.065897ms
      message: 'load-balancer-api-internal: resolved host name a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:57:49Z"
    - latency: 3.81631ms
      message: 'load-balancer-api-internal: tcp connection to a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:49Z"
    - latency: 7.761892ms
      message: 'load-balancer-api-internal: resolved host name a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:56:49Z"
    - latency: 4.626652ms
      message: 'load-balancer-api-internal: tcp connection to a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:49Z"
    - latency: 7.087415ms
      message: 'load-balancer-api-internal: resolved host name a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:55:49Z"
    - latency: 5.21253ms
      message: 'load-balancer-api-internal: tcp connection to a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:49Z"
    - latency: 7.296081ms
      message: 'load-balancer-api-internal: resolved host name a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:54:49Z"
    - latency: 5.052195ms
      message: 'load-balancer-api-internal: tcp connection to a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:53:49Z"
    - latency: 6.640332ms
      message: 'load-balancer-api-internal: resolved host name a6475639b3ffa4535b9843989754e796-cf833db4cb02a259.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:53:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:21:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-network-check-target-ip-10-0-132-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 0cd35e36-8e4f-45fc-bf1a-904842da39b5
    resourceVersion: "54729"
    uid: 818f1721-4cd2-4d86-a356-af25f1e29d97
  spec:
    sourcePod: network-check-source-989f8b8dc-v6tk4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:28:49Z"
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 992.037µs
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:49Z"
    - latency: 1.526756ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:49Z"
    - latency: 1.00627ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:49Z"
    - latency: 1.074657ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:53:49Z"
    - latency: 1.164413ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:52:49Z"
    - latency: 1.404287ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:51:49Z"
    - latency: 1.009697ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:50:49Z"
    - latency: 1.139176ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:49:49Z"
    - latency: 984.796µs
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:48:49Z"
    - latency: 979.861µs
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:47:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:21:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-network-check-target-ip-10-0-133-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 0cd35e36-8e4f-45fc-bf1a-904842da39b5
    resourceVersion: "54728"
    uid: a11e3f6f-ba2d-47b6-bf90-7415abfb0743
  spec:
    sourcePod: network-check-source-989f8b8dc-v6tk4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:28:49Z"
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.926273ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:49Z"
    - latency: 1.919719ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:49Z"
    - latency: 1.959831ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:49Z"
    - latency: 1.718518ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:53:49Z"
    - latency: 1.904092ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:52:49Z"
    - latency: 1.648414ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:51:49Z"
    - latency: 2.066428ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:50:49Z"
    - latency: 2.081361ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:49:49Z"
    - latency: 2.11773ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:48:49Z"
    - latency: 1.78578ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:47:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:21:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-network-check-target-ip-10-0-134-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 0cd35e36-8e4f-45fc-bf1a-904842da39b5
    resourceVersion: "54730"
    uid: ac7d7a80-edbd-4e39-9a2f-ca99e00e43d8
  spec:
    sourcePod: network-check-source-989f8b8dc-v6tk4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:28:49Z"
      message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.933803ms
      message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:49Z"
    - latency: 2.261348ms
      message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:49Z"
    - latency: 2.286147ms
      message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:49Z"
    - latency: 2.135624ms
      message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:53:49Z"
    - latency: 2.091152ms
      message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:52:49Z"
    - latency: 2.136904ms
      message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:51:49Z"
    - latency: 2.295099ms
      message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:50:49Z"
    - latency: 2.460388ms
      message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:49:49Z"
    - latency: 2.170218ms
      message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:48:49Z"
    - latency: 2.154394ms
      message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:47:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T18:21:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 0cd35e36-8e4f-45fc-bf1a-904842da39b5
    resourceVersion: "55848"
    uid: 948c268d-22f0-4807-aee0-84ce174201af
  spec:
    sourcePod: network-check-source-989f8b8dc-v6tk4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T18:27:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.161666ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:57:49Z"
    - latency: 1.661951ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:57:49Z"
    - latency: 930.919µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:56:49Z"
    - latency: 2.029252ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:56:49Z"
    - latency: 1.254395ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:55:49Z"
    - latency: 1.765366ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:55:49Z"
    - latency: 1.080143ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:54:49Z"
    - latency: 1.820799ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:54:49Z"
    - latency: 1.22371ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T18:53:49Z"
    - latency: 1.799188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T18:53:49Z"
kind: List
metadata:
  resourceVersion: ""