apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:06:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-144.ec2.internal
      uid: 68a865be-b1fc-4fdc-a9f4-4ca53e15d411
    resourceVersion: "53808"
    uid: 088fa017-b0cc-43db-904d-fb8627e0fc48
  spec:
    sourcePod: network-check-source-6f8b768455-49png
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:13:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.114789ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:34:02Z"
    - latency: 916.991µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:33:02Z"
    - latency: 1.405873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:32:02Z"
    - latency: 1.38032ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:31:02Z"
    - latency: 834.653µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:30:02Z"
    - latency: 1.22899ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:29:02Z"
    - latency: 777.004µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:28:02Z"
    - latency: 944.944µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:27:02Z"
    - latency: 916.612µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:26:02Z"
    - latency: 996.458µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:25:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:06:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-144.ec2.internal
      uid: 68a865be-b1fc-4fdc-a9f4-4ca53e15d411
    resourceVersion: "55460"
    uid: 11869267-2e50-4d0f-8bcc-920680a45997
  spec:
    sourcePod: network-check-source-6f8b768455-49png
    targetEndpoint: af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:12:03Z"
      message: 'load-balancer-api-external: tcp connection to af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.079705ms
      message: 'load-balancer-api-external: tcp connection to af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:36:03Z"
    - latency: 7.935387ms
      message: 'load-balancer-api-external: resolved host name af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:36:02Z"
    - latency: 4.140168ms
      message: 'load-balancer-api-external: tcp connection to af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:35:03Z"
    - latency: 8.417631ms
      message: 'load-balancer-api-external: resolved host name af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:35:02Z"
    - latency: 3.851173ms
      message: 'load-balancer-api-external: tcp connection to af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:34:03Z"
    - latency: 6.794809ms
      message: 'load-balancer-api-external: resolved host name af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:34:02Z"
    - latency: 5.462163ms
      message: 'load-balancer-api-external: tcp connection to af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:33:03Z"
    - latency: 8.291866ms
      message: 'load-balancer-api-external: resolved host name af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:33:02Z"
    - latency: 5.383366ms
      message: 'load-balancer-api-external: tcp connection to af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:32:03Z"
    - latency: 7.477443ms
      message: 'load-balancer-api-external: resolved host name af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:06:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-144.ec2.internal
      uid: 68a865be-b1fc-4fdc-a9f4-4ca53e15d411
    resourceVersion: "55461"
    uid: aa31c12c-e54b-46aa-a03b-fd283e38ae92
  spec:
    sourcePod: network-check-source-6f8b768455-49png
    targetEndpoint: af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:12:03Z"
      message: 'load-balancer-api-internal: tcp connection to af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.092622ms
      message: 'load-balancer-api-internal: tcp connection to af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:36:03Z"
    - latency: 7.906994ms
      message: 'load-balancer-api-internal: resolved host name af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:36:02Z"
    - latency: 4.129941ms
      message: 'load-balancer-api-internal: tcp connection to af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:35:03Z"
    - latency: 8.340777ms
      message: 'load-balancer-api-internal: resolved host name af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:35:02Z"
    - latency: 4.915345ms
      message: 'load-balancer-api-internal: tcp connection to af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:34:03Z"
    - latency: 6.7518ms
      message: 'load-balancer-api-internal: resolved host name af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:34:02Z"
    - latency: 5.16979ms
      message: 'load-balancer-api-internal: tcp connection to af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:33:03Z"
    - latency: 8.315093ms
      message: 'load-balancer-api-internal: resolved host name af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:33:02Z"
    - latency: 5.359847ms
      message: 'load-balancer-api-internal: tcp connection to af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:32:03Z"
    - latency: 7.438469ms
      message: 'load-balancer-api-internal: resolved host name af2acb1ec19fe4d0fb81690c4c5a12df-c2522f352c203d80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:06:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-144-to-network-check-target-ip-10-0-130-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-144.ec2.internal
      uid: 68a865be-b1fc-4fdc-a9f4-4ca53e15d411
    resourceVersion: "53807"
    uid: 29edee58-2a9e-4f37-9132-1a5489feb1b6
  spec:
    sourcePod: network-check-source-6f8b768455-49png
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:13:02Z"
      message: 'network-check-target-ip-10-0-130-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.429343ms
      message: 'network-check-target-ip-10-0-130-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:34:02Z"
    - latency: 2.26429ms
      message: 'network-check-target-ip-10-0-130-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:33:02Z"
    - latency: 2.299091ms
      message: 'network-check-target-ip-10-0-130-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:32:02Z"
    - latency: 2.494981ms
      message: 'network-check-target-ip-10-0-130-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:31:02Z"
    - latency: 2.171844ms
      message: 'network-check-target-ip-10-0-130-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:30:02Z"
    - latency: 2.041069ms
      message: 'network-check-target-ip-10-0-130-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:29:02Z"
    - latency: 1.999566ms
      message: 'network-check-target-ip-10-0-130-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:28:02Z"
    - latency: 2.124751ms
      message: 'network-check-target-ip-10-0-130-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:27:02Z"
    - latency: 2.576773ms
      message: 'network-check-target-ip-10-0-130-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:26:02Z"
    - latency: 2.269107ms
      message: 'network-check-target-ip-10-0-130-67: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:25:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:06:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-144-to-network-check-target-ip-10-0-134-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-144.ec2.internal
      uid: 68a865be-b1fc-4fdc-a9f4-4ca53e15d411
    resourceVersion: "53805"
    uid: 06d02b77-6b1e-41ba-82cc-6fce097ed45f
  spec:
    sourcePod: network-check-source-6f8b768455-49png
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:13:02Z"
      message: 'network-check-target-ip-10-0-134-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.291µs
      message: 'network-check-target-ip-10-0-134-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:34:02Z"
    - latency: 972.381µs
      message: 'network-check-target-ip-10-0-134-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:33:02Z"
    - latency: 877.301µs
      message: 'network-check-target-ip-10-0-134-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:32:02Z"
    - latency: 1.004882ms
      message: 'network-check-target-ip-10-0-134-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:31:02Z"
    - latency: 864.012µs
      message: 'network-check-target-ip-10-0-134-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:30:02Z"
    - latency: 1.059121ms
      message: 'network-check-target-ip-10-0-134-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:29:02Z"
    - latency: 798.876µs
      message: 'network-check-target-ip-10-0-134-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:28:02Z"
    - latency: 818.758µs
      message: 'network-check-target-ip-10-0-134-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:27:02Z"
    - latency: 923.687µs
      message: 'network-check-target-ip-10-0-134-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:26:02Z"
    - latency: 933.978µs
      message: 'network-check-target-ip-10-0-134-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:25:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:06:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-144-to-network-check-target-ip-10-0-139-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-144.ec2.internal
      uid: 68a865be-b1fc-4fdc-a9f4-4ca53e15d411
    resourceVersion: "53806"
    uid: 6a8f591b-b0dd-4750-b89c-c4c01b6d85c5
  spec:
    sourcePod: network-check-source-6f8b768455-49png
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:13:02Z"
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.131331ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:34:02Z"
    - latency: 2.154682ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:33:02Z"
    - latency: 2.593193ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:32:02Z"
    - latency: 2.183086ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:31:02Z"
    - latency: 1.897299ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:30:02Z"
    - latency: 1.815688ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:29:02Z"
    - latency: 1.942986ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:28:02Z"
    - latency: 1.99208ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:27:02Z"
    - latency: 2.264878ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:26:02Z"
    - latency: 1.836218ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:25:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:06:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-144.ec2.internal
      uid: 68a865be-b1fc-4fdc-a9f4-4ca53e15d411
    resourceVersion: "55458"
    uid: 25f7e988-81c7-4c9c-b8d4-5450015b1e99
  spec:
    sourcePod: network-check-source-6f8b768455-49png
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:12:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.120223ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:36:02Z"
    - latency: 1.824249ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:36:02Z"
    - latency: 1.079826ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:35:02Z"
    - latency: 1.744958ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:35:02Z"
    - latency: 858.708µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:34:02Z"
    - latency: 1.775463ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:34:02Z"
    - latency: 1.311211ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:33:02Z"
    - latency: 1.868396ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:33:02Z"
    - latency: 940.035µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:32:02Z"
    - latency: 1.932186ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:32:02Z"
kind: List
metadata:
  resourceVersion: ""