apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-67-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-67.ec2.internal
      uid: 28164f7d-b6f0-4290-9898-9c08f15e9afc
    resourceVersion: "62586"
    uid: 8cfe07ad-33dc-4aa7-8076-ddc6bffac89f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vs55f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:08:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.289846ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:43:27Z"
    - latency: 1.148524ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:42:27Z"
    - latency: 1.037473ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:41:27Z"
    - latency: 1.264955ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:40:27Z"
    - latency: 925.095µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:39:27Z"
    - latency: 988.615µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:38:27Z"
    - latency: 921.776µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:37:27Z"
    - latency: 1.025663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:36:27Z"
    - latency: 986.177µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:35:27Z"
    - latency: 1.254332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-67-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-67.ec2.internal
      uid: 28164f7d-b6f0-4290-9898-9c08f15e9afc
    resourceVersion: "62587"
    uid: 030b0ba3-566a-47bf-bc1e-2d7e89022d75
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vs55f
    targetEndpoint: a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:07:27Z"
      message: 'load-balancer-api-external: tcp connection to a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.858454ms
      message: 'load-balancer-api-external: tcp connection to a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:43:27Z"
    - latency: 7.302466ms
      message: 'load-balancer-api-external: resolved host name a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:43:27Z"
    - latency: 5.095922ms
      message: 'load-balancer-api-external: tcp connection to a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:42:27Z"
    - latency: 6.733525ms
      message: 'load-balancer-api-external: resolved host name a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:42:27Z"
    - latency: 3.953756ms
      message: 'load-balancer-api-external: tcp connection to a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:41:27Z"
    - latency: 6.758685ms
      message: 'load-balancer-api-external: resolved host name a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:41:27Z"
    - latency: 4.679646ms
      message: 'load-balancer-api-external: tcp connection to a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:40:27Z"
    - latency: 8.11124ms
      message: 'load-balancer-api-external: resolved host name a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:40:27Z"
    - latency: 6.319548ms
      message: 'load-balancer-api-external: tcp connection to a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:39:27Z"
    - latency: 6.074199ms
      message: 'load-balancer-api-external: resolved host name a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:39:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-67-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-67.ec2.internal
      uid: 28164f7d-b6f0-4290-9898-9c08f15e9afc
    resourceVersion: "62588"
    uid: 81998309-2d39-4729-9fba-4882b46320f0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vs55f
    targetEndpoint: a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:07:27Z"
      message: 'load-balancer-api-internal: tcp connection to a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.617796ms
      message: 'load-balancer-api-internal: tcp connection to a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:43:27Z"
    - latency: 7.38306ms
      message: 'load-balancer-api-internal: resolved host name a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:43:27Z"
    - latency: 5.166297ms
      message: 'load-balancer-api-internal: tcp connection to a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:42:27Z"
    - latency: 6.683982ms
      message: 'load-balancer-api-internal: resolved host name a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:42:27Z"
    - latency: 3.983482ms
      message: 'load-balancer-api-internal: tcp connection to a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:41:27Z"
    - latency: 6.869973ms
      message: 'load-balancer-api-internal: resolved host name a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:41:27Z"
    - latency: 4.740386ms
      message: 'load-balancer-api-internal: tcp connection to a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:40:27Z"
    - latency: 8.063709ms
      message: 'load-balancer-api-internal: resolved host name a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:40:27Z"
    - latency: 4.01504ms
      message: 'load-balancer-api-internal: tcp connection to a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:39:27Z"
    - latency: 6.153637ms
      message: 'load-balancer-api-internal: resolved host name a90d2893e671c42fbbac42057c29c3d6-c2cf9b676fe81faa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:39:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-67-to-network-check-target-ip-10-0-131-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-67.ec2.internal
      uid: 28164f7d-b6f0-4290-9898-9c08f15e9afc
    resourceVersion: "62582"
    uid: 5a0993d6-b1da-471e-ace9-969ca43c0875
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vs55f
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:08:27Z"
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.491488ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:43:27Z"
    - latency: 993.42µs
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:42:27Z"
    - latency: 984.309µs
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:41:27Z"
    - latency: 894.767µs
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:40:27Z"
    - latency: 968.527µs
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:39:27Z"
    - latency: 1.12354ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:38:27Z"
    - latency: 1.033428ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:37:27Z"
    - latency: 986.205µs
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:36:27Z"
    - latency: 1.036601ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:35:27Z"
    - latency: 1.674561ms
      message: 'network-check-target-ip-10-0-131-67: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-67-to-network-check-target-ip-10-0-138-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-67.ec2.internal
      uid: 28164f7d-b6f0-4290-9898-9c08f15e9afc
    resourceVersion: "62583"
    uid: 9da36caf-307b-4d0f-ac4a-b0238cf96d8e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vs55f
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:08:27Z"
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.37551ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:43:27Z"
    - latency: 2.351749ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:42:27Z"
    - latency: 2.304286ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:41:27Z"
    - latency: 2.354512ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:40:27Z"
    - latency: 1.880543ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:39:27Z"
    - latency: 2.587024ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:38:27Z"
    - latency: 2.137163ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:37:27Z"
    - latency: 2.342261ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:36:27Z"
    - latency: 2.234332ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:35:27Z"
    - latency: 2.309133ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-67-to-network-check-target-ip-10-0-139-214
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-67.ec2.internal
      uid: 28164f7d-b6f0-4290-9898-9c08f15e9afc
    resourceVersion: "62584"
    uid: c5e23589-4d90-4b06-8cb1-36e1243f4eb4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vs55f
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:08:27Z"
      message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.460549ms
      message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:43:27Z"
    - latency: 2.404691ms
      message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:42:27Z"
    - latency: 2.365537ms
      message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:41:27Z"
    - latency: 2.364695ms
      message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:40:27Z"
    - latency: 2.001002ms
      message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:39:27Z"
    - latency: 2.186789ms
      message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:38:27Z"
    - latency: 2.149597ms
      message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:37:27Z"
    - latency: 2.359897ms
      message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:36:27Z"
    - latency: 2.538559ms
      message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:35:27Z"
    - latency: 2.67976ms
      message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-67-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-67.ec2.internal
      uid: 28164f7d-b6f0-4290-9898-9c08f15e9afc
    resourceVersion: "62585"
    uid: aeb5788a-b5bc-4f2e-9301-7f48c85118ad
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vs55f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:07:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.075681ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:43:27Z"
    - latency: 2.328659ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:43:27Z"
    - latency: 1.0926ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:42:27Z"
    - latency: 1.718743ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:42:27Z"
    - latency: 896.509µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:41:27Z"
    - latency: 2.138997ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:41:27Z"
    - latency: 772.275µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:40:27Z"
    - latency: 1.767488ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:40:27Z"
    - latency: 914.53µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:39:27Z"
    - latency: 1.750296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:39:27Z"
kind: List
metadata:
  resourceVersion: ""