apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-165-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-165.ec2.internal
      uid: 5298f1d0-44c2-4ac7-8db0-6c7d00419e31
    resourceVersion: "31918"
    uid: 8278c810-267f-4a6c-8fff-d1435e0d2f8b
  spec:
    sourcePod: network-check-source-56499946bc-v5sl4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:08:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 888.117µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:43:59Z"
    - latency: 896.338µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:42:59Z"
    - latency: 1.242768ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:41:59Z"
    - latency: 1.169175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:40:59Z"
    - latency: 1.169123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:59Z"
    - latency: 985.355µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:38:59Z"
    - latency: 903.128µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:37:59Z"
    - latency: 1.281696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:36:59Z"
    - latency: 920.129µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:35:59Z"
    - latency: 892.243µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:34:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-165-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-165.ec2.internal
      uid: 5298f1d0-44c2-4ac7-8db0-6c7d00419e31
    resourceVersion: "31919"
    uid: 8bcebf9d-f41a-47f0-ba27-ac0a217ba044
  spec:
    sourcePod: network-check-source-56499946bc-v5sl4
    targetEndpoint: a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:07:59Z"
      message: 'load-balancer-api-external: tcp connection to a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.530931ms
      message: 'load-balancer-api-external: tcp connection to a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:43:59Z"
    - latency: 9.366107ms
      message: 'load-balancer-api-external: resolved host name a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:43:59Z"
    - latency: 6.110078ms
      message: 'load-balancer-api-external: tcp connection to a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:42:59Z"
    - latency: 9.604351ms
      message: 'load-balancer-api-external: resolved host name a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:42:59Z"
    - latency: 4.636059ms
      message: 'load-balancer-api-external: tcp connection to a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:41:59Z"
    - latency: 9.345435ms
      message: 'load-balancer-api-external: resolved host name a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:41:59Z"
    - latency: 4.622202ms
      message: 'load-balancer-api-external: tcp connection to a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:40:59Z"
    - latency: 9.380374ms
      message: 'load-balancer-api-external: resolved host name a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:40:59Z"
    - latency: 4.651856ms
      message: 'load-balancer-api-external: tcp connection to a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:59Z"
    - latency: 10.61155ms
      message: 'load-balancer-api-external: resolved host name a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:39:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-165-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-165.ec2.internal
      uid: 5298f1d0-44c2-4ac7-8db0-6c7d00419e31
    resourceVersion: "31920"
    uid: 52368111-591e-4ff9-b215-b56bdd05d7b9
  spec:
    sourcePod: network-check-source-56499946bc-v5sl4
    targetEndpoint: a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:07:59Z"
      message: 'load-balancer-api-internal: tcp connection to a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.558739ms
      message: 'load-balancer-api-internal: tcp connection to a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:43:59Z"
    - latency: 9.283584ms
      message: 'load-balancer-api-internal: resolved host name a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:43:59Z"
    - latency: 4.723188ms
      message: 'load-balancer-api-internal: tcp connection to a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:42:59Z"
    - latency: 9.531638ms
      message: 'load-balancer-api-internal: resolved host name a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:42:59Z"
    - latency: 4.635208ms
      message: 'load-balancer-api-internal: tcp connection to a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:41:59Z"
    - latency: 9.247142ms
      message: 'load-balancer-api-internal: resolved host name a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:41:59Z"
    - latency: 4.679707ms
      message: 'load-balancer-api-internal: tcp connection to a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:40:59Z"
    - latency: 9.338242ms
      message: 'load-balancer-api-internal: resolved host name a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:40:59Z"
    - latency: 4.63359ms
      message: 'load-balancer-api-internal: tcp connection to a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:59Z"
    - latency: 10.588244ms
      message: 'load-balancer-api-internal: resolved host name a560aae34a45d4c378f9b5a53ab074de-b0a7558bdbaf59d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:39:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-165-to-network-check-target-ip-10-0-137-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-165.ec2.internal
      uid: 5298f1d0-44c2-4ac7-8db0-6c7d00419e31
    resourceVersion: "31917"
    uid: ed55a662-0d6e-4849-b01b-56e0981a4e0a
  spec:
    sourcePod: network-check-source-56499946bc-v5sl4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:08:59Z"
      message: 'network-check-target-ip-10-0-137-180: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.491224ms
      message: 'network-check-target-ip-10-0-137-180: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:43:59Z"
    - latency: 2.230011ms
      message: 'network-check-target-ip-10-0-137-180: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:42:59Z"
    - latency: 2.828641ms
      message: 'network-check-target-ip-10-0-137-180: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:41:59Z"
    - latency: 2.407932ms
      message: 'network-check-target-ip-10-0-137-180: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:40:59Z"
    - latency: 2.502295ms
      message: 'network-check-target-ip-10-0-137-180: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:59Z"
    - latency: 2.307159ms
      message: 'network-check-target-ip-10-0-137-180: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:38:59Z"
    - latency: 2.334179ms
      message: 'network-check-target-ip-10-0-137-180: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:37:59Z"
    - latency: 2.468232ms
      message: 'network-check-target-ip-10-0-137-180: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:36:59Z"
    - latency: 2.320965ms
      message: 'network-check-target-ip-10-0-137-180: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:35:59Z"
    - latency: 2.238217ms
      message: 'network-check-target-ip-10-0-137-180: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:34:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-165-to-network-check-target-ip-10-0-138-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-165.ec2.internal
      uid: 5298f1d0-44c2-4ac7-8db0-6c7d00419e31
    resourceVersion: "31914"
    uid: 649cc339-af17-49fe-92f6-d7d0acb7adb3
  spec:
    sourcePod: network-check-source-56499946bc-v5sl4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:08:59Z"
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.054447ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:43:59Z"
    - latency: 808.732µs
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:42:59Z"
    - latency: 1.029745ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:41:59Z"
    - latency: 917.735µs
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:40:59Z"
    - latency: 988.119µs
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:59Z"
    - latency: 818.73µs
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:38:59Z"
    - latency: 925.051µs
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:37:59Z"
    - latency: 1.686073ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:36:59Z"
    - latency: 1.265197ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:35:59Z"
    - latency: 901.458µs
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:34:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-165-to-network-check-target-ip-10-0-140-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-165.ec2.internal
      uid: 5298f1d0-44c2-4ac7-8db0-6c7d00419e31
    resourceVersion: "31915"
    uid: 185fa406-db3e-4e71-8dbf-bda6eeaf2955
  spec:
    sourcePod: network-check-source-56499946bc-v5sl4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:08:59Z"
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.043282ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:43:59Z"
    - latency: 1.738774ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:42:59Z"
    - latency: 2.185901ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:41:59Z"
    - latency: 1.854238ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:40:59Z"
    - latency: 2.131539ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:59Z"
    - latency: 1.709126ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:38:59Z"
    - latency: 1.922976ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:37:59Z"
    - latency: 2.70629ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:36:59Z"
    - latency: 2.155251ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:35:59Z"
    - latency: 2.217758ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:34:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-165-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-165.ec2.internal
      uid: 5298f1d0-44c2-4ac7-8db0-6c7d00419e31
    resourceVersion: "31916"
    uid: f9aaf9da-cf94-4675-833d-a7646c1e93db
  spec:
    sourcePod: network-check-source-56499946bc-v5sl4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T17:07:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 856.348µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:43:59Z"
    - latency: 2.085928ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:43:59Z"
    - latency: 692.788µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:42:59Z"
    - latency: 2.374717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:42:59Z"
    - latency: 1.041064ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:41:59Z"
    - latency: 2.132217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:41:59Z"
    - latency: 1.382366ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:40:59Z"
    - latency: 1.841372ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:40:59Z"
    - latency: 915.184µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:39:59Z"
    - latency: 2.051332ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T17:39:59Z"
kind: List
metadata:
  resourceVersion: ""