apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T19:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-77-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-77.ec2.internal
      uid: 120e7cec-d97e-4b4d-b9a1-83efa13b433c
    resourceVersion: "44902"
    uid: 6d0dcf6c-1133-429c-a967-2c320394c801
  spec:
    sourcePod: network-check-source-7f44b6dd87-x4mb5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T19:42:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 972.713µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:03:00Z"
    - latency: 841.317µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:02:00Z"
    - latency: 890.926µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:01:00Z"
    - latency: 1.469668ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:00:00Z"
    - latency: 1.107164ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:59:00Z"
    - latency: 1.012215ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:58:00Z"
    - latency: 1.139781ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:57:00Z"
    - latency: 818.733µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:56:00Z"
    - latency: 1.065132ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:55:00Z"
    - latency: 951.651µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:54:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T19:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-77-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-77.ec2.internal
      uid: 120e7cec-d97e-4b4d-b9a1-83efa13b433c
    resourceVersion: "46997"
    uid: db9e9276-b670-4a7c-8b88-9aa6195e5e2c
  spec:
    sourcePod: network-check-source-7f44b6dd87-x4mb5
    targetEndpoint: a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T19:41:00Z"
      message: 'load-balancer-api-external: tcp connection to a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.880118ms
      message: 'load-balancer-api-external: tcp connection to a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:05:00Z"
    - latency: 10.285264ms
      message: 'load-balancer-api-external: resolved host name a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:05:00Z"
    - latency: 3.346401ms
      message: 'load-balancer-api-external: tcp connection to a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:04:00Z"
    - latency: 8.026074ms
      message: 'load-balancer-api-external: resolved host name a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:04:00Z"
    - latency: 4.962175ms
      message: 'load-balancer-api-external: tcp connection to a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:03:00Z"
    - latency: 9.670963ms
      message: 'load-balancer-api-external: resolved host name a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:03:00Z"
    - latency: 3.298385ms
      message: 'load-balancer-api-external: tcp connection to a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:02:00Z"
    - latency: 8.537867ms
      message: 'load-balancer-api-external: resolved host name a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:02:00Z"
    - latency: 4.596663ms
      message: 'load-balancer-api-external: tcp connection to a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:01:00Z"
    - latency: 10.229591ms
      message: 'load-balancer-api-external: resolved host name a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:01:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T19:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-77-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-77.ec2.internal
      uid: 120e7cec-d97e-4b4d-b9a1-83efa13b433c
    resourceVersion: "46998"
    uid: 7fa54b50-a582-48a6-b290-d6beb14aead5
  spec:
    sourcePod: network-check-source-7f44b6dd87-x4mb5
    targetEndpoint: a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T19:41:00Z"
      message: 'load-balancer-api-internal: tcp connection to a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.407563ms
      message: 'load-balancer-api-internal: tcp connection to a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:05:00Z"
    - latency: 10.318194ms
      message: 'load-balancer-api-internal: resolved host name a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:05:00Z"
    - latency: 4.319772ms
      message: 'load-balancer-api-internal: tcp connection to a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:04:00Z"
    - latency: 7.9565ms
      message: 'load-balancer-api-internal: resolved host name a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:04:00Z"
    - latency: 3.658352ms
      message: 'load-balancer-api-internal: tcp connection to a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:03:00Z"
    - latency: 9.594361ms
      message: 'load-balancer-api-internal: resolved host name a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:03:00Z"
    - latency: 3.250642ms
      message: 'load-balancer-api-internal: tcp connection to a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:02:00Z"
    - latency: 8.59775ms
      message: 'load-balancer-api-internal: resolved host name a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:02:00Z"
    - latency: 4.549424ms
      message: 'load-balancer-api-internal: tcp connection to a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:01:00Z"
    - latency: 10.118244ms
      message: 'load-balancer-api-internal: resolved host name a1d922c35d9b74366a7a734fce49e5a2-a4936ffe9e659269.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:01:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T19:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-77-to-network-check-target-ip-10-0-131-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-77.ec2.internal
      uid: 120e7cec-d97e-4b4d-b9a1-83efa13b433c
    resourceVersion: "44901"
    uid: e9897ca8-8931-494f-819a-bc1f88d7f7ef
  spec:
    sourcePod: network-check-source-7f44b6dd87-x4mb5
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T19:42:00Z"
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.990275ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:03:00Z"
    - latency: 1.867517ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:02:00Z"
    - latency: 1.850004ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:01:00Z"
    - latency: 1.869926ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:00:00Z"
    - latency: 1.785376ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:59:00Z"
    - latency: 1.658358ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:58:00Z"
    - latency: 1.765002ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:57:00Z"
    - latency: 1.865473ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:56:00Z"
    - latency: 1.856999ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:55:00Z"
    - latency: 2.027956ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:54:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T19:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-77-to-network-check-target-ip-10-0-139-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-77.ec2.internal
      uid: 120e7cec-d97e-4b4d-b9a1-83efa13b433c
    resourceVersion: "44900"
    uid: bbef68a4-14ed-4752-bc54-6374fba3a88f
  spec:
    sourcePod: network-check-source-7f44b6dd87-x4mb5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T19:42:00Z"
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.144034ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:03:00Z"
    - latency: 1.840317ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:02:00Z"
    - latency: 2.168002ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:01:00Z"
    - latency: 2.077091ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:00:00Z"
    - latency: 1.963375ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:59:00Z"
    - latency: 2.012757ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:58:00Z"
    - latency: 1.971471ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:57:00Z"
    - latency: 2.09672ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:56:00Z"
    - latency: 2.064272ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:55:00Z"
    - latency: 2.38375ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:54:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T19:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-77-to-network-check-target-ip-10-0-143-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-77.ec2.internal
      uid: 120e7cec-d97e-4b4d-b9a1-83efa13b433c
    resourceVersion: "44898"
    uid: b96a5b65-1171-49e0-aa3b-f8a27048ddc4
  spec:
    sourcePod: network-check-source-7f44b6dd87-x4mb5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T19:42:00Z"
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.22µs
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:03:00Z"
    - latency: 717.932µs
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:02:00Z"
    - latency: 810.792µs
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:01:00Z"
    - latency: 817.953µs
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:00:00Z"
    - latency: 824.942µs
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:59:00Z"
    - latency: 1.066826ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:58:00Z"
    - latency: 717.604µs
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:57:00Z"
    - latency: 731.419µs
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:56:00Z"
    - latency: 1.097536ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:55:00Z"
    - latency: 1.28579ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T19:54:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T19:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-77-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-77.ec2.internal
      uid: 120e7cec-d97e-4b4d-b9a1-83efa13b433c
    resourceVersion: "46996"
    uid: 99fd97e7-8c88-4be3-b983-2ecc15195974
  spec:
    sourcePod: network-check-source-7f44b6dd87-x4mb5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T19:41:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 784.396µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:05:00Z"
    - latency: 1.723679ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:05:00Z"
    - latency: 837.444µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:04:00Z"
    - latency: 1.558944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:04:00Z"
    - latency: 837.081µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:03:00Z"
    - latency: 1.544262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:03:00Z"
    - latency: 1.052898ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:02:00Z"
    - latency: 1.702222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:02:00Z"
    - latency: 797.036µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T20:01:00Z"
    - latency: 1.685553ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T20:01:00Z"
kind: List
metadata:
  resourceVersion: ""