apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:36:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-2-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-2.ec2.internal
      uid: eeae96dc-890e-440e-93d4-5d015b616ba9
    resourceVersion: "47647"
    uid: f0092444-b150-427e-b834-0a8f6143b5e0
  spec:
    sourcePod: network-check-source-989f8b8dc-48ttc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:43:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.081709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:04:09Z"
    - latency: 1.28935ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:03:09Z"
    - latency: 1.438506ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:02:09Z"
    - latency: 1.209096ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:01:09Z"
    - latency: 929.751µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:00:09Z"
    - latency: 925.589µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:59:09Z"
    - latency: 975.041µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:58:09Z"
    - latency: 1.455147ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:57:09Z"
    - latency: 1.120244ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:56:09Z"
    - latency: 1.336021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:55:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:36:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-2-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-2.ec2.internal
      uid: eeae96dc-890e-440e-93d4-5d015b616ba9
    resourceVersion: "50456"
    uid: 4ce3a11c-8109-4462-bd69-76de99c577c6
  spec:
    sourcePod: network-check-source-989f8b8dc-48ttc
    targetEndpoint: adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:42:09Z"
      message: 'load-balancer-api-external: tcp connection to adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.24532ms
      message: 'load-balancer-api-external: tcp connection to adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:06:09Z"
    - latency: 7.938293ms
      message: 'load-balancer-api-external: resolved host name adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:06:09Z"
    - latency: 4.483873ms
      message: 'load-balancer-api-external: tcp connection to adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:05:09Z"
    - latency: 8.217491ms
      message: 'load-balancer-api-external: resolved host name adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:05:09Z"
    - latency: 4.479487ms
      message: 'load-balancer-api-external: tcp connection to adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:04:09Z"
    - latency: 11.473396ms
      message: 'load-balancer-api-external: resolved host name adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:04:09Z"
    - latency: 5.292157ms
      message: 'load-balancer-api-external: tcp connection to adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:03:09Z"
    - latency: 6.903173ms
      message: 'load-balancer-api-external: resolved host name adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:03:09Z"
    - latency: 3.359338ms
      message: 'load-balancer-api-external: tcp connection to adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:02:09Z"
    - latency: 7.725966ms
      message: 'load-balancer-api-external: resolved host name adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:02:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:36:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-2-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-2.ec2.internal
      uid: eeae96dc-890e-440e-93d4-5d015b616ba9
    resourceVersion: "50455"
    uid: 1d30f2a4-6edf-442f-bf1c-cc88f969e9a3
  spec:
    sourcePod: network-check-source-989f8b8dc-48ttc
    targetEndpoint: adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:42:09Z"
      message: 'load-balancer-api-internal: tcp connection to adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.120349ms
      message: 'load-balancer-api-internal: tcp connection to adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:06:09Z"
    - latency: 7.870934ms
      message: 'load-balancer-api-internal: resolved host name adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:06:09Z"
    - latency: 4.502495ms
      message: 'load-balancer-api-internal: tcp connection to adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:05:09Z"
    - latency: 8.150281ms
      message: 'load-balancer-api-internal: resolved host name adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:05:09Z"
    - latency: 4.527452ms
      message: 'load-balancer-api-internal: tcp connection to adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:04:09Z"
    - latency: 11.388581ms
      message: 'load-balancer-api-internal: resolved host name adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:04:09Z"
    - latency: 5.320199ms
      message: 'load-balancer-api-internal: tcp connection to adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:03:09Z"
    - latency: 6.97324ms
      message: 'load-balancer-api-internal: resolved host name adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:03:09Z"
    - latency: 3.294546ms
      message: 'load-balancer-api-internal: tcp connection to adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:02:09Z"
    - latency: 7.702682ms
      message: 'load-balancer-api-internal: resolved host name adc7f5e61c6a645c49437098a4141967-b11a00f436d3d092.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:02:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:36:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-2-to-network-check-target-ip-10-0-131-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-2.ec2.internal
      uid: eeae96dc-890e-440e-93d4-5d015b616ba9
    resourceVersion: "47644"
    uid: cd8b102b-235a-46b2-b6d8-f7a0543ff85d
  spec:
    sourcePod: network-check-source-989f8b8dc-48ttc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:43:09Z"
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.18427ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:04:09Z"
    - latency: 926.075µs
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:03:09Z"
    - latency: 1.696242ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:02:09Z"
    - latency: 968.849µs
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:01:09Z"
    - latency: 1.040779ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:00:09Z"
    - latency: 1.209785ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:59:09Z"
    - latency: 972.15µs
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:58:09Z"
    - latency: 1.449577ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:57:09Z"
    - latency: 807.245µs
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:56:09Z"
    - latency: 1.520178ms
      message: 'network-check-target-ip-10-0-131-2: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:55:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:36:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-2-to-network-check-target-ip-10-0-139-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-2.ec2.internal
      uid: eeae96dc-890e-440e-93d4-5d015b616ba9
    resourceVersion: "47645"
    uid: 0d5e8686-c36d-4995-8813-d5e12739eae2
  spec:
    sourcePod: network-check-source-989f8b8dc-48ttc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:43:09Z"
      message: 'network-check-target-ip-10-0-139-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.937966ms
      message: 'network-check-target-ip-10-0-139-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:04:09Z"
    - latency: 1.727973ms
      message: 'network-check-target-ip-10-0-139-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:03:09Z"
    - latency: 1.866813ms
      message: 'network-check-target-ip-10-0-139-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:02:09Z"
    - latency: 1.964683ms
      message: 'network-check-target-ip-10-0-139-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:01:09Z"
    - latency: 1.798904ms
      message: 'network-check-target-ip-10-0-139-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:00:09Z"
    - latency: 1.827741ms
      message: 'network-check-target-ip-10-0-139-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:59:09Z"
    - latency: 1.752734ms
      message: 'network-check-target-ip-10-0-139-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:58:09Z"
    - latency: 1.889155ms
      message: 'network-check-target-ip-10-0-139-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:57:09Z"
    - latency: 1.773613ms
      message: 'network-check-target-ip-10-0-139-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:56:09Z"
    - latency: 1.906393ms
      message: 'network-check-target-ip-10-0-139-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:55:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:36:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-2-to-network-check-target-ip-10-0-143-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-2.ec2.internal
      uid: eeae96dc-890e-440e-93d4-5d015b616ba9
    resourceVersion: "47646"
    uid: f57a7525-15af-46aa-af7a-3d4ffa122fbb
  spec:
    sourcePod: network-check-source-989f8b8dc-48ttc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:43:09Z"
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.30032ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:04:09Z"
    - latency: 2.265387ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:03:09Z"
    - latency: 2.240025ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:02:09Z"
    - latency: 3.038835ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:01:09Z"
    - latency: 2.285851ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:00:09Z"
    - latency: 2.291007ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:59:09Z"
    - latency: 2.166474ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:58:09Z"
    - latency: 2.254507ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:57:09Z"
    - latency: 2.13839ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:56:09Z"
    - latency: 2.428005ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T21:55:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T21:36:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-2-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-2.ec2.internal
      uid: eeae96dc-890e-440e-93d4-5d015b616ba9
    resourceVersion: "50454"
    uid: ec2675ea-2655-46b2-8189-8a0449a7c546
  spec:
    sourcePod: network-check-source-989f8b8dc-48ttc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T21:42:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.949µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:06:09Z"
    - latency: 1.918806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:06:09Z"
    - latency: 1.030475ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:05:09Z"
    - latency: 1.892008ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:05:09Z"
    - latency: 1.01184ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:04:09Z"
    - latency: 2.035998ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:04:09Z"
    - latency: 950.736µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:03:09Z"
    - latency: 1.617531ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:03:09Z"
    - latency: 1.105848ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:02:09Z"
    - latency: 2.13671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T22:02:09Z"
kind: List
metadata:
  resourceVersion: ""