apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-2-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-2.ec2.internal
      uid: 3beec12e-8619-4245-9706-53d5d4f019a2
    resourceVersion: "54162"
    uid: d666b96e-6b58-4d68-9f82-c0efd4d38972
  spec:
    sourcePod: network-check-source-6f8b768455-r6gft
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:01:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.294433ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:22:49Z"
    - latency: 1.442067ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:21:49Z"
    - latency: 1.144562ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:49Z"
    - latency: 1.191083ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:19:49Z"
    - latency: 1.52618ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:18:49Z"
    - latency: 1.354365ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:17:49Z"
    - latency: 1.339399ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:16:49Z"
    - latency: 889.798µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:15:49Z"
    - latency: 1.635177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:14:49Z"
    - latency: 1.030554ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:13:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-2-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-2.ec2.internal
      uid: 3beec12e-8619-4245-9706-53d5d4f019a2
    resourceVersion: "55871"
    uid: 8d0da5df-81c6-4313-ab40-1998c5214ef0
  spec:
    sourcePod: network-check-source-6f8b768455-r6gft
    targetEndpoint: a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:00:49Z"
      message: 'load-balancer-api-external: tcp connection to a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.151122ms
      message: 'load-balancer-api-external: tcp connection to a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:24:49Z"
    - latency: 8.639362ms
      message: 'load-balancer-api-external: resolved host name a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:24:49Z"
    - latency: 3.928799ms
      message: 'load-balancer-api-external: tcp connection to a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:23:49Z"
    - latency: 11.82524ms
      message: 'load-balancer-api-external: resolved host name a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:23:49Z"
    - latency: 2.948523ms
      message: 'load-balancer-api-external: tcp connection to a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:22:49Z"
    - latency: 8.01056ms
      message: 'load-balancer-api-external: resolved host name a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:22:49Z"
    - latency: 3.977226ms
      message: 'load-balancer-api-external: tcp connection to a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:21:49Z"
    - latency: 8.722409ms
      message: 'load-balancer-api-external: resolved host name a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:21:49Z"
    - latency: 3.569983ms
      message: 'load-balancer-api-external: tcp connection to a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:49Z"
    - latency: 9.415834ms
      message: 'load-balancer-api-external: resolved host name a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:20:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-2-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-2.ec2.internal
      uid: 3beec12e-8619-4245-9706-53d5d4f019a2
    resourceVersion: "55870"
    uid: d4ecfb08-84d7-41b4-8f0d-159ec760e728
  spec:
    sourcePod: network-check-source-6f8b768455-r6gft
    targetEndpoint: a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:00:49Z"
      message: 'load-balancer-api-internal: tcp connection to a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.183794ms
      message: 'load-balancer-api-internal: tcp connection to a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:24:49Z"
    - latency: 8.585167ms
      message: 'load-balancer-api-internal: resolved host name a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:24:49Z"
    - latency: 7.020772ms
      message: 'load-balancer-api-internal: tcp connection to a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:23:49Z"
    - latency: 11.861673ms
      message: 'load-balancer-api-internal: resolved host name a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:23:49Z"
    - latency: 5.417569ms
      message: 'load-balancer-api-internal: tcp connection to a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:22:49Z"
    - latency: 8.048712ms
      message: 'load-balancer-api-internal: resolved host name a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:22:49Z"
    - latency: 3.995333ms
      message: 'load-balancer-api-internal: tcp connection to a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:21:49Z"
    - latency: 8.658868ms
      message: 'load-balancer-api-internal: resolved host name a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:21:49Z"
    - latency: 4.692718ms
      message: 'load-balancer-api-internal: tcp connection to a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:49Z"
    - latency: 9.521588ms
      message: 'load-balancer-api-internal: resolved host name a4e59fe5c81fa48869e76625d3480d01-4dc330a30405146f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:20:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-2-to-network-check-target-ip-10-0-130-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-2.ec2.internal
      uid: 3beec12e-8619-4245-9706-53d5d4f019a2
    resourceVersion: "54159"
    uid: ece5f83e-0be6-4c4d-badd-4f9cef0c7ee5
  spec:
    sourcePod: network-check-source-6f8b768455-r6gft
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:01:49Z"
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.120257ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:22:49Z"
    - latency: 879.107µs
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:21:49Z"
    - latency: 1.092567ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:49Z"
    - latency: 953.234µs
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:19:49Z"
    - latency: 956.964µs
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:18:49Z"
    - latency: 932.566µs
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:17:49Z"
    - latency: 880.861µs
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:16:49Z"
    - latency: 795.371µs
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:15:49Z"
    - latency: 950.287µs
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:14:49Z"
    - latency: 1.214983ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:13:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-2-to-network-check-target-ip-10-0-136-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-2.ec2.internal
      uid: 3beec12e-8619-4245-9706-53d5d4f019a2
    resourceVersion: "54161"
    uid: b26af550-3a62-4568-a89a-5841b2a9b523
  spec:
    sourcePod: network-check-source-6f8b768455-r6gft
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:01:49Z"
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.385459ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:22:49Z"
    - latency: 2.403638ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:21:49Z"
    - latency: 2.738677ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:49Z"
    - latency: 2.358796ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:19:49Z"
    - latency: 3.448233ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:18:49Z"
    - latency: 2.713058ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:17:49Z"
    - latency: 2.340911ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:16:49Z"
    - latency: 2.449375ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:15:49Z"
    - latency: 2.502455ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:14:49Z"
    - latency: 2.388548ms
      message: 'network-check-target-ip-10-0-136-222: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:13:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-2-to-network-check-target-ip-10-0-138-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-2.ec2.internal
      uid: 3beec12e-8619-4245-9706-53d5d4f019a2
    resourceVersion: "54160"
    uid: 7a47b127-00b4-41ce-af79-022dfebddba9
  spec:
    sourcePod: network-check-source-6f8b768455-r6gft
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:01:49Z"
      message: 'network-check-target-ip-10-0-138-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.21529ms
      message: 'network-check-target-ip-10-0-138-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:22:49Z"
    - latency: 2.288258ms
      message: 'network-check-target-ip-10-0-138-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:21:49Z"
    - latency: 2.325932ms
      message: 'network-check-target-ip-10-0-138-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:49Z"
    - latency: 2.142931ms
      message: 'network-check-target-ip-10-0-138-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:19:49Z"
    - latency: 2.179053ms
      message: 'network-check-target-ip-10-0-138-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:18:49Z"
    - latency: 2.212689ms
      message: 'network-check-target-ip-10-0-138-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:17:49Z"
    - latency: 2.299486ms
      message: 'network-check-target-ip-10-0-138-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:16:49Z"
    - latency: 2.037501ms
      message: 'network-check-target-ip-10-0-138-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:15:49Z"
    - latency: 2.268239ms
      message: 'network-check-target-ip-10-0-138-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:14:49Z"
    - latency: 2.079967ms
      message: 'network-check-target-ip-10-0-138-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:13:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-2-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-2.ec2.internal
      uid: 3beec12e-8619-4245-9706-53d5d4f019a2
    resourceVersion: "55869"
    uid: 430d8abd-ef68-40b8-945f-c4121ef446b3
  spec:
    sourcePod: network-check-source-6f8b768455-r6gft
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:00:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.008651ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:24:49Z"
    - latency: 1.809628ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:24:49Z"
    - latency: 1.147721ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:23:49Z"
    - latency: 2.363689ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:23:49Z"
    - latency: 1.321328ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:22:49Z"
    - latency: 1.66341ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:22:49Z"
    - latency: 1.065899ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:21:49Z"
    - latency: 1.90239ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:21:49Z"
    - latency: 1.429288ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:49Z"
    - latency: 2.13228ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:20:49Z"
kind: List
metadata:
  resourceVersion: ""