apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:02:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-94-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-94.ec2.internal
      uid: 9455ad02-581b-4c2e-b7d2-f334ac3f6f70
    resourceVersion: "114203"
    uid: f6ceb094-68fa-4f49-a51d-541bea7ac770
  spec:
    sourcePod: network-check-source-6f78d59f99-7ncwj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:09:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.415251ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:51:51Z"
    - latency: 1.187525ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:50:51Z"
    - latency: 1.213881ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:49:51Z"
    - latency: 1.173153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:48:51Z"
    - latency: 1.976649ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:47:51Z"
    - latency: 1.312826ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:51Z"
    - latency: 1.293458ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:51Z"
    - latency: 1.095674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:51Z"
    - latency: 1.180278ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:51Z"
    - latency: 1.299846ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:02:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-94-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-94.ec2.internal
      uid: 9455ad02-581b-4c2e-b7d2-f334ac3f6f70
    resourceVersion: "113623"
    uid: 4d74d2ff-3e9f-455d-9120-0e866dd0a1d8
  spec:
    sourcePod: network-check-source-6f78d59f99-7ncwj
    targetEndpoint: a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:08:51Z"
      message: 'load-balancer-api-external: tcp connection to a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.446024ms
      message: 'load-balancer-api-external: tcp connection to a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:50:51Z"
    - latency: 7.053965ms
      message: 'load-balancer-api-external: resolved host name a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:50:51Z"
    - latency: 18.201167ms
      message: 'load-balancer-api-external: tcp connection to a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:49:51Z"
    - latency: 8.059741ms
      message: 'load-balancer-api-external: resolved host name a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:49:51Z"
    - latency: 16.275375ms
      message: 'load-balancer-api-external: tcp connection to a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:48:51Z"
    - latency: 11.399975ms
      message: 'load-balancer-api-external: resolved host name a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:48:51Z"
    - latency: 16.788987ms
      message: 'load-balancer-api-external: tcp connection to a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:47:51Z"
    - latency: 13.094693ms
      message: 'load-balancer-api-external: resolved host name a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:47:51Z"
    - latency: 15.700366ms
      message: 'load-balancer-api-external: tcp connection to a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:51Z"
    - latency: 7.130688ms
      message: 'load-balancer-api-external: resolved host name a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:46:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:02:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-94-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-94.ec2.internal
      uid: 9455ad02-581b-4c2e-b7d2-f334ac3f6f70
    resourceVersion: "113624"
    uid: e2690cef-1303-4a41-9ab6-76c9f60c444b
  spec:
    sourcePod: network-check-source-6f78d59f99-7ncwj
    targetEndpoint: a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:08:51Z"
      message: 'load-balancer-api-internal: tcp connection to a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.756585ms
      message: 'load-balancer-api-internal: tcp connection to a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:50:51Z"
    - latency: 7.021441ms
      message: 'load-balancer-api-internal: resolved host name a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:50:51Z"
    - latency: 18.447294ms
      message: 'load-balancer-api-internal: tcp connection to a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:49:51Z"
    - latency: 8.028767ms
      message: 'load-balancer-api-internal: resolved host name a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:49:51Z"
    - latency: 16.818517ms
      message: 'load-balancer-api-internal: tcp connection to a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:48:51Z"
    - latency: 11.374945ms
      message: 'load-balancer-api-internal: resolved host name a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:48:51Z"
    - latency: 16.199832ms
      message: 'load-balancer-api-internal: tcp connection to a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:47:51Z"
    - latency: 13.068521ms
      message: 'load-balancer-api-internal: resolved host name a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:47:51Z"
    - latency: 17.462148ms
      message: 'load-balancer-api-internal: tcp connection to a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:51Z"
    - latency: 7.093713ms
      message: 'load-balancer-api-internal: resolved host name a12840c7323dd4f5e8ca7b6f319d95c3-aafe87cc6257ca1d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:46:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:22:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-94-to-network-check-target-ip-10-0-133-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-94.ec2.internal
      uid: 9455ad02-581b-4c2e-b7d2-f334ac3f6f70
    resourceVersion: "113465"
    uid: a243abf9-18a5-471c-b568-609fbf12cafe
  spec:
    sourcePod: network-check-source-6f78d59f99-7ncwj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:29:40Z"
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.385378ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:50:40Z"
    - latency: 4.335369ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:49:40Z"
    - latency: 4.646506ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:48:40Z"
    - latency: 4.936017ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:47:40Z"
    - latency: 14.953385ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:40Z"
    - latency: 4.49212ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:40Z"
    - latency: 4.074004ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:40Z"
    - latency: 3.816273ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:40Z"
    - latency: 4.230422ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:40Z"
    - latency: 4.611555ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:41:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:02:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-94-to-network-check-target-ip-10-0-141-106
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-94.ec2.internal
      uid: 9455ad02-581b-4c2e-b7d2-f334ac3f6f70
    resourceVersion: "114202"
    uid: 35ffd59a-a329-47cd-9d17-880bc687ada4
  spec:
    sourcePod: network-check-source-6f78d59f99-7ncwj
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:09:51Z"
      message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.355743ms
      message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:51:51Z"
    - latency: 2.478175ms
      message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:50:51Z"
    - latency: 2.381697ms
      message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:49:51Z"
    - latency: 2.218941ms
      message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:48:51Z"
    - latency: 4.180414ms
      message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:47:51Z"
    - latency: 2.384051ms
      message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:51Z"
    - latency: 2.29504ms
      message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:51Z"
    - latency: 2.451474ms
      message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:51Z"
    - latency: 2.098808ms
      message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:51Z"
    - latency: 2.432181ms
      message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:02:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-94-to-network-check-target-ip-10-0-143-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-94.ec2.internal
      uid: 9455ad02-581b-4c2e-b7d2-f334ac3f6f70
    resourceVersion: "114201"
    uid: 2892c870-3679-4eda-8af0-2261d9d8ccb9
  spec:
    sourcePod: network-check-source-6f78d59f99-7ncwj
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:09:51Z"
      message: 'network-check-target-ip-10-0-143-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.385479ms
      message: 'network-check-target-ip-10-0-143-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:51:51Z"
    - latency: 1.747832ms
      message: 'network-check-target-ip-10-0-143-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:50:51Z"
    - latency: 1.42777ms
      message: 'network-check-target-ip-10-0-143-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:49:51Z"
    - latency: 1.577032ms
      message: 'network-check-target-ip-10-0-143-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:48:51Z"
    - latency: 2.503763ms
      message: 'network-check-target-ip-10-0-143-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:47:51Z"
    - latency: 874.421µs
      message: 'network-check-target-ip-10-0-143-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:51Z"
    - latency: 1.1223ms
      message: 'network-check-target-ip-10-0-143-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:51Z"
    - latency: 1.060413ms
      message: 'network-check-target-ip-10-0-143-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:51Z"
    - latency: 937.947µs
      message: 'network-check-target-ip-10-0-143-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:51Z"
    - latency: 1.767188ms
      message: 'network-check-target-ip-10-0-143-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:02:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-94-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-94.ec2.internal
      uid: 9455ad02-581b-4c2e-b7d2-f334ac3f6f70
    resourceVersion: "113622"
    uid: fc6556dc-ada2-49ef-a2f8-269fcff797ec
  spec:
    sourcePod: network-check-source-6f78d59f99-7ncwj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:08:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.266138ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:50:51Z"
    - latency: 2.04768ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:50:51Z"
    - latency: 3.859744ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:49:51Z"
    - latency: 2.116296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:49:51Z"
    - latency: 1.078647ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:48:51Z"
    - latency: 2.014281ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:48:51Z"
    - latency: 969.178µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:47:51Z"
    - latency: 4.37616ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:47:51Z"
    - latency: 923.063µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:51Z"
    - latency: 2.410454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:46:51Z"
kind: List
metadata:
  resourceVersion: ""