apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 7c8cb3c9-fa3a-4473-9317-de888df601b5
    resourceVersion: "23275"
    uid: 783246c5-6506-450c-bbc3-28fab44f3380
  spec:
    sourcePod: network-check-source-65bdbbff45-5dmjq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:56:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 846.188µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:10:37Z"
    - latency: 1.065182ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:09:37Z"
    - latency: 949.148µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:08:37Z"
    - latency: 992.864µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:07:37Z"
    - latency: 1.001829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:06:37Z"
    - latency: 950.398µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:05:37Z"
    - latency: 950.028µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:04:37Z"
    - latency: 1.052097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:03:37Z"
    - latency: 866.409µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:02:37Z"
    - latency: 973.671µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:01:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 7c8cb3c9-fa3a-4473-9317-de888df601b5
    resourceVersion: "21798"
    uid: ee70ccc3-bfb6-4e56-8aef-50eaa44ee8c5
  spec:
    sourcePod: network-check-source-65bdbbff45-5dmjq
    targetEndpoint: ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:55:37Z"
      message: 'load-balancer-api-external: tcp connection to ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.235219ms
      message: 'load-balancer-api-external: tcp connection to ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:07:37Z"
    - latency: 10.867027ms
      message: 'load-balancer-api-external: resolved host name ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:07:37Z"
    - latency: 4.678ms
      message: 'load-balancer-api-external: tcp connection to ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:06:37Z"
    - latency: 8.778925ms
      message: 'load-balancer-api-external: resolved host name ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:06:37Z"
    - latency: 5.460116ms
      message: 'load-balancer-api-external: tcp connection to ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:05:37Z"
    - latency: 6.359833ms
      message: 'load-balancer-api-external: resolved host name ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:05:37Z"
    - latency: 4.799933ms
      message: 'load-balancer-api-external: tcp connection to ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:04:37Z"
    - latency: 10.995968ms
      message: 'load-balancer-api-external: resolved host name ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:04:37Z"
    - latency: 5.286464ms
      message: 'load-balancer-api-external: tcp connection to ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:03:37Z"
    - latency: 9.087634ms
      message: 'load-balancer-api-external: resolved host name ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:03:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 7c8cb3c9-fa3a-4473-9317-de888df601b5
    resourceVersion: "21797"
    uid: c6d13df5-77a2-48e6-b834-4550e05fe05b
  spec:
    sourcePod: network-check-source-65bdbbff45-5dmjq
    targetEndpoint: ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:55:37Z"
      message: 'load-balancer-api-internal: tcp connection to ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.740835ms
      message: 'load-balancer-api-internal: tcp connection to ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:07:37Z"
    - latency: 10.955249ms
      message: 'load-balancer-api-internal: resolved host name ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:07:37Z"
    - latency: 4.70359ms
      message: 'load-balancer-api-internal: tcp connection to ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:06:37Z"
    - latency: 8.735494ms
      message: 'load-balancer-api-internal: resolved host name ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:06:37Z"
    - latency: 5.369611ms
      message: 'load-balancer-api-internal: tcp connection to ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:05:37Z"
    - latency: 6.393084ms
      message: 'load-balancer-api-internal: resolved host name ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:05:37Z"
    - latency: 4.800786ms
      message: 'load-balancer-api-internal: tcp connection to ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:04:37Z"
    - latency: 11.056484ms
      message: 'load-balancer-api-internal: resolved host name ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:04:37Z"
    - latency: 5.321128ms
      message: 'load-balancer-api-internal: tcp connection to ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:03:37Z"
    - latency: 9.043016ms
      message: 'load-balancer-api-internal: resolved host name ade9fd1a1ee0e483c9321570c8385d8a-f1049e740eacdc31.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:03:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-network-check-target-ip-10-0-131-119
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 7c8cb3c9-fa3a-4473-9317-de888df601b5
    resourceVersion: "23273"
    uid: 49489d18-569f-47bb-8faa-7406b6c8fe81
  spec:
    sourcePod: network-check-source-65bdbbff45-5dmjq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:56:37Z"
      message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.263519ms
      message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:10:37Z"
    - latency: 2.534266ms
      message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:09:37Z"
    - latency: 2.52238ms
      message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:08:37Z"
    - latency: 2.32646ms
      message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:07:37Z"
    - latency: 2.433661ms
      message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:06:37Z"
    - latency: 2.336898ms
      message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:05:37Z"
    - latency: 2.359743ms
      message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:04:37Z"
    - latency: 2.444564ms
      message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:03:37Z"
    - latency: 2.141213ms
      message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:02:37Z"
    - latency: 2.445527ms
      message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:01:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-network-check-target-ip-10-0-132-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 7c8cb3c9-fa3a-4473-9317-de888df601b5
    resourceVersion: "23272"
    uid: b409d3a7-d667-47ee-99db-8e8e4f5b297b
  spec:
    sourcePod: network-check-source-65bdbbff45-5dmjq
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:56:37Z"
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 945.646µs
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:10:37Z"
    - latency: 886.583µs
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:09:37Z"
    - latency: 1.33409ms
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:08:37Z"
    - latency: 974.024µs
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:07:37Z"
    - latency: 1.062264ms
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:06:37Z"
    - latency: 1.020965ms
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:05:37Z"
    - latency: 876.185µs
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:04:37Z"
    - latency: 1.044256ms
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:03:37Z"
    - latency: 1.085238ms
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:02:37Z"
    - latency: 927.558µs
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:01:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-network-check-target-ip-10-0-139-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 7c8cb3c9-fa3a-4473-9317-de888df601b5
    resourceVersion: "23274"
    uid: 346fba61-8510-462f-a0d6-7b60ef39a95f
  spec:
    sourcePod: network-check-source-65bdbbff45-5dmjq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:56:37Z"
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.675681ms
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:10:37Z"
    - latency: 2.450706ms
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:09:37Z"
    - latency: 2.573171ms
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:08:37Z"
    - latency: 2.57207ms
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:07:37Z"
    - latency: 2.534901ms
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:06:37Z"
    - latency: 2.760787ms
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:05:37Z"
    - latency: 2.376405ms
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:04:37Z"
    - latency: 2.499024ms
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:03:37Z"
    - latency: 2.756728ms
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:02:37Z"
    - latency: 2.763752ms
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:01:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 7c8cb3c9-fa3a-4473-9317-de888df601b5
    resourceVersion: "21795"
    uid: 5a589674-a318-4024-a3fd-8fc5e2f997b9
  spec:
    sourcePod: network-check-source-65bdbbff45-5dmjq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:55:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 800.591µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:07:37Z"
    - latency: 1.726001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:07:37Z"
    - latency: 752.624µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:06:37Z"
    - latency: 1.790531ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:06:37Z"
    - latency: 934.127µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:05:37Z"
    - latency: 1.875754ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:05:37Z"
    - latency: 1.412835ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:04:37Z"
    - latency: 1.883933ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:04:37Z"
    - latency: 1.120869ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:03:37Z"
    - latency: 1.920956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:03:37Z"
kind: List
metadata:
  resourceVersion: ""