apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:14:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-193-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-193.ec2.internal
      uid: 49b2f388-52f1-4c69-8319-73fabddf0602
    resourceVersion: "165206"
    uid: cb576332-dcb3-4439-8c88-b55973472717
  spec:
    sourcePod: network-check-source-6f78d59f99-q9cfc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:21:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 906.611µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:24:33Z"
    - latency: 964.905µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:23:33Z"
    - latency: 908.832µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:22:33Z"
    - latency: 1.472117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:21:33Z"
    - latency: 1.38612ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:20:33Z"
    - latency: 2.086151ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:19:33Z"
    - latency: 1.421771ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:18:33Z"
    - latency: 1.703388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:17:33Z"
    - latency: 1.463484ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:16:33Z"
    - latency: 1.549152ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:15:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:14:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-193-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-193.ec2.internal
      uid: 49b2f388-52f1-4c69-8319-73fabddf0602
    resourceVersion: "160300"
    uid: 0dd4f6cd-0b0e-447b-a243-1eb76ed3adab
  spec:
    sourcePod: network-check-source-6f78d59f99-q9cfc
    targetEndpoint: a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:20:33Z"
      message: 'load-balancer-api-external: tcp connection to a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.922815ms
      message: 'load-balancer-api-external: tcp connection to a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:20:33Z"
    - latency: 7.452563ms
      message: 'load-balancer-api-external: resolved host name a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:20:33Z"
    - latency: 17.764845ms
      message: 'load-balancer-api-external: tcp connection to a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:19:33Z"
    - latency: 8.525655ms
      message: 'load-balancer-api-external: resolved host name a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:19:33Z"
    - latency: 16.394886ms
      message: 'load-balancer-api-external: tcp connection to a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:18:33Z"
    - latency: 6.854456ms
      message: 'load-balancer-api-external: resolved host name a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:18:33Z"
    - latency: 16.115669ms
      message: 'load-balancer-api-external: tcp connection to a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:17:33Z"
    - latency: 9.488356ms
      message: 'load-balancer-api-external: resolved host name a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:17:33Z"
    - latency: 19.380003ms
      message: 'load-balancer-api-external: tcp connection to a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:16:33Z"
    - latency: 7.226504ms
      message: 'load-balancer-api-external: resolved host name a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:16:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:14:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-193-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-193.ec2.internal
      uid: 49b2f388-52f1-4c69-8319-73fabddf0602
    resourceVersion: "160301"
    uid: 653f5c80-d919-45aa-b845-1b89e150de83
  spec:
    sourcePod: network-check-source-6f78d59f99-q9cfc
    targetEndpoint: a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:20:33Z"
      message: 'load-balancer-api-internal: tcp connection to a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.352801ms
      message: 'load-balancer-api-internal: tcp connection to a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:20:33Z"
    - latency: 7.52521ms
      message: 'load-balancer-api-internal: resolved host name a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:20:33Z"
    - latency: 18.594595ms
      message: 'load-balancer-api-internal: tcp connection to a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:19:33Z"
    - latency: 8.671608ms
      message: 'load-balancer-api-internal: resolved host name a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:19:33Z"
    - latency: 16.424111ms
      message: 'load-balancer-api-internal: tcp connection to a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:18:33Z"
    - latency: 6.887863ms
      message: 'load-balancer-api-internal: resolved host name a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:18:33Z"
    - latency: 17.769721ms
      message: 'load-balancer-api-internal: tcp connection to a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:17:33Z"
    - latency: 9.564483ms
      message: 'load-balancer-api-internal: resolved host name a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:17:33Z"
    - latency: 17.136619ms
      message: 'load-balancer-api-internal: tcp connection to a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:16:33Z"
    - latency: 7.270569ms
      message: 'load-balancer-api-internal: resolved host name a267d71b4e6414faf84e06b2ef860b65-0bb1677787aa549a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:16:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:14:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-193-to-network-check-target-ip-10-0-128-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-193.ec2.internal
      uid: 49b2f388-52f1-4c69-8319-73fabddf0602
    resourceVersion: "165204"
    uid: 784b00ce-d0cd-4415-9319-c1dc4109e4eb
  spec:
    sourcePod: network-check-source-6f78d59f99-q9cfc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:21:33Z"
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.368627ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:24:33Z"
    - latency: 2.365442ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:23:33Z"
    - latency: 2.152933ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:22:33Z"
    - latency: 2.162505ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:21:33Z"
    - latency: 2.623537ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:20:33Z"
    - latency: 3.155723ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:19:33Z"
    - latency: 2.428774ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:18:33Z"
    - latency: 2.42769ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:17:33Z"
    - latency: 2.809696ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:16:33Z"
    - latency: 2.179633ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:15:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:14:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-193-to-network-check-target-ip-10-0-133-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-193.ec2.internal
      uid: 49b2f388-52f1-4c69-8319-73fabddf0602
    resourceVersion: "165203"
    uid: 71c0f666-8c7d-47db-897a-6e5ad5fb2557
  spec:
    sourcePod: network-check-source-6f78d59f99-q9cfc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:21:33Z"
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.254µs
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:24:33Z"
    - latency: 1.017753ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:23:33Z"
    - latency: 1.244635ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:22:33Z"
    - latency: 848.458µs
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:21:33Z"
    - latency: 1.105143ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:20:33Z"
    - latency: 1.792853ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:19:33Z"
    - latency: 908.187µs
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:18:33Z"
    - latency: 1.159718ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:17:33Z"
    - latency: 1.670065ms
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:16:33Z"
    - latency: 820.643µs
      message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:15:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:14:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-193-to-network-check-target-ip-10-0-139-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-193.ec2.internal
      uid: 49b2f388-52f1-4c69-8319-73fabddf0602
    resourceVersion: "165205"
    uid: 7747c9c0-017f-4da4-b943-284d9c98b0b9
  spec:
    sourcePod: network-check-source-6f78d59f99-q9cfc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:21:33Z"
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.335323ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:24:33Z"
    - latency: 2.272786ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:23:33Z"
    - latency: 2.617605ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:22:33Z"
    - latency: 2.352872ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:21:33Z"
    - latency: 2.654016ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:20:33Z"
    - latency: 3.38433ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:19:33Z"
    - latency: 1.945167ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:18:33Z"
    - latency: 2.433606ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:17:33Z"
    - latency: 2.311079ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:16:33Z"
    - latency: 2.307926ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:15:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:14:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-193-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-193.ec2.internal
      uid: 49b2f388-52f1-4c69-8319-73fabddf0602
    resourceVersion: "160298"
    uid: 5e72d8de-1403-445b-8d56-446dcce763d8
  spec:
    sourcePod: network-check-source-6f78d59f99-q9cfc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:20:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.304042ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:20:33Z"
    - latency: 2.650607ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:20:33Z"
    - latency: 1.254876ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:19:33Z"
    - latency: 2.014354ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:19:33Z"
    - latency: 1.331089ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:18:33Z"
    - latency: 1.889146ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:18:33Z"
    - latency: 1.220285ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:17:33Z"
    - latency: 2.199687ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:17:33Z"
    - latency: 1.285164ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:16:33Z"
    - latency: 1.878927ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:16:33Z"
kind: List
metadata:
  resourceVersion: ""