apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T03:58:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: b4b219b0-3864-4d4e-be5b-69f2b810d3ce
    resourceVersion: "63726"
    uid: a8e257b5-46ec-4af4-968f-775dda47c721
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7r456
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:05:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.787µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:40:19Z"
    - latency: 1.139131ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:39:19Z"
    - latency: 1.012491ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:38:19Z"
    - latency: 803.135µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:37:19Z"
    - latency: 1.080378ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:36:19Z"
    - latency: 893.567µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:35:19Z"
    - latency: 1.167903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:34:19Z"
    - latency: 1.092576ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:33:19Z"
    - latency: 808.604µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:32:19Z"
    - latency: 1.667682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:31:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T03:58:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: b4b219b0-3864-4d4e-be5b-69f2b810d3ce
    resourceVersion: "63727"
    uid: 6096390f-b6dc-419a-9f94-2a28900e804e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7r456
    targetEndpoint: a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:04:19Z"
      message: 'load-balancer-api-external: tcp connection to a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.07001ms
      message: 'load-balancer-api-external: tcp connection to a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:40:19Z"
    - latency: 9.989577ms
      message: 'load-balancer-api-external: resolved host name a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:40:19Z"
    - latency: 4.303592ms
      message: 'load-balancer-api-external: tcp connection to a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:39:19Z"
    - latency: 7.595696ms
      message: 'load-balancer-api-external: resolved host name a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:39:19Z"
    - latency: 3.877472ms
      message: 'load-balancer-api-external: tcp connection to a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:38:19Z"
    - latency: 11.470729ms
      message: 'load-balancer-api-external: resolved host name a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:38:19Z"
    - latency: 5.83832ms
      message: 'load-balancer-api-external: tcp connection to a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:37:19Z"
    - latency: 12.92577ms
      message: 'load-balancer-api-external: resolved host name a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:37:19Z"
    - latency: 3.910258ms
      message: 'load-balancer-api-external: tcp connection to a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:36:19Z"
    - latency: 16.831201ms
      message: 'load-balancer-api-external: resolved host name a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:36:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T03:58:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: b4b219b0-3864-4d4e-be5b-69f2b810d3ce
    resourceVersion: "63728"
    uid: 0da2bacd-341b-4f28-a536-5b276a90d95f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7r456
    targetEndpoint: a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:04:19Z"
      message: 'load-balancer-api-internal: tcp connection to a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.099389ms
      message: 'load-balancer-api-internal: tcp connection to a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:40:19Z"
    - latency: 10.035667ms
      message: 'load-balancer-api-internal: resolved host name a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:40:19Z"
    - latency: 4.293459ms
      message: 'load-balancer-api-internal: tcp connection to a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:39:19Z"
    - latency: 7.664601ms
      message: 'load-balancer-api-internal: resolved host name a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:39:19Z"
    - latency: 3.890094ms
      message: 'load-balancer-api-internal: tcp connection to a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:38:19Z"
    - latency: 11.522871ms
      message: 'load-balancer-api-internal: resolved host name a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:38:19Z"
    - latency: 5.849814ms
      message: 'load-balancer-api-internal: tcp connection to a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:37:19Z"
    - latency: 12.941518ms
      message: 'load-balancer-api-internal: resolved host name a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:37:19Z"
    - latency: 3.878298ms
      message: 'load-balancer-api-internal: tcp connection to a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:36:19Z"
    - latency: 16.85921ms
      message: 'load-balancer-api-internal: resolved host name a3a01287373144235afcf18bf12be753-64fd5afb594a8561.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:36:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T03:58:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-network-check-target-ip-10-0-131-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: b4b219b0-3864-4d4e-be5b-69f2b810d3ce
    resourceVersion: "63724"
    uid: f6dae5db-6993-408e-937b-e9ec0f8c20de
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7r456
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:05:19Z"
      message: 'network-check-target-ip-10-0-131-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.039065ms
      message: 'network-check-target-ip-10-0-131-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:40:19Z"
    - latency: 1.91573ms
      message: 'network-check-target-ip-10-0-131-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:39:19Z"
    - latency: 1.996554ms
      message: 'network-check-target-ip-10-0-131-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:38:19Z"
    - latency: 2.080407ms
      message: 'network-check-target-ip-10-0-131-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:37:19Z"
    - latency: 2.022018ms
      message: 'network-check-target-ip-10-0-131-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:36:19Z"
    - latency: 2.008032ms
      message: 'network-check-target-ip-10-0-131-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:35:19Z"
    - latency: 2.003928ms
      message: 'network-check-target-ip-10-0-131-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:34:19Z"
    - latency: 2.090553ms
      message: 'network-check-target-ip-10-0-131-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:33:19Z"
    - latency: 2.108034ms
      message: 'network-check-target-ip-10-0-131-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:32:19Z"
    - latency: 1.886028ms
      message: 'network-check-target-ip-10-0-131-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:31:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T03:58:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-network-check-target-ip-10-0-138-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: b4b219b0-3864-4d4e-be5b-69f2b810d3ce
    resourceVersion: "63722"
    uid: 760cd77b-a35e-4146-85e5-19d126e1f10e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7r456
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:05:19Z"
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.482436ms
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:40:19Z"
    - latency: 845.332µs
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:39:19Z"
    - latency: 1.279291ms
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:38:19Z"
    - latency: 1.188129ms
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:37:19Z"
    - latency: 895.976µs
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:36:19Z"
    - latency: 1.366967ms
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:35:19Z"
    - latency: 967.415µs
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:34:19Z"
    - latency: 1.037121ms
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:33:19Z"
    - latency: 879.455µs
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:32:19Z"
    - latency: 1.00369ms
      message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:31:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T03:58:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-network-check-target-ip-10-0-140-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: b4b219b0-3864-4d4e-be5b-69f2b810d3ce
    resourceVersion: "63723"
    uid: d6fc51a7-495c-4d3e-82f2-e00ccd24c83c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7r456
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:05:19Z"
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.309237ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:40:19Z"
    - latency: 1.915431ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:39:19Z"
    - latency: 2.293535ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:38:19Z"
    - latency: 1.923948ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:37:19Z"
    - latency: 1.967279ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:36:19Z"
    - latency: 2.46993ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:35:19Z"
    - latency: 2.337366ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:34:19Z"
    - latency: 2.161155ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:33:19Z"
    - latency: 2.107446ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:32:19Z"
    - latency: 2.194467ms
      message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:31:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T03:58:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-244-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-244.ec2.internal
      uid: b4b219b0-3864-4d4e-be5b-69f2b810d3ce
    resourceVersion: "63725"
    uid: eafd99ec-8140-41bd-868f-19e41470f80e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7r456
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T04:04:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.239052ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:40:19Z"
    - latency: 1.936724ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:40:19Z"
    - latency: 981.997µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:39:19Z"
    - latency: 2.142134ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:39:19Z"
    - latency: 955.092µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:38:19Z"
    - latency: 1.879266ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:38:19Z"
    - latency: 955.344µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:37:19Z"
    - latency: 1.687973ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:37:19Z"
    - latency: 1.104541ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T04:36:19Z"
    - latency: 1.807168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T04:36:19Z"
kind: List
metadata:
  resourceVersion: ""