apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-120-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-120.ec2.internal
      uid: 01dc1b51-df9b-4b8e-a2db-2d3a1bc5b7b9
    resourceVersion: "39647"
    uid: 8c00379b-f6d5-47c9-a07f-a3b3563b8cb7
  spec:
    sourcePod: network-check-source-6f8b768455-sbk9q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 900.132µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:38:18Z"
    - latency: 845.346µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:18Z"
    - latency: 1.064315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:18Z"
    - latency: 1.461934ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:18Z"
    - latency: 1.195848ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:18Z"
    - latency: 929.314µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:18Z"
    - latency: 960.975µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:18Z"
    - latency: 879.863µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:18Z"
    - latency: 1.708231ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:18Z"
    - latency: 987.119µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-120-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-120.ec2.internal
      uid: 01dc1b51-df9b-4b8e-a2db-2d3a1bc5b7b9
    resourceVersion: "39113"
    uid: 7f0893a7-735a-43c0-9dd7-6a1eb0f11d88
  spec:
    sourcePod: network-check-source-6f8b768455-sbk9q
    targetEndpoint: a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:18Z"
      message: 'load-balancer-api-external: tcp connection to a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.750353ms
      message: 'load-balancer-api-external: tcp connection to a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:18Z"
    - latency: 6.401123ms
      message: 'load-balancer-api-external: resolved host name a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:37:18Z"
    - latency: 5.193729ms
      message: 'load-balancer-api-external: tcp connection to a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:18Z"
    - latency: 6.430809ms
      message: 'load-balancer-api-external: resolved host name a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:36:18Z"
    - latency: 5.700767ms
      message: 'load-balancer-api-external: tcp connection to a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:18Z"
    - latency: 7.098034ms
      message: 'load-balancer-api-external: resolved host name a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:35:18Z"
    - latency: 5.183844ms
      message: 'load-balancer-api-external: tcp connection to a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:18Z"
    - latency: 6.666428ms
      message: 'load-balancer-api-external: resolved host name a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:18Z"
    - latency: 3.966288ms
      message: 'load-balancer-api-external: tcp connection to a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:18Z"
    - latency: 7.331345ms
      message: 'load-balancer-api-external: resolved host name a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-120-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-120.ec2.internal
      uid: 01dc1b51-df9b-4b8e-a2db-2d3a1bc5b7b9
    resourceVersion: "39112"
    uid: e7b155e4-9789-4597-a5bd-7d9e3c6d6016
  spec:
    sourcePod: network-check-source-6f8b768455-sbk9q
    targetEndpoint: a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:18Z"
      message: 'load-balancer-api-internal: tcp connection to a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.663726ms
      message: 'load-balancer-api-internal: tcp connection to a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:18Z"
    - latency: 6.497763ms
      message: 'load-balancer-api-internal: resolved host name a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:37:18Z"
    - latency: 5.174492ms
      message: 'load-balancer-api-internal: tcp connection to a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:18Z"
    - latency: 6.357394ms
      message: 'load-balancer-api-internal: resolved host name a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:36:18Z"
    - latency: 5.751273ms
      message: 'load-balancer-api-internal: tcp connection to a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:18Z"
    - latency: 7.046169ms
      message: 'load-balancer-api-internal: resolved host name a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:35:18Z"
    - latency: 5.098669ms
      message: 'load-balancer-api-internal: tcp connection to a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:18Z"
    - latency: 6.628965ms
      message: 'load-balancer-api-internal: resolved host name a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:18Z"
    - latency: 5.125112ms
      message: 'load-balancer-api-internal: tcp connection to a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:18Z"
    - latency: 7.238152ms
      message: 'load-balancer-api-internal: resolved host name a36a062a1fed6437d809268794062a1d-9eeb584b7e68d7a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-120-to-network-check-target-ip-10-0-137-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-120.ec2.internal
      uid: 01dc1b51-df9b-4b8e-a2db-2d3a1bc5b7b9
    resourceVersion: "39646"
    uid: 741e77b0-ed10-42f7-ac2a-d23307b1c3b7
  spec:
    sourcePod: network-check-source-6f8b768455-sbk9q
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:18Z"
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.923227ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:38:18Z"
    - latency: 2.287041ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:18Z"
    - latency: 2.712185ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:18Z"
    - latency: 2.078759ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:18Z"
    - latency: 2.180819ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:18Z"
    - latency: 2.193625ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:18Z"
    - latency: 2.35429ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:18Z"
    - latency: 2.363695ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:18Z"
    - latency: 2.556028ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:18Z"
    - latency: 2.287936ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-120-to-network-check-target-ip-10-0-137-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-120.ec2.internal
      uid: 01dc1b51-df9b-4b8e-a2db-2d3a1bc5b7b9
    resourceVersion: "39645"
    uid: 6be57646-3677-4ff1-89a7-fc60588f95f2
  spec:
    sourcePod: network-check-source-6f8b768455-sbk9q
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:18Z"
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.261335ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:38:18Z"
    - latency: 2.427383ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:18Z"
    - latency: 2.31207ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:18Z"
    - latency: 6.625665ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:18Z"
    - latency: 2.251572ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:18Z"
    - latency: 2.760698ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:18Z"
    - latency: 3.597925ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:18Z"
    - latency: 2.406847ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:18Z"
    - latency: 3.120535ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:18Z"
    - latency: 2.436652ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-120-to-network-check-target-ip-10-0-139-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-120.ec2.internal
      uid: 01dc1b51-df9b-4b8e-a2db-2d3a1bc5b7b9
    resourceVersion: "39644"
    uid: 7cd52ce1-4a4a-4381-9265-1b6c1f58b80a
  spec:
    sourcePod: network-check-source-6f8b768455-sbk9q
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:18Z"
      message: 'network-check-target-ip-10-0-139-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 945.136µs
      message: 'network-check-target-ip-10-0-139-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:38:18Z"
    - latency: 1.311177ms
      message: 'network-check-target-ip-10-0-139-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:18Z"
    - latency: 899.497µs
      message: 'network-check-target-ip-10-0-139-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:18Z"
    - latency: 1.590421ms
      message: 'network-check-target-ip-10-0-139-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:18Z"
    - latency: 978.575µs
      message: 'network-check-target-ip-10-0-139-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:18Z"
    - latency: 1.369131ms
      message: 'network-check-target-ip-10-0-139-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:18Z"
    - latency: 1.447723ms
      message: 'network-check-target-ip-10-0-139-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:18Z"
    - latency: 789.825µs
      message: 'network-check-target-ip-10-0-139-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:18Z"
    - latency: 911.369µs
      message: 'network-check-target-ip-10-0-139-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:18Z"
    - latency: 829.735µs
      message: 'network-check-target-ip-10-0-139-120: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-120-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-120.ec2.internal
      uid: 01dc1b51-df9b-4b8e-a2db-2d3a1bc5b7b9
    resourceVersion: "39111"
    uid: b2303bba-79a3-448e-9ff7-cb42ab731411
  spec:
    sourcePod: network-check-source-6f8b768455-sbk9q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.45087ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:18Z"
    - latency: 1.805114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:37:18Z"
    - latency: 1.764628ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:18Z"
    - latency: 1.719035ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:36:18Z"
    - latency: 876.013µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:18Z"
    - latency: 2.425266ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:35:18Z"
    - latency: 1.015223ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:18Z"
    - latency: 1.819086ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:18Z"
    - latency: 1.007878ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:18Z"
    - latency: 1.823311ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:18Z"
kind: List
metadata:
  resourceVersion: ""