apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:23:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-199-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-199.ec2.internal
      uid: e82306c6-2da2-49a8-879f-6842c47ffa53
    resourceVersion: "55553"
    uid: 3ad6ad9f-612a-4035-aad0-d3d839317872
  spec:
    sourcePod: network-check-source-869dcfcdcd-9zjzc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:30:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.049149ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:58:56Z"
    - latency: 991.267µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:57:56Z"
    - latency: 828.432µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:56:56Z"
    - latency: 942.862µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:55:56Z"
    - latency: 887.543µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:54:56Z"
    - latency: 1.024815ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:53:56Z"
    - latency: 808.281µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:52:56Z"
    - latency: 1.085604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:51:56Z"
    - latency: 895.957µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:50:56Z"
    - latency: 1.079976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:49:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:23:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-199-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-199.ec2.internal
      uid: e82306c6-2da2-49a8-879f-6842c47ffa53
    resourceVersion: "56543"
    uid: 581af343-0325-46bf-9b30-2e540b957fa8
  spec:
    sourcePod: network-check-source-869dcfcdcd-9zjzc
    targetEndpoint: a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:29:56Z"
      message: 'load-balancer-api-external: tcp connection to a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.05339ms
      message: 'load-balancer-api-external: tcp connection to a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:59:56Z"
    - latency: 6.022368ms
      message: 'load-balancer-api-external: resolved host name a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:59:56Z"
    - latency: 5.822228ms
      message: 'load-balancer-api-external: tcp connection to a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:58:56Z"
    - latency: 7.353811ms
      message: 'load-balancer-api-external: resolved host name a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:58:56Z"
    - latency: 5.464608ms
      message: 'load-balancer-api-external: tcp connection to a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:57:56Z"
    - latency: 6.142526ms
      message: 'load-balancer-api-external: resolved host name a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:57:56Z"
    - latency: 5.244898ms
      message: 'load-balancer-api-external: tcp connection to a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:56:56Z"
    - latency: 7.207883ms
      message: 'load-balancer-api-external: resolved host name a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:56:56Z"
    - latency: 8.550662ms
      message: 'load-balancer-api-external: tcp connection to a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:55:56Z"
    - latency: 6.18174ms
      message: 'load-balancer-api-external: resolved host name a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:55:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:23:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-199-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-199.ec2.internal
      uid: e82306c6-2da2-49a8-879f-6842c47ffa53
    resourceVersion: "56544"
    uid: 98c76085-83d5-414f-91ef-9198c31f7146
  spec:
    sourcePod: network-check-source-869dcfcdcd-9zjzc
    targetEndpoint: a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:29:56Z"
      message: 'load-balancer-api-internal: tcp connection to a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.561198ms
      message: 'load-balancer-api-internal: tcp connection to a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:59:56Z"
    - latency: 5.965318ms
      message: 'load-balancer-api-internal: resolved host name a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:59:56Z"
    - latency: 5.849302ms
      message: 'load-balancer-api-internal: tcp connection to a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:58:56Z"
    - latency: 7.305293ms
      message: 'load-balancer-api-internal: resolved host name a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:58:56Z"
    - latency: 3.81758ms
      message: 'load-balancer-api-internal: tcp connection to a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:57:56Z"
    - latency: 6.162655ms
      message: 'load-balancer-api-internal: resolved host name a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:57:56Z"
    - latency: 5.253935ms
      message: 'load-balancer-api-internal: tcp connection to a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:56:56Z"
    - latency: 7.299731ms
      message: 'load-balancer-api-internal: resolved host name a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:56:56Z"
    - latency: 6.527279ms
      message: 'load-balancer-api-internal: tcp connection to a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:55:56Z"
    - latency: 6.236891ms
      message: 'load-balancer-api-internal: resolved host name a9c2fcb450ad9443eb3f070d5281a6e8-f58b9f5362c947eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:55:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:23:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-199-to-network-check-target-ip-10-0-132-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-199.ec2.internal
      uid: e82306c6-2da2-49a8-879f-6842c47ffa53
    resourceVersion: "55551"
    uid: c247a990-4c47-4ce1-b34f-d58a5ccc09fb
  spec:
    sourcePod: network-check-source-869dcfcdcd-9zjzc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:30:56Z"
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.141863ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:58:56Z"
    - latency: 2.46653ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:57:56Z"
    - latency: 2.076797ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:56:56Z"
    - latency: 2.009091ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:55:56Z"
    - latency: 2.462646ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:54:56Z"
    - latency: 2.427727ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:53:56Z"
    - latency: 2.083286ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:52:56Z"
    - latency: 2.292728ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:51:56Z"
    - latency: 2.150806ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:50:56Z"
    - latency: 2.438737ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:49:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:23:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-199-to-network-check-target-ip-10-0-141-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-199.ec2.internal
      uid: e82306c6-2da2-49a8-879f-6842c47ffa53
    resourceVersion: "55550"
    uid: df080df0-98a7-4d85-8163-c25f2fa11fa5
  spec:
    sourcePod: network-check-source-869dcfcdcd-9zjzc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:30:56Z"
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.24201ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:58:56Z"
    - latency: 899.39µs
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:57:56Z"
    - latency: 853.49µs
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:56:56Z"
    - latency: 870.488µs
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:55:56Z"
    - latency: 861.201µs
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:54:56Z"
    - latency: 1.010733ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:53:56Z"
    - latency: 864.566µs
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:52:56Z"
    - latency: 1.110587ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:51:56Z"
    - latency: 1.144195ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:50:56Z"
    - latency: 1.008167ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:49:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:23:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-199-to-network-check-target-ip-10-0-142-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-199.ec2.internal
      uid: e82306c6-2da2-49a8-879f-6842c47ffa53
    resourceVersion: "55552"
    uid: e81c1bbe-58d5-43ed-963e-902397ab4a7b
  spec:
    sourcePod: network-check-source-869dcfcdcd-9zjzc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:30:56Z"
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.034019ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:58:56Z"
    - latency: 2.511268ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:57:56Z"
    - latency: 1.795199ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:56:56Z"
    - latency: 2.302972ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:55:56Z"
    - latency: 2.079647ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:54:56Z"
    - latency: 2.567383ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:53:56Z"
    - latency: 2.080495ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:52:56Z"
    - latency: 2.327554ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:51:56Z"
    - latency: 2.194411ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:50:56Z"
    - latency: 2.422974ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:49:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:23:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-199-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-199.ec2.internal
      uid: e82306c6-2da2-49a8-879f-6842c47ffa53
    resourceVersion: "56542"
    uid: 7e1a7147-7cfd-43a1-a991-3431aa945637
  spec:
    sourcePod: network-check-source-869dcfcdcd-9zjzc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:29:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.075µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:59:56Z"
    - latency: 1.613731ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:59:56Z"
    - latency: 1.223029ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:58:56Z"
    - latency: 1.830659ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:58:56Z"
    - latency: 1.073421ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:57:56Z"
    - latency: 1.643683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:57:56Z"
    - latency: 894.613µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:56:56Z"
    - latency: 1.674345ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:56:56Z"
    - latency: 823.692µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:55:56Z"
    - latency: 1.623663ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:55:56Z"
kind: List
metadata:
  resourceVersion: ""