apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T17:44:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-182-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-182.ec2.internal
      uid: 332a324d-0139-41a2-9ed8-54eb1a6ba288
    resourceVersion: "30276"
    uid: 4bbd49d1-d56c-45b5-9e1a-694a7f082ff3
  spec:
    sourcePod: network-check-source-6947749cfc-jx9dl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T17:51:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.177619ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:58:35Z"
    - latency: 1.126321ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:57:35Z"
    - latency: 1.016305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:56:35Z"
    - latency: 965.124µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:55:35Z"
    - latency: 1.191408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:54:35Z"
    - latency: 924.085µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:53:35Z"
    - latency: 1.056486ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:52:35Z"
    - latency: 2.817544ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:51:35Z"
    - latency: 1.142346ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:50:35Z"
    - latency: 957.528µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:49:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T17:44:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-182-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-182.ec2.internal
      uid: 332a324d-0139-41a2-9ed8-54eb1a6ba288
    resourceVersion: "29011"
    uid: 3c343cb0-ad75-4eba-82e9-fa6d7d38d07b
  spec:
    sourcePod: network-check-source-6947749cfc-jx9dl
    targetEndpoint: a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T17:50:35Z"
      message: 'load-balancer-api-external: tcp connection to a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.073258ms
      message: 'load-balancer-api-external: tcp connection to a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:56:35Z"
    - latency: 9.189645ms
      message: 'load-balancer-api-external: resolved host name a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:56:35Z"
    - latency: 5.353143ms
      message: 'load-balancer-api-external: tcp connection to a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:55:35Z"
    - latency: 7.330359ms
      message: 'load-balancer-api-external: resolved host name a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:55:35Z"
    - latency: 4.990664ms
      message: 'load-balancer-api-external: tcp connection to a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:54:35Z"
    - latency: 6.70424ms
      message: 'load-balancer-api-external: resolved host name a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:54:35Z"
    - latency: 5.545734ms
      message: 'load-balancer-api-external: tcp connection to a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:53:35Z"
    - latency: 8.404529ms
      message: 'load-balancer-api-external: resolved host name a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:53:35Z"
    - latency: 4.624354ms
      message: 'load-balancer-api-external: tcp connection to a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:52:35Z"
    - latency: 7.472947ms
      message: 'load-balancer-api-external: resolved host name a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:52:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T17:44:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-182-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-182.ec2.internal
      uid: 332a324d-0139-41a2-9ed8-54eb1a6ba288
    resourceVersion: "29012"
    uid: d1ad6d0b-43f6-4747-92ff-41903fa0392e
  spec:
    sourcePod: network-check-source-6947749cfc-jx9dl
    targetEndpoint: a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T17:50:35Z"
      message: 'load-balancer-api-internal: tcp connection to a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.081781ms
      message: 'load-balancer-api-internal: tcp connection to a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:56:35Z"
    - latency: 9.241547ms
      message: 'load-balancer-api-internal: resolved host name a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:56:35Z"
    - latency: 5.324559ms
      message: 'load-balancer-api-internal: tcp connection to a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:55:35Z"
    - latency: 7.275333ms
      message: 'load-balancer-api-internal: resolved host name a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:55:35Z"
    - latency: 4.932191ms
      message: 'load-balancer-api-internal: tcp connection to a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:54:35Z"
    - latency: 6.779232ms
      message: 'load-balancer-api-internal: resolved host name a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:54:35Z"
    - latency: 5.586478ms
      message: 'load-balancer-api-internal: tcp connection to a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:53:35Z"
    - latency: 8.349252ms
      message: 'load-balancer-api-internal: resolved host name a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:53:35Z"
    - latency: 3.737238ms
      message: 'load-balancer-api-internal: tcp connection to a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:52:35Z"
    - latency: 7.440043ms
      message: 'load-balancer-api-internal: resolved host name a2a475c03064347a4b9290604bbac408-b21aabbe921761a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:52:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T17:44:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-182-to-network-check-target-ip-10-0-129-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-182.ec2.internal
      uid: 332a324d-0139-41a2-9ed8-54eb1a6ba288
    resourceVersion: "30275"
    uid: 6ea6d30c-e78c-4e1b-b468-7e8deec26c65
  spec:
    sourcePod: network-check-source-6947749cfc-jx9dl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T17:51:35Z"
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.406324ms
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:58:35Z"
    - latency: 912.095µs
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:57:35Z"
    - latency: 997.341µs
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:56:35Z"
    - latency: 916.726µs
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:55:35Z"
    - latency: 806.095µs
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:54:35Z"
    - latency: 1.431985ms
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:53:35Z"
    - latency: 938.172µs
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:52:35Z"
    - latency: 6.231149ms
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:51:35Z"
    - latency: 1.344381ms
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:50:35Z"
    - latency: 1.068136ms
      message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:49:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T17:44:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-182-to-network-check-target-ip-10-0-129-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-182.ec2.internal
      uid: 332a324d-0139-41a2-9ed8-54eb1a6ba288
    resourceVersion: "30274"
    uid: 627ca7b2-c314-4d49-9867-be59702827c7
  spec:
    sourcePod: network-check-source-6947749cfc-jx9dl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T17:51:35Z"
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.129759ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:58:35Z"
    - latency: 2.072407ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:57:35Z"
    - latency: 1.838722ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:56:35Z"
    - latency: 1.946048ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:55:35Z"
    - latency: 1.75541ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:54:35Z"
    - latency: 1.911398ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:53:35Z"
    - latency: 2.349334ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:52:35Z"
    - latency: 4.638338ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:51:35Z"
    - latency: 1.934383ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:50:35Z"
    - latency: 2.045172ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:49:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T17:44:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-182-to-network-check-target-ip-10-0-130-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-182.ec2.internal
      uid: 332a324d-0139-41a2-9ed8-54eb1a6ba288
    resourceVersion: "30273"
    uid: dfab6ccb-8690-40c0-9cf7-da979580fcc9
  spec:
    sourcePod: network-check-source-6947749cfc-jx9dl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T17:51:35Z"
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.222529ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:58:35Z"
    - latency: 2.217758ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:57:35Z"
    - latency: 2.141173ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:56:35Z"
    - latency: 2.145694ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:55:35Z"
    - latency: 2.129309ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:54:35Z"
    - latency: 2.05729ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:53:35Z"
    - latency: 2.329719ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:52:35Z"
    - latency: 2.993046ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:51:35Z"
    - latency: 2.459264ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:50:35Z"
    - latency: 1.954233ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:49:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T17:44:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-182-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-182.ec2.internal
      uid: 332a324d-0139-41a2-9ed8-54eb1a6ba288
    resourceVersion: "29010"
    uid: 05318f53-6597-4fe3-bb71-96ecfe13e6cf
  spec:
    sourcePod: network-check-source-6947749cfc-jx9dl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T17:50:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.080603ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:56:35Z"
    - latency: 1.858077ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:56:35Z"
    - latency: 837.267µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:55:35Z"
    - latency: 2.119478ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:55:35Z"
    - latency: 1.163789ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:54:35Z"
    - latency: 2.144486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:54:35Z"
    - latency: 861.435µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:53:35Z"
    - latency: 2.023438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:53:35Z"
    - latency: 862.102µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T17:52:35Z"
    - latency: 1.814095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T17:52:35Z"
kind: List
metadata:
  resourceVersion: ""