apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:24:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-231-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-231.ec2.internal
      uid: 6f8526b7-37f3-41b5-9405-8b135c208a0c
    resourceVersion: "48241"
    uid: 5228afb9-5a80-4cfd-9dd6-22a6cb9c8d30
  spec:
    sourcePod: network-check-source-989f8b8dc-zxkjb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:31:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.196857ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:12Z"
    - latency: 1.137709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:12Z"
    - latency: 946.529µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:12Z"
    - latency: 1.116079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:49:12Z"
    - latency: 1.055337ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:48:12Z"
    - latency: 1.612338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:47:12Z"
    - latency: 1.014312ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:46:12Z"
    - latency: 849.211µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:45:12Z"
    - latency: 1.047784ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:44:12Z"
    - latency: 898.748µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:43:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:24:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-231-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-231.ec2.internal
      uid: 6f8526b7-37f3-41b5-9405-8b135c208a0c
    resourceVersion: "50455"
    uid: 955d8df1-09e1-4e69-b245-e1a28cdd0790
  spec:
    sourcePod: network-check-source-989f8b8dc-zxkjb
    targetEndpoint: a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:30:12Z"
      message: 'load-balancer-api-external: tcp connection to a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.788362ms
      message: 'load-balancer-api-external: tcp connection to a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:12Z"
    - latency: 8.711088ms
      message: 'load-balancer-api-external: resolved host name a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:54:12Z"
    - latency: 4.573569ms
      message: 'load-balancer-api-external: tcp connection to a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:12Z"
    - latency: 7.336132ms
      message: 'load-balancer-api-external: resolved host name a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:53:12Z"
    - latency: 6.599891ms
      message: 'load-balancer-api-external: tcp connection to a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:12Z"
    - latency: 6.970795ms
      message: 'load-balancer-api-external: resolved host name a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:52:12Z"
    - latency: 5.382327ms
      message: 'load-balancer-api-external: tcp connection to a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:12Z"
    - latency: 7.26633ms
      message: 'load-balancer-api-external: resolved host name a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:51:12Z"
    - latency: 5.234712ms
      message: 'load-balancer-api-external: tcp connection to a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:12Z"
    - latency: 6.995884ms
      message: 'load-balancer-api-external: resolved host name a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:50:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:24:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-231-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-231.ec2.internal
      uid: 6f8526b7-37f3-41b5-9405-8b135c208a0c
    resourceVersion: "50454"
    uid: 4ec1d0e4-9e36-49c6-bb6a-aec725612209
  spec:
    sourcePod: network-check-source-989f8b8dc-zxkjb
    targetEndpoint: a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:30:12Z"
      message: 'load-balancer-api-internal: tcp connection to a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.61716ms
      message: 'load-balancer-api-internal: tcp connection to a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:12Z"
    - latency: 8.792094ms
      message: 'load-balancer-api-internal: resolved host name a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:54:12Z"
    - latency: 5.017083ms
      message: 'load-balancer-api-internal: tcp connection to a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:12Z"
    - latency: 7.434839ms
      message: 'load-balancer-api-internal: resolved host name a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:53:12Z"
    - latency: 4.591476ms
      message: 'load-balancer-api-internal: tcp connection to a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:12Z"
    - latency: 7.042167ms
      message: 'load-balancer-api-internal: resolved host name a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:52:12Z"
    - latency: 4.766125ms
      message: 'load-balancer-api-internal: tcp connection to a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:12Z"
    - latency: 7.310139ms
      message: 'load-balancer-api-internal: resolved host name a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:51:12Z"
    - latency: 5.378882ms
      message: 'load-balancer-api-internal: tcp connection to a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:12Z"
    - latency: 7.055766ms
      message: 'load-balancer-api-internal: resolved host name a1f7a6ee3c9e44e218b27a5d92eae6d0-d07bc85d9342a263.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:50:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:24:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-231-to-network-check-target-ip-10-0-128-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-231.ec2.internal
      uid: 6f8526b7-37f3-41b5-9405-8b135c208a0c
    resourceVersion: "48240"
    uid: da57b7eb-2c9e-4915-932a-de36f9db2ad9
  spec:
    sourcePod: network-check-source-989f8b8dc-zxkjb
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:31:12Z"
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.568625ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:12Z"
    - latency: 2.588349ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:12Z"
    - latency: 2.208275ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:12Z"
    - latency: 2.338165ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:49:12Z"
    - latency: 2.620374ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:48:12Z"
    - latency: 2.307667ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:47:12Z"
    - latency: 2.288975ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:46:12Z"
    - latency: 2.432445ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:45:12Z"
    - latency: 2.35642ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:44:12Z"
    - latency: 2.869632ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:43:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:24:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-231-to-network-check-target-ip-10-0-133-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-231.ec2.internal
      uid: 6f8526b7-37f3-41b5-9405-8b135c208a0c
    resourceVersion: "48239"
    uid: b4b28fe2-c2ac-4ebf-9a23-22a0ed47fbd8
  spec:
    sourcePod: network-check-source-989f8b8dc-zxkjb
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:31:12Z"
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.134693ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:12Z"
    - latency: 2.314781ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:12Z"
    - latency: 2.141131ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:12Z"
    - latency: 2.327755ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:49:12Z"
    - latency: 2.311283ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:48:12Z"
    - latency: 2.432447ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:47:12Z"
    - latency: 2.235792ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:46:12Z"
    - latency: 2.001477ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:45:12Z"
    - latency: 2.22324ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:44:12Z"
    - latency: 2.725405ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:43:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:24:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-231-to-network-check-target-ip-10-0-133-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-231.ec2.internal
      uid: 6f8526b7-37f3-41b5-9405-8b135c208a0c
    resourceVersion: "48238"
    uid: 2d02f40e-d71b-4926-8204-a99256330efc
  spec:
    sourcePod: network-check-source-989f8b8dc-zxkjb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:31:12Z"
      message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 938.784µs
      message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:12Z"
    - latency: 926.073µs
      message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:12Z"
    - latency: 895.323µs
      message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:12Z"
    - latency: 1.122615ms
      message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:49:12Z"
    - latency: 1.487301ms
      message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:48:12Z"
    - latency: 978.729µs
      message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:47:12Z"
    - latency: 1.030262ms
      message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:46:12Z"
    - latency: 1.068545ms
      message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:45:12Z"
    - latency: 1.077253ms
      message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:44:12Z"
    - latency: 1.112637ms
      message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:43:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:24:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-231-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-231.ec2.internal
      uid: 6f8526b7-37f3-41b5-9405-8b135c208a0c
    resourceVersion: "50453"
    uid: f93b51dd-3bac-4116-ae63-d8ba872816d0
  spec:
    sourcePod: network-check-source-989f8b8dc-zxkjb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:30:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 855.731µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:54:12Z"
    - latency: 1.777771ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:54:12Z"
    - latency: 1.134605ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:53:12Z"
    - latency: 1.762945ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:53:12Z"
    - latency: 910.098µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:52:12Z"
    - latency: 1.741422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:52:12Z"
    - latency: 927.503µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:51:12Z"
    - latency: 1.650967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:51:12Z"
    - latency: 941.247µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T17:50:12Z"
    - latency: 1.712588ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T17:50:12Z"
kind: List
metadata:
  resourceVersion: ""