apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T14:16:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: f21c43f8-6b4b-4caf-8789-f9f5c52c3430
    resourceVersion: "56866"
    uid: 3a77baf4-a5d2-4450-9209-843d18f5b878
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kwqzn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T14:23:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 802.369µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:51:04Z"
    - latency: 861.475µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:50:04Z"
    - latency: 2.25838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:49:04Z"
    - latency: 743.374µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:48:04Z"
    - latency: 1.083936ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:47:04Z"
    - latency: 847.803µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:46:04Z"
    - latency: 794.642µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:45:04Z"
    - latency: 1.032486ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:44:04Z"
    - latency: 977.456µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:43:04Z"
    - latency: 691.583µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:42:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T14:16:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: f21c43f8-6b4b-4caf-8789-f9f5c52c3430
    resourceVersion: "58017"
    uid: b782d386-4c93-489d-9033-fea65eb7a236
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kwqzn
    targetEndpoint: a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T14:22:04Z"
      message: 'load-balancer-api-external: tcp connection to a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.577043ms
      message: 'load-balancer-api-external: tcp connection to a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:52:04Z"
    - latency: 9.767747ms
      message: 'load-balancer-api-external: resolved host name a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:52:04Z"
    - latency: 3.86299ms
      message: 'load-balancer-api-external: tcp connection to a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:51:04Z"
    - latency: 7.869669ms
      message: 'load-balancer-api-external: resolved host name a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:51:04Z"
    - latency: 10.842518ms
      message: 'load-balancer-api-external: tcp connection to a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:50:04Z"
    - latency: 9.988372ms
      message: 'load-balancer-api-external: resolved host name a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:50:04Z"
    - latency: 3.540556ms
      message: 'load-balancer-api-external: tcp connection to a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:49:04Z"
    - latency: 7.212762ms
      message: 'load-balancer-api-external: resolved host name a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:49:04Z"
    - latency: 5.051308ms
      message: 'load-balancer-api-external: tcp connection to a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:48:04Z"
    - latency: 10.716232ms
      message: 'load-balancer-api-external: resolved host name a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:48:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T14:16:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: f21c43f8-6b4b-4caf-8789-f9f5c52c3430
    resourceVersion: "58016"
    uid: 426994a2-70d7-42fe-9018-97811e07bbe9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kwqzn
    targetEndpoint: a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T14:22:04Z"
      message: 'load-balancer-api-internal: tcp connection to a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.987888ms
      message: 'load-balancer-api-internal: tcp connection to a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:52:04Z"
    - latency: 9.83464ms
      message: 'load-balancer-api-internal: resolved host name a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:52:04Z"
    - latency: 3.948606ms
      message: 'load-balancer-api-internal: tcp connection to a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:51:04Z"
    - latency: 7.932948ms
      message: 'load-balancer-api-internal: resolved host name a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:51:04Z"
    - latency: 4.446184ms
      message: 'load-balancer-api-internal: tcp connection to a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:50:04Z"
    - latency: 10.067731ms
      message: 'load-balancer-api-internal: resolved host name a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:50:04Z"
    - latency: 5.384626ms
      message: 'load-balancer-api-internal: tcp connection to a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:49:04Z"
    - latency: 7.367389ms
      message: 'load-balancer-api-internal: resolved host name a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:49:04Z"
    - latency: 5.0398ms
      message: 'load-balancer-api-internal: tcp connection to a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:48:04Z"
    - latency: 10.817013ms
      message: 'load-balancer-api-internal: resolved host name a651b7083f1ab46e09ec6b2086b74a54-46dea47dc784dd9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:48:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T14:16:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-network-check-target-ip-10-0-138-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: f21c43f8-6b4b-4caf-8789-f9f5c52c3430
    resourceVersion: "56865"
    uid: 7cd7e885-bebf-4aa5-8a4e-34f3a2e5af10
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kwqzn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T14:23:04Z"
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.867009ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:51:04Z"
    - latency: 2.010755ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:50:04Z"
    - latency: 2.146644ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:49:04Z"
    - latency: 1.812478ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:48:04Z"
    - latency: 3.115555ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:47:04Z"
    - latency: 2.112357ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:46:04Z"
    - latency: 1.922214ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:45:04Z"
    - latency: 2.15091ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:44:04Z"
    - latency: 2.099087ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:43:04Z"
    - latency: 2.023691ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:42:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T14:16:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-network-check-target-ip-10-0-141-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: f21c43f8-6b4b-4caf-8789-f9f5c52c3430
    resourceVersion: "56863"
    uid: 604f9c40-5b82-4f0c-8e57-7dba3311b990
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kwqzn
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T14:23:04Z"
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 934.852µs
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:51:04Z"
    - latency: 1.220864ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:50:04Z"
    - latency: 1.064692ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:49:04Z"
    - latency: 868.486µs
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:48:04Z"
    - latency: 1.100671ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:47:04Z"
    - latency: 744.506µs
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:46:04Z"
    - latency: 1.002221ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:45:04Z"
    - latency: 1.069571ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:44:04Z"
    - latency: 1.283935ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:43:04Z"
    - latency: 1.677734ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:42:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T14:16:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-network-check-target-ip-10-0-143-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: f21c43f8-6b4b-4caf-8789-f9f5c52c3430
    resourceVersion: "56864"
    uid: 594332d5-8e3d-4fec-9e35-2ce721440049
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kwqzn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T14:23:04Z"
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.043902ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:51:04Z"
    - latency: 2.323382ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:50:04Z"
    - latency: 2.433012ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:49:04Z"
    - latency: 1.934203ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:48:04Z"
    - latency: 2.207494ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:47:04Z"
    - latency: 2.238061ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:46:04Z"
    - latency: 2.113314ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:45:04Z"
    - latency: 2.514251ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:44:04Z"
    - latency: 2.094467ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:43:04Z"
    - latency: 1.894959ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:42:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T14:16:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-191-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-191.ec2.internal
      uid: f21c43f8-6b4b-4caf-8789-f9f5c52c3430
    resourceVersion: "58015"
    uid: 318cc5a5-72b5-42be-9541-1a8af9cf0c85
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kwqzn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T14:22:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.494µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:52:04Z"
    - latency: 1.615303ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:52:04Z"
    - latency: 920.522µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:51:04Z"
    - latency: 1.721659ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:51:04Z"
    - latency: 884.401µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:50:04Z"
    - latency: 1.954654ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:50:04Z"
    - latency: 1.007991ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:49:04Z"
    - latency: 2.314761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:49:04Z"
    - latency: 864.997µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T14:48:04Z"
    - latency: 1.629616ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T14:48:04Z"
kind: List
metadata:
  resourceVersion: ""