apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:55:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: a4e53c03-2eaf-4721-8455-56631451fe61
    resourceVersion: "32303"
    uid: 4c595903-3d49-4b41-bfdb-da533d0d8869
  spec:
    sourcePod: network-check-source-685456655f-nnf7c
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:02:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.052755ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:37:36Z"
    - latency: 1.019324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:36:36Z"
    - latency: 1.319377ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:35:36Z"
    - latency: 1.01274ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:34:36Z"
    - latency: 948.041µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:33:36Z"
    - latency: 856.917µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:32:36Z"
    - latency: 895.668µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:31:36Z"
    - latency: 1.079164ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:30:36Z"
    - latency: 970.303µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:29:36Z"
    - latency: 1.3056ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:55:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: a4e53c03-2eaf-4721-8455-56631451fe61
    resourceVersion: "32304"
    uid: 3173ea3d-8bf9-4b5d-a5de-5d5272dd118d
  spec:
    sourcePod: network-check-source-685456655f-nnf7c
    targetEndpoint: aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:01:36Z"
      message: 'load-balancer-api-external: tcp connection to aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.636786ms
      message: 'load-balancer-api-external: tcp connection to aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:37:36Z"
    - latency: 8.131765ms
      message: 'load-balancer-api-external: resolved host name aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:37:36Z"
    - latency: 4.859759ms
      message: 'load-balancer-api-external: tcp connection to aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:36:36Z"
    - latency: 8.147698ms
      message: 'load-balancer-api-external: resolved host name aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:36:36Z"
    - latency: 4.924698ms
      message: 'load-balancer-api-external: tcp connection to aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:35:36Z"
    - latency: 8.346089ms
      message: 'load-balancer-api-external: resolved host name aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:35:36Z"
    - latency: 4.94997ms
      message: 'load-balancer-api-external: tcp connection to aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:34:36Z"
    - latency: 8.47667ms
      message: 'load-balancer-api-external: resolved host name aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:34:36Z"
    - latency: 6.22197ms
      message: 'load-balancer-api-external: tcp connection to aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:33:36Z"
    - latency: 9.712908ms
      message: 'load-balancer-api-external: resolved host name aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:33:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:55:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: a4e53c03-2eaf-4721-8455-56631451fe61
    resourceVersion: "32305"
    uid: 904d4d83-1cb1-427d-b049-22d14215ef2b
  spec:
    sourcePod: network-check-source-685456655f-nnf7c
    targetEndpoint: aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:01:36Z"
      message: 'load-balancer-api-internal: tcp connection to aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.121877ms
      message: 'load-balancer-api-internal: tcp connection to aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:37:36Z"
    - latency: 8.044022ms
      message: 'load-balancer-api-internal: resolved host name aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:37:36Z"
    - latency: 4.848461ms
      message: 'load-balancer-api-internal: tcp connection to aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:36:36Z"
    - latency: 8.060701ms
      message: 'load-balancer-api-internal: resolved host name aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:36:36Z"
    - latency: 4.933954ms
      message: 'load-balancer-api-internal: tcp connection to aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:35:36Z"
    - latency: 8.23441ms
      message: 'load-balancer-api-internal: resolved host name aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:35:36Z"
    - latency: 4.956967ms
      message: 'load-balancer-api-internal: tcp connection to aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:34:36Z"
    - latency: 8.424118ms
      message: 'load-balancer-api-internal: resolved host name aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:34:36Z"
    - latency: 5.438059ms
      message: 'load-balancer-api-internal: tcp connection to aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:33:36Z"
    - latency: 9.693915ms
      message: 'load-balancer-api-internal: resolved host name aff744af3abfb4dc7af7ddb2642b55b6-84136e1cab53432f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:33:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:55:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-network-check-target-ip-10-0-129-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: a4e53c03-2eaf-4721-8455-56631451fe61
    resourceVersion: "32301"
    uid: 97d26b0f-0333-4888-aabc-be2d50fbbc4d
  spec:
    sourcePod: network-check-source-685456655f-nnf7c
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:02:36Z"
      message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.518568ms
      message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:37:36Z"
    - latency: 2.336254ms
      message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:36:36Z"
    - latency: 2.412039ms
      message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:35:36Z"
    - latency: 2.368149ms
      message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:34:36Z"
    - latency: 2.263356ms
      message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:33:36Z"
    - latency: 2.300625ms
      message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:32:36Z"
    - latency: 2.271911ms
      message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:31:36Z"
    - latency: 2.583018ms
      message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:30:36Z"
    - latency: 2.502551ms
      message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:29:36Z"
    - latency: 2.326306ms
      message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:55:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-network-check-target-ip-10-0-140-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: a4e53c03-2eaf-4721-8455-56631451fe61
    resourceVersion: "32299"
    uid: ea1b43a4-0056-48dd-a7be-91bf5bcaf24e
  spec:
    sourcePod: network-check-source-685456655f-nnf7c
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:02:36Z"
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 759.981µs
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:37:36Z"
    - latency: 1.071612ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:36:36Z"
    - latency: 1.010177ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:35:36Z"
    - latency: 849.867µs
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:34:36Z"
    - latency: 1.438713ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:33:36Z"
    - latency: 855.394µs
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:32:36Z"
    - latency: 789.608µs
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:31:36Z"
    - latency: 792.538µs
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:30:36Z"
    - latency: 840.691µs
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:29:36Z"
    - latency: 685.769µs
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:55:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-network-check-target-ip-10-0-142-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: a4e53c03-2eaf-4721-8455-56631451fe61
    resourceVersion: "32302"
    uid: 123d6af3-44cf-448d-9ceb-f210b50cecfb
  spec:
    sourcePod: network-check-source-685456655f-nnf7c
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:02:36Z"
      message: 'network-check-target-ip-10-0-142-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.91127ms
      message: 'network-check-target-ip-10-0-142-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:37:36Z"
    - latency: 2.02899ms
      message: 'network-check-target-ip-10-0-142-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:36:36Z"
    - latency: 2.184661ms
      message: 'network-check-target-ip-10-0-142-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:35:36Z"
    - latency: 2.152039ms
      message: 'network-check-target-ip-10-0-142-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:34:36Z"
    - latency: 2.19701ms
      message: 'network-check-target-ip-10-0-142-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:33:36Z"
    - latency: 2.219155ms
      message: 'network-check-target-ip-10-0-142-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:32:36Z"
    - latency: 1.857692ms
      message: 'network-check-target-ip-10-0-142-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:31:36Z"
    - latency: 2.182114ms
      message: 'network-check-target-ip-10-0-142-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:30:36Z"
    - latency: 2.329409ms
      message: 'network-check-target-ip-10-0-142-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:29:36Z"
    - latency: 2.154153ms
      message: 'network-check-target-ip-10-0-142-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:55:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: a4e53c03-2eaf-4721-8455-56631451fe61
    resourceVersion: "32300"
    uid: 79de5c70-b40e-4420-8b28-940c5b612929
  spec:
    sourcePod: network-check-source-685456655f-nnf7c
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:01:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.197071ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:37:36Z"
    - latency: 1.694824ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:37:36Z"
    - latency: 827.607µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:36:36Z"
    - latency: 1.672773ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:36:36Z"
    - latency: 974.44µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:35:36Z"
    - latency: 2.11492ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:35:36Z"
    - latency: 1.007687ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:34:36Z"
    - latency: 1.592096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:34:36Z"
    - latency: 845.978µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:33:36Z"
    - latency: 1.755286ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:33:36Z"
kind: List
metadata:
  resourceVersion: ""