apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: c67aa666-0126-41ae-ab4b-9d64ef864542
    resourceVersion: "54824"
    uid: 2b77a727-9070-4861-bd6b-86f5ec31cc0e
  spec:
    sourcePod: network-check-source-989f8b8dc-vdf4t
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:39:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.09025ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:11Z"
    - latency: 1.447977ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:11Z"
    - latency: 1.049013ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:11Z"
    - latency: 1.053255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:11Z"
    - latency: 898.903µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:11Z"
    - latency: 1.324389ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:11Z"
    - latency: 971.033µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:11Z"
    - latency: 1.053836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:11Z"
    - latency: 1.024062ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:11Z"
    - latency: 1.062203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: c67aa666-0126-41ae-ab4b-9d64ef864542
    resourceVersion: "55995"
    uid: 1af0564a-9799-4790-b710-2d0c9d94623c
  spec:
    sourcePod: network-check-source-989f8b8dc-vdf4t
    targetEndpoint: acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:38:11Z"
      message: 'load-balancer-api-external: tcp connection to acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.892522ms
      message: 'load-balancer-api-external: tcp connection to acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:11Z"
    - latency: 7.713444ms
      message: 'load-balancer-api-external: resolved host name acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:11Z"
    - latency: 5.097768ms
      message: 'load-balancer-api-external: tcp connection to acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:11Z"
    - latency: 7.647661ms
      message: 'load-balancer-api-external: resolved host name acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:11Z"
    - latency: 5.365584ms
      message: 'load-balancer-api-external: tcp connection to acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:11Z"
    - latency: 7.290724ms
      message: 'load-balancer-api-external: resolved host name acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:11Z"
    - latency: 4.760491ms
      message: 'load-balancer-api-external: tcp connection to acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:11Z"
    - latency: 18.613057ms
      message: 'load-balancer-api-external: resolved host name acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:11Z"
    - latency: 6.119055ms
      message: 'load-balancer-api-external: tcp connection to acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:11Z"
    - latency: 8.539428ms
      message: 'load-balancer-api-external: resolved host name acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: c67aa666-0126-41ae-ab4b-9d64ef864542
    resourceVersion: "55996"
    uid: 63addadb-6d58-4641-a2b7-82ccd823dedc
  spec:
    sourcePod: network-check-source-989f8b8dc-vdf4t
    targetEndpoint: acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:38:11Z"
      message: 'load-balancer-api-internal: tcp connection to acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.880418ms
      message: 'load-balancer-api-internal: tcp connection to acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:11Z"
    - latency: 7.664612ms
      message: 'load-balancer-api-internal: resolved host name acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:11Z"
    - latency: 9.293176ms
      message: 'load-balancer-api-internal: tcp connection to acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:11Z"
    - latency: 7.540251ms
      message: 'load-balancer-api-internal: resolved host name acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:11Z"
    - latency: 4.517564ms
      message: 'load-balancer-api-internal: tcp connection to acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:11Z"
    - latency: 7.222303ms
      message: 'load-balancer-api-internal: resolved host name acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:11Z"
    - latency: 6.189289ms
      message: 'load-balancer-api-internal: tcp connection to acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:11Z"
    - latency: 18.545701ms
      message: 'load-balancer-api-internal: resolved host name acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:11Z"
    - latency: 6.051019ms
      message: 'load-balancer-api-internal: tcp connection to acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:11Z"
    - latency: 8.51024ms
      message: 'load-balancer-api-internal: resolved host name acd028595317847db81edfdd98eff41b-54b36feb6ca41253.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-network-check-target-ip-10-0-130-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: c67aa666-0126-41ae-ab4b-9d64ef864542
    resourceVersion: "54823"
    uid: d0290e0f-0616-4610-8ad8-d4d077a299ab
  spec:
    sourcePod: network-check-source-989f8b8dc-vdf4t
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:39:11Z"
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.18341ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:11Z"
    - latency: 2.122487ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:11Z"
    - latency: 2.256752ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:11Z"
    - latency: 2.402526ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:11Z"
    - latency: 2.161904ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:11Z"
    - latency: 2.051249ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:11Z"
    - latency: 2.248237ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:11Z"
    - latency: 2.238677ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:11Z"
    - latency: 2.059572ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:11Z"
    - latency: 2.353914ms
      message: 'network-check-target-ip-10-0-130-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-network-check-target-ip-10-0-137-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: c67aa666-0126-41ae-ab4b-9d64ef864542
    resourceVersion: "54822"
    uid: 86bbbaec-4808-47ef-9ef6-83b8bc3e07d7
  spec:
    sourcePod: network-check-source-989f8b8dc-vdf4t
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:39:11Z"
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 973.305µs
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:11Z"
    - latency: 766.905µs
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:11Z"
    - latency: 1.662191ms
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:11Z"
    - latency: 774.444µs
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:11Z"
    - latency: 829.448µs
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:11Z"
    - latency: 1.030161ms
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:11Z"
    - latency: 1.560023ms
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:11Z"
    - latency: 949.693µs
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:11Z"
    - latency: 1.420257ms
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:11Z"
    - latency: 826.11µs
      message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-network-check-target-ip-10-0-141-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: c67aa666-0126-41ae-ab4b-9d64ef864542
    resourceVersion: "54821"
    uid: 18180685-29ce-494a-bbc4-cd8102e1f33c
  spec:
    sourcePod: network-check-source-989f8b8dc-vdf4t
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:39:11Z"
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.020103ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:11Z"
    - latency: 1.739143ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:11Z"
    - latency: 1.962046ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:11Z"
    - latency: 1.819678ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:11Z"
    - latency: 1.649758ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:11Z"
    - latency: 1.766796ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:11Z"
    - latency: 1.506494ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:11Z"
    - latency: 1.911397ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:11Z"
    - latency: 1.921612ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:11Z"
    - latency: 1.931022ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-0-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-0.ec2.internal
      uid: c67aa666-0126-41ae-ab4b-9d64ef864542
    resourceVersion: "55994"
    uid: 8a009e9f-0bca-4589-b2c7-80546c210d40
  spec:
    sourcePod: network-check-source-989f8b8dc-vdf4t
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:38:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.129778ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:11Z"
    - latency: 1.586146ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:11Z"
    - latency: 893.277µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:11Z"
    - latency: 2.005262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:11Z"
    - latency: 887.127µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:11Z"
    - latency: 2.117132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:11Z"
    - latency: 1.03809ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:11Z"
    - latency: 1.68966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:11Z"
    - latency: 1.211932ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:11Z"
    - latency: 1.74655ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:11Z"
kind: List
metadata:
  resourceVersion: ""