apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 459e8488-ac98-42be-8fd7-b10ccbadbcb9
    resourceVersion: "68776"
    uid: bffaf1ae-9ec7-4ae8-920a-3b88495af0c1
  spec:
    sourcePod: network-check-source-7cbc45fddc-qm7v4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:16:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 774.582µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:13Z"
    - latency: 851.976µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:13Z"
    - latency: 1.476984ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:13Z"
    - latency: 1.025155ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:13Z"
    - latency: 1.40474ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:13Z"
    - latency: 1.181964ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:13Z"
    - latency: 1.253183ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:13Z"
    - latency: 828.897µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:37:13Z"
    - latency: 1.148748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:36:13Z"
    - latency: 935.39µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 459e8488-ac98-42be-8fd7-b10ccbadbcb9
    resourceVersion: "69750"
    uid: f4054096-b744-4911-adf2-e01dc2b7df1f
  spec:
    sourcePod: network-check-source-7cbc45fddc-qm7v4
    targetEndpoint: a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:15:13Z"
      message: 'load-balancer-api-external: tcp connection to a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.689659ms
      message: 'load-balancer-api-external: tcp connection to a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:45:13Z"
    - latency: 12.940778ms
      message: 'load-balancer-api-external: resolved host name a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:45:13Z"
    - latency: 4.112816ms
      message: 'load-balancer-api-external: tcp connection to a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:13Z"
    - latency: 8.428886ms
      message: 'load-balancer-api-external: resolved host name a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:44:13Z"
    - latency: 5.434879ms
      message: 'load-balancer-api-external: tcp connection to a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:13Z"
    - latency: 8.35982ms
      message: 'load-balancer-api-external: resolved host name a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:43:13Z"
    - latency: 4.803733ms
      message: 'load-balancer-api-external: tcp connection to a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:13Z"
    - latency: 8.26364ms
      message: 'load-balancer-api-external: resolved host name a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:42:13Z"
    - latency: 4.028323ms
      message: 'load-balancer-api-external: tcp connection to a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:13Z"
    - latency: 9.030736ms
      message: 'load-balancer-api-external: resolved host name a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:41:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 459e8488-ac98-42be-8fd7-b10ccbadbcb9
    resourceVersion: "69749"
    uid: 74616cc8-5514-4476-9592-78121b820217
  spec:
    sourcePod: network-check-source-7cbc45fddc-qm7v4
    targetEndpoint: a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:15:13Z"
      message: 'load-balancer-api-internal: tcp connection to a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.682595ms
      message: 'load-balancer-api-internal: tcp connection to a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:45:13Z"
    - latency: 12.902648ms
      message: 'load-balancer-api-internal: resolved host name a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:45:13Z"
    - latency: 5.490866ms
      message: 'load-balancer-api-internal: tcp connection to a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:13Z"
    - latency: 8.351041ms
      message: 'load-balancer-api-internal: resolved host name a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:44:13Z"
    - latency: 5.442258ms
      message: 'load-balancer-api-internal: tcp connection to a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:13Z"
    - latency: 8.397872ms
      message: 'load-balancer-api-internal: resolved host name a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:43:13Z"
    - latency: 4.840149ms
      message: 'load-balancer-api-internal: tcp connection to a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:13Z"
    - latency: 8.238376ms
      message: 'load-balancer-api-internal: resolved host name a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:42:13Z"
    - latency: 3.975129ms
      message: 'load-balancer-api-internal: tcp connection to a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:13Z"
    - latency: 9.01414ms
      message: 'load-balancer-api-internal: resolved host name a987e455fce9245c6b6eaf00af0a34cb-b55fcab530d0b108.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:41:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-network-check-target-ip-10-0-128-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 459e8488-ac98-42be-8fd7-b10ccbadbcb9
    resourceVersion: "68775"
    uid: 642e1ea2-725a-4e3e-8672-d1fa8075fb8c
  spec:
    sourcePod: network-check-source-7cbc45fddc-qm7v4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:16:13Z"
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.910068ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:13Z"
    - latency: 1.944999ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:13Z"
    - latency: 2.786132ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:13Z"
    - latency: 2.261781ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:13Z"
    - latency: 2.180903ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:13Z"
    - latency: 2.183049ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:13Z"
    - latency: 2.183849ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:13Z"
    - latency: 2.339742ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:37:13Z"
    - latency: 2.334826ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:36:13Z"
    - latency: 1.89809ms
      message: 'network-check-target-ip-10-0-128-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-network-check-target-ip-10-0-133-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 459e8488-ac98-42be-8fd7-b10ccbadbcb9
    resourceVersion: "68773"
    uid: 6f60d107-092b-42ea-be70-5cdad47cd773
  spec:
    sourcePod: network-check-source-7cbc45fddc-qm7v4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:16:13Z"
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 855.721µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:13Z"
    - latency: 840.114µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:13Z"
    - latency: 744.101µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:13Z"
    - latency: 1.132408ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:13Z"
    - latency: 871.59µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:13Z"
    - latency: 802.023µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:13Z"
    - latency: 874.602µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:13Z"
    - latency: 1.494183ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:37:13Z"
    - latency: 738.178µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:36:13Z"
    - latency: 842.36µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-network-check-target-ip-10-0-139-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 459e8488-ac98-42be-8fd7-b10ccbadbcb9
    resourceVersion: "68774"
    uid: 9c17ac2e-5341-423f-8cc1-0266bbfe028a
  spec:
    sourcePod: network-check-source-7cbc45fddc-qm7v4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:16:13Z"
      message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.868045ms
      message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:13Z"
    - latency: 1.781835ms
      message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:13Z"
    - latency: 1.952958ms
      message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:13Z"
    - latency: 1.97591ms
      message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:13Z"
    - latency: 1.776505ms
      message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:13Z"
    - latency: 1.93607ms
      message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:13Z"
    - latency: 1.538661ms
      message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:13Z"
    - latency: 2.322736ms
      message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:37:13Z"
    - latency: 2.134653ms
      message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:36:13Z"
    - latency: 1.666268ms
      message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:09:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 459e8488-ac98-42be-8fd7-b10ccbadbcb9
    resourceVersion: "69748"
    uid: da002357-28fa-444b-bfc1-ddb57ec7e773
  spec:
    sourcePod: network-check-source-7cbc45fddc-qm7v4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:15:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.087556ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:45:13Z"
    - latency: 2.75686ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:45:13Z"
    - latency: 880.312µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:44:13Z"
    - latency: 1.958752ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:44:13Z"
    - latency: 1.09213ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:43:13Z"
    - latency: 1.784373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:43:13Z"
    - latency: 992.071µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:13Z"
    - latency: 1.860067ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:42:13Z"
    - latency: 1.055464ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:13Z"
    - latency: 1.96936ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:41:13Z"
kind: List
metadata:
  resourceVersion: ""