apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:39:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-66-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-66.ec2.internal
      uid: 23f66723-2a80-458b-827c-059acc77510d
    resourceVersion: "20386"
    uid: 84f6c40d-cb6c-4733-9a81-442e58e786dd
  spec:
    sourcePod: network-check-source-685456655f-b8gsv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:46:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 795.079µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:00:58Z"
    - latency: 1.145573ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:59:58Z"
    - latency: 1.272138ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:58:58Z"
    - latency: 1.022688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:57:58Z"
    - latency: 933.804µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:56:58Z"
    - latency: 950.298µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:55:58Z"
    - latency: 1.009617ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:54:58Z"
    - latency: 1.061137ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:53:58Z"
    - latency: 828.436µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:52:58Z"
    - latency: 931.565µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:51:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:39:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-66-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-66.ec2.internal
      uid: 23f66723-2a80-458b-827c-059acc77510d
    resourceVersion: "21882"
    uid: e6d87316-cd73-4389-8133-20c9267d344a
  spec:
    sourcePod: network-check-source-685456655f-b8gsv
    targetEndpoint: a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:45:58Z"
      message: 'load-balancer-api-external: tcp connection to a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.37181ms
      message: 'load-balancer-api-external: tcp connection to a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:03:58Z"
    - latency: 10.409622ms
      message: 'load-balancer-api-external: resolved host name a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:03:58Z"
    - latency: 5.156944ms
      message: 'load-balancer-api-external: tcp connection to a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:02:58Z"
    - latency: 9.210653ms
      message: 'load-balancer-api-external: resolved host name a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:02:58Z"
    - latency: 4.816816ms
      message: 'load-balancer-api-external: tcp connection to a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:01:58Z"
    - latency: 8.496002ms
      message: 'load-balancer-api-external: resolved host name a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:01:58Z"
    - latency: 5.123621ms
      message: 'load-balancer-api-external: tcp connection to a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:00:58Z"
    - latency: 7.92645ms
      message: 'load-balancer-api-external: resolved host name a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:00:58Z"
    - latency: 4.530587ms
      message: 'load-balancer-api-external: tcp connection to a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:59:58Z"
    - latency: 7.753254ms
      message: 'load-balancer-api-external: resolved host name a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:59:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:39:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-66-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-66.ec2.internal
      uid: 23f66723-2a80-458b-827c-059acc77510d
    resourceVersion: "21881"
    uid: 56e36467-d75c-4a16-a10e-08d5b91b6a7d
  spec:
    sourcePod: network-check-source-685456655f-b8gsv
    targetEndpoint: a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:45:58Z"
      message: 'load-balancer-api-internal: tcp connection to a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.385823ms
      message: 'load-balancer-api-internal: tcp connection to a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:03:58Z"
    - latency: 10.354033ms
      message: 'load-balancer-api-internal: resolved host name a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:03:58Z"
    - latency: 5.080186ms
      message: 'load-balancer-api-internal: tcp connection to a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:02:58Z"
    - latency: 9.38526ms
      message: 'load-balancer-api-internal: resolved host name a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:02:58Z"
    - latency: 4.80548ms
      message: 'load-balancer-api-internal: tcp connection to a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:01:58Z"
    - latency: 8.66554ms
      message: 'load-balancer-api-internal: resolved host name a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:01:58Z"
    - latency: 5.079792ms
      message: 'load-balancer-api-internal: tcp connection to a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:00:58Z"
    - latency: 8.001285ms
      message: 'load-balancer-api-internal: resolved host name a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:00:58Z"
    - latency: 4.538519ms
      message: 'load-balancer-api-internal: tcp connection to a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:59:58Z"
    - latency: 7.839112ms
      message: 'load-balancer-api-internal: resolved host name a81bfe3c2e1d54ab2ae3ed1ea30b7681-d967517a6e2c07a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:59:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:39:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-66-to-network-check-target-ip-10-0-130-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-66.ec2.internal
      uid: 23f66723-2a80-458b-827c-059acc77510d
    resourceVersion: "20385"
    uid: 593375bd-ab41-4af2-8ae2-b8de7d79f251
  spec:
    sourcePod: network-check-source-685456655f-b8gsv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:46:58Z"
      message: 'network-check-target-ip-10-0-130-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.367198ms
      message: 'network-check-target-ip-10-0-130-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:00:58Z"
    - latency: 2.157478ms
      message: 'network-check-target-ip-10-0-130-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:59:58Z"
    - latency: 2.074788ms
      message: 'network-check-target-ip-10-0-130-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:58:58Z"
    - latency: 2.388865ms
      message: 'network-check-target-ip-10-0-130-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:57:58Z"
    - latency: 2.744545ms
      message: 'network-check-target-ip-10-0-130-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:56:58Z"
    - latency: 2.245977ms
      message: 'network-check-target-ip-10-0-130-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:55:58Z"
    - latency: 2.271576ms
      message: 'network-check-target-ip-10-0-130-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:54:58Z"
    - latency: 2.323134ms
      message: 'network-check-target-ip-10-0-130-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:53:58Z"
    - latency: 2.119492ms
      message: 'network-check-target-ip-10-0-130-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:52:58Z"
    - latency: 2.379139ms
      message: 'network-check-target-ip-10-0-130-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:51:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:39:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-66-to-network-check-target-ip-10-0-133-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-66.ec2.internal
      uid: 23f66723-2a80-458b-827c-059acc77510d
    resourceVersion: "20383"
    uid: c4760829-fb51-4048-8dc4-02cdc7a61c41
  spec:
    sourcePod: network-check-source-685456655f-b8gsv
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:46:58Z"
      message: 'network-check-target-ip-10-0-133-66: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 834.701µs
      message: 'network-check-target-ip-10-0-133-66: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:00:58Z"
    - latency: 933.78µs
      message: 'network-check-target-ip-10-0-133-66: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:59:58Z"
    - latency: 2.00327ms
      message: 'network-check-target-ip-10-0-133-66: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:58:58Z"
    - latency: 1.000467ms
      message: 'network-check-target-ip-10-0-133-66: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:57:58Z"
    - latency: 785.593µs
      message: 'network-check-target-ip-10-0-133-66: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:56:58Z"
    - latency: 942.658µs
      message: 'network-check-target-ip-10-0-133-66: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:55:58Z"
    - latency: 951.785µs
      message: 'network-check-target-ip-10-0-133-66: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:54:58Z"
    - latency: 996.262µs
      message: 'network-check-target-ip-10-0-133-66: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:53:58Z"
    - latency: 934.95µs
      message: 'network-check-target-ip-10-0-133-66: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:52:58Z"
    - latency: 903.393µs
      message: 'network-check-target-ip-10-0-133-66: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:51:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:39:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-66-to-network-check-target-ip-10-0-136-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-66.ec2.internal
      uid: 23f66723-2a80-458b-827c-059acc77510d
    resourceVersion: "20384"
    uid: 037f7770-206a-45da-8bef-757b128b2c87
  spec:
    sourcePod: network-check-source-685456655f-b8gsv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:46:58Z"
      message: 'network-check-target-ip-10-0-136-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.317767ms
      message: 'network-check-target-ip-10-0-136-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:00:58Z"
    - latency: 2.237824ms
      message: 'network-check-target-ip-10-0-136-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:59:58Z"
    - latency: 2.461291ms
      message: 'network-check-target-ip-10-0-136-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:58:58Z"
    - latency: 2.385627ms
      message: 'network-check-target-ip-10-0-136-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:57:58Z"
    - latency: 2.195903ms
      message: 'network-check-target-ip-10-0-136-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:56:58Z"
    - latency: 2.271002ms
      message: 'network-check-target-ip-10-0-136-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:55:58Z"
    - latency: 2.48004ms
      message: 'network-check-target-ip-10-0-136-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:54:58Z"
    - latency: 2.23771ms
      message: 'network-check-target-ip-10-0-136-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:53:58Z"
    - latency: 2.182502ms
      message: 'network-check-target-ip-10-0-136-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:52:58Z"
    - latency: 2.312429ms
      message: 'network-check-target-ip-10-0-136-233: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:51:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T14:39:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-66-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-66.ec2.internal
      uid: 23f66723-2a80-458b-827c-059acc77510d
    resourceVersion: "21880"
    uid: ab3b71f2-27fb-4d8f-85e2-26256b87a34d
  spec:
    sourcePod: network-check-source-685456655f-b8gsv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T14:45:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.519µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:03:58Z"
    - latency: 1.908566ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:03:58Z"
    - latency: 843.173µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:02:58Z"
    - latency: 1.788444ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:02:58Z"
    - latency: 856.767µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:01:58Z"
    - latency: 1.823152ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:01:58Z"
    - latency: 938.299µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:00:58Z"
    - latency: 1.736043ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:00:58Z"
    - latency: 983.319µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T14:59:58Z"
    - latency: 1.87674ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T14:59:58Z"
kind: List
metadata:
  resourceVersion: ""