apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:14:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.ec2.internal
      uid: fa72b23a-0cfb-4c29-a202-e71097388714
    resourceVersion: "52361"
    uid: 317c47b0-06a8-4aa7-beeb-8ef162039099
  spec:
    sourcePod: network-check-source-6947749cfc-jzbx6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:21:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.165µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:49:11Z"
    - latency: 1.479851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:48:11Z"
    - latency: 1.541834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:47:11Z"
    - latency: 1.243607ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:46:11Z"
    - latency: 1.201766ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:45:11Z"
    - latency: 1.112636ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:44:11Z"
    - latency: 1.23651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:43:11Z"
    - latency: 1.149652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:42:11Z"
    - latency: 1.142866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:41:11Z"
    - latency: 1.08188ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:40:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:14:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.ec2.internal
      uid: fa72b23a-0cfb-4c29-a202-e71097388714
    resourceVersion: "52991"
    uid: fa30bf94-80e8-4fc0-bbb7-7d64af385187
  spec:
    sourcePod: network-check-source-6947749cfc-jzbx6
    targetEndpoint: a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:20:11Z"
      message: 'load-balancer-api-external: tcp connection to a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.446184ms
      message: 'load-balancer-api-external: tcp connection to a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:50:11Z"
    - latency: 7.160348ms
      message: 'load-balancer-api-external: resolved host name a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:50:11Z"
    - latency: 5.097372ms
      message: 'load-balancer-api-external: tcp connection to a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:49:11Z"
    - latency: 7.333971ms
      message: 'load-balancer-api-external: resolved host name a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:49:11Z"
    - latency: 4.920423ms
      message: 'load-balancer-api-external: tcp connection to a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:48:11Z"
    - latency: 8.15868ms
      message: 'load-balancer-api-external: resolved host name a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:48:11Z"
    - latency: 4.335739ms
      message: 'load-balancer-api-external: tcp connection to a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:47:11Z"
    - latency: 7.276716ms
      message: 'load-balancer-api-external: resolved host name a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:47:11Z"
    - latency: 4.846255ms
      message: 'load-balancer-api-external: tcp connection to a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:46:11Z"
    - latency: 7.369097ms
      message: 'load-balancer-api-external: resolved host name a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:46:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:14:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.ec2.internal
      uid: fa72b23a-0cfb-4c29-a202-e71097388714
    resourceVersion: "52990"
    uid: 813bdb29-3ffb-4c94-9e11-1ddcbc3c45c3
  spec:
    sourcePod: network-check-source-6947749cfc-jzbx6
    targetEndpoint: a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:20:11Z"
      message: 'load-balancer-api-internal: tcp connection to a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.002771ms
      message: 'load-balancer-api-internal: tcp connection to a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:50:11Z"
    - latency: 7.240301ms
      message: 'load-balancer-api-internal: resolved host name a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:50:11Z"
    - latency: 5.111674ms
      message: 'load-balancer-api-internal: tcp connection to a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:49:11Z"
    - latency: 7.437106ms
      message: 'load-balancer-api-internal: resolved host name a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:49:11Z"
    - latency: 4.891245ms
      message: 'load-balancer-api-internal: tcp connection to a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:48:11Z"
    - latency: 8.232558ms
      message: 'load-balancer-api-internal: resolved host name a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:48:11Z"
    - latency: 4.300701ms
      message: 'load-balancer-api-internal: tcp connection to a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:47:11Z"
    - latency: 7.405685ms
      message: 'load-balancer-api-internal: resolved host name a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:47:11Z"
    - latency: 4.950514ms
      message: 'load-balancer-api-internal: tcp connection to a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:46:11Z"
    - latency: 7.498718ms
      message: 'load-balancer-api-internal: resolved host name a322917730e264fb1b80d111b183b166-15b858f32d9d74c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:46:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:14:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-network-check-target-ip-10-0-130-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.ec2.internal
      uid: fa72b23a-0cfb-4c29-a202-e71097388714
    resourceVersion: "52360"
    uid: 49091af2-a67b-468b-91d8-659e476ca798
  spec:
    sourcePod: network-check-source-6947749cfc-jzbx6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:21:11Z"
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.01247ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:49:11Z"
    - latency: 2.211065ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:48:11Z"
    - latency: 2.071899ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:47:11Z"
    - latency: 1.694748ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:46:11Z"
    - latency: 2.008324ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:45:11Z"
    - latency: 1.889177ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:44:11Z"
    - latency: 1.858852ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:43:11Z"
    - latency: 2.158254ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:42:11Z"
    - latency: 2.097296ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:41:11Z"
    - latency: 2.080075ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:40:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:14:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-network-check-target-ip-10-0-131-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.ec2.internal
      uid: fa72b23a-0cfb-4c29-a202-e71097388714
    resourceVersion: "52358"
    uid: 0d818f0a-cca5-433a-b633-3fb514c161ab
  spec:
    sourcePod: network-check-source-6947749cfc-jzbx6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:21:11Z"
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 905.49µs
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:49:11Z"
    - latency: 1.555047ms
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:48:11Z"
    - latency: 1.748048ms
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:47:11Z"
    - latency: 907.493µs
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:46:11Z"
    - latency: 1.439186ms
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:45:11Z"
    - latency: 965.392µs
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:44:11Z"
    - latency: 969.298µs
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:43:11Z"
    - latency: 866.682µs
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:42:11Z"
    - latency: 931.682µs
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:41:11Z"
    - latency: 1.125507ms
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:40:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:14:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-network-check-target-ip-10-0-143-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.ec2.internal
      uid: fa72b23a-0cfb-4c29-a202-e71097388714
    resourceVersion: "52359"
    uid: 837ab579-b119-4dc1-895b-4d1946404c41
  spec:
    sourcePod: network-check-source-6947749cfc-jzbx6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:21:11Z"
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.09729ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:49:11Z"
    - latency: 2.144144ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:48:11Z"
    - latency: 2.394897ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:47:11Z"
    - latency: 2.297918ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:46:11Z"
    - latency: 2.206056ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:45:11Z"
    - latency: 2.170532ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:44:11Z"
    - latency: 2.457039ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:43:11Z"
    - latency: 2.186176ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:42:11Z"
    - latency: 2.096009ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:41:11Z"
    - latency: 2.302802ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:40:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:14:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.ec2.internal
      uid: fa72b23a-0cfb-4c29-a202-e71097388714
    resourceVersion: "52989"
    uid: 3683f2fc-f6f6-4f73-802a-e6f05695ad81
  spec:
    sourcePod: network-check-source-6947749cfc-jzbx6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:20:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.048786ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:50:11Z"
    - latency: 1.746106ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:50:11Z"
    - latency: 923.05µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:49:11Z"
    - latency: 2.01088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:49:11Z"
    - latency: 932.831µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:48:11Z"
    - latency: 1.874251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:48:11Z"
    - latency: 1.13376ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:47:11Z"
    - latency: 2.087756ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:47:11Z"
    - latency: 1.246363ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:46:11Z"
    - latency: 1.810751ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:46:11Z"
kind: List
metadata:
  resourceVersion: ""