apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T22:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-197-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-197.ec2.internal
      uid: 67bcc1d5-a394-4d37-8ee4-140d2230c24b
    resourceVersion: "70005"
    uid: 122e96ac-08d2-4487-8193-0ff07c266b6c
  spec:
    sourcePod: network-check-source-65bdbbff45-br2c4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T22:09: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.163782ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:51:36Z"
    - latency: 1.275741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:50:36Z"
    - latency: 1.351478ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:49:36Z"
    - latency: 1.098211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:48:36Z"
    - latency: 1.175271ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:47:36Z"
    - latency: 1.000755ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:46:36Z"
    - latency: 763.389µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:45:36Z"
    - latency: 1.470668ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:44:36Z"
    - latency: 1.506479ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:43:36Z"
    - latency: 1.184455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:42:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T22:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-197-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-197.ec2.internal
      uid: 67bcc1d5-a394-4d37-8ee4-140d2230c24b
    resourceVersion: "75291"
    uid: a6e5d992-6fe0-4618-8c69-f4f2fbf279ba
  spec:
    sourcePod: network-check-source-65bdbbff45-br2c4
    targetEndpoint: aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T22:08:36Z"
      message: 'load-balancer-api-external: tcp connection to aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.654261ms
      message: 'load-balancer-api-external: tcp connection to aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:56:36Z"
    - latency: 8.472027ms
      message: 'load-balancer-api-external: resolved host name aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:56:36Z"
    - latency: 5.042884ms
      message: 'load-balancer-api-external: tcp connection to aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:55:36Z"
    - latency: 7.467193ms
      message: 'load-balancer-api-external: resolved host name aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:55:36Z"
    - latency: 5.62198ms
      message: 'load-balancer-api-external: tcp connection to aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:54:36Z"
    - latency: 7.026294ms
      message: 'load-balancer-api-external: resolved host name aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:54:36Z"
    - latency: 3.370038ms
      message: 'load-balancer-api-external: tcp connection to aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:53:36Z"
    - latency: 6.626512ms
      message: 'load-balancer-api-external: resolved host name aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:53:36Z"
    - latency: 3.66051ms
      message: 'load-balancer-api-external: tcp connection to aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:52:36Z"
    - latency: 6.709978ms
      message: 'load-balancer-api-external: resolved host name aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:52:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T22:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-197-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-197.ec2.internal
      uid: 67bcc1d5-a394-4d37-8ee4-140d2230c24b
    resourceVersion: "75292"
    uid: 8feda0ea-4751-4718-b9f7-8d89af3cf7ff
  spec:
    sourcePod: network-check-source-65bdbbff45-br2c4
    targetEndpoint: aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T22:08:36Z"
      message: 'load-balancer-api-internal: tcp connection to aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.308882ms
      message: 'load-balancer-api-internal: tcp connection to aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:56:36Z"
    - latency: 8.436356ms
      message: 'load-balancer-api-internal: resolved host name aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:56:36Z"
    - latency: 4.123995ms
      message: 'load-balancer-api-internal: tcp connection to aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:55:36Z"
    - latency: 7.43218ms
      message: 'load-balancer-api-internal: resolved host name aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:55:36Z"
    - latency: 5.478435ms
      message: 'load-balancer-api-internal: tcp connection to aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:54:36Z"
    - latency: 6.949753ms
      message: 'load-balancer-api-internal: resolved host name aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:54:36Z"
    - latency: 5.247819ms
      message: 'load-balancer-api-internal: tcp connection to aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:53:36Z"
    - latency: 6.570005ms
      message: 'load-balancer-api-internal: resolved host name aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:53:36Z"
    - latency: 4.411373ms
      message: 'load-balancer-api-internal: tcp connection to aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:52:36Z"
    - latency: 6.660317ms
      message: 'load-balancer-api-internal: resolved host name aebe771b1cbd140688342dcfda1d9508-310bf7d642b98222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:52:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T22:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-197-to-network-check-target-ip-10-0-130-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-197.ec2.internal
      uid: 67bcc1d5-a394-4d37-8ee4-140d2230c24b
    resourceVersion: "70003"
    uid: cecfffdc-04f4-4e3b-b075-f89575ec5df3
  spec:
    sourcePod: network-check-source-65bdbbff45-br2c4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T22:09:36Z"
      message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.972784ms
      message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:51:36Z"
    - latency: 1.68621ms
      message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:50:36Z"
    - latency: 1.92787ms
      message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:49:36Z"
    - latency: 1.761439ms
      message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:48:36Z"
    - latency: 1.980262ms
      message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:47:36Z"
    - latency: 2.138064ms
      message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:46:36Z"
    - latency: 1.777753ms
      message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:45:36Z"
    - latency: 1.706287ms
      message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:44:36Z"
    - latency: 2.100372ms
      message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:43:36Z"
    - latency: 1.988021ms
      message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:42:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T22:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-197-to-network-check-target-ip-10-0-139-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-197.ec2.internal
      uid: 67bcc1d5-a394-4d37-8ee4-140d2230c24b
    resourceVersion: "70004"
    uid: b256a086-1dc5-447a-9a20-2bccf5b550b8
  spec:
    sourcePod: network-check-source-65bdbbff45-br2c4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T22:09:36Z"
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.337814ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:51:36Z"
    - latency: 1.990207ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:50:36Z"
    - latency: 2.401931ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:49:36Z"
    - latency: 2.30276ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:48:36Z"
    - latency: 2.350982ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:47:36Z"
    - latency: 2.152279ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:46:36Z"
    - latency: 2.129826ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:45:36Z"
    - latency: 2.387158ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:44:36Z"
    - latency: 3.049179ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:43:36Z"
    - latency: 2.032898ms
      message: 'network-check-target-ip-10-0-139-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:42:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T22:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-197-to-network-check-target-ip-10-0-140-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-197.ec2.internal
      uid: 67bcc1d5-a394-4d37-8ee4-140d2230c24b
    resourceVersion: "70002"
    uid: 76a87af5-e887-48fc-937a-d491054c66e9
  spec:
    sourcePod: network-check-source-65bdbbff45-br2c4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T22:09:36Z"
      message: 'network-check-target-ip-10-0-140-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 790.779µs
      message: 'network-check-target-ip-10-0-140-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:51:36Z"
    - latency: 1.719116ms
      message: 'network-check-target-ip-10-0-140-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:50:36Z"
    - latency: 1.549533ms
      message: 'network-check-target-ip-10-0-140-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:49:36Z"
    - latency: 742.851µs
      message: 'network-check-target-ip-10-0-140-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:48:36Z"
    - latency: 1.553971ms
      message: 'network-check-target-ip-10-0-140-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:47:36Z"
    - latency: 1.351096ms
      message: 'network-check-target-ip-10-0-140-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:46:36Z"
    - latency: 863.158µs
      message: 'network-check-target-ip-10-0-140-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:45:36Z"
    - latency: 1.48443ms
      message: 'network-check-target-ip-10-0-140-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:44:36Z"
    - latency: 784.945µs
      message: 'network-check-target-ip-10-0-140-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:43:36Z"
    - latency: 959.474µs
      message: 'network-check-target-ip-10-0-140-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:42:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T22:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-197-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-197.ec2.internal
      uid: 67bcc1d5-a394-4d37-8ee4-140d2230c24b
    resourceVersion: "75290"
    uid: 5ed6efb7-9163-4865-8d10-7e90d637c0c1
  spec:
    sourcePod: network-check-source-65bdbbff45-br2c4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T22:08:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 762.335µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:56:36Z"
    - latency: 1.736344ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:56:36Z"
    - latency: 1.236179ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:55:36Z"
    - latency: 2.077229ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:55:36Z"
    - latency: 1.115376ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:54:36Z"
    - latency: 1.662784ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:54:36Z"
    - latency: 1.246393ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:53:36Z"
    - latency: 1.670041ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:53:36Z"
    - latency: 794.61µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T22:52:36Z"
    - latency: 1.699707ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T22:52:36Z"
kind: List
metadata:
  resourceVersion: ""