apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: 6ceae43a-b3fb-4475-9ba2-6d5be8f3759d
    resourceVersion: "55533"
    uid: 158bf1bf-0e03-4256-8e1b-52bcb4cb2d51
  spec:
    sourcePod: network-check-source-989f8b8dc-lt6r6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:37:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.064658ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:05:33Z"
    - latency: 1.030638ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:04:33Z"
    - latency: 972.259µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:03:33Z"
    - latency: 1.573909ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:02:33Z"
    - latency: 1.225792ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:01:33Z"
    - latency: 1.147133ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:00:33Z"
    - latency: 1.240966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:59:33Z"
    - latency: 940.304µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:58:33Z"
    - latency: 1.263564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:57:33Z"
    - latency: 1.180439ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:56:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: 6ceae43a-b3fb-4475-9ba2-6d5be8f3759d
    resourceVersion: "56551"
    uid: c1c22b2c-775c-4a98-9bb2-d9fa83957ff9
  spec:
    sourcePod: network-check-source-989f8b8dc-lt6r6
    targetEndpoint: a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:36:33Z"
      message: 'load-balancer-api-external: tcp connection to a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.805917ms
      message: 'load-balancer-api-external: tcp connection to a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:06:33Z"
    - latency: 6.583994ms
      message: 'load-balancer-api-external: resolved host name a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:06:33Z"
    - latency: 4.084424ms
      message: 'load-balancer-api-external: tcp connection to a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:05:33Z"
    - latency: 8.328069ms
      message: 'load-balancer-api-external: resolved host name a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:05:33Z"
    - latency: 5.58163ms
      message: 'load-balancer-api-external: tcp connection to a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:04:33Z"
    - latency: 9.472156ms
      message: 'load-balancer-api-external: resolved host name a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:04:33Z"
    - latency: 5.2078ms
      message: 'load-balancer-api-external: tcp connection to a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:03:33Z"
    - latency: 7.463599ms
      message: 'load-balancer-api-external: resolved host name a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:03:33Z"
    - latency: 5.342832ms
      message: 'load-balancer-api-external: tcp connection to a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:02:33Z"
    - latency: 7.584242ms
      message: 'load-balancer-api-external: resolved host name a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:02:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: 6ceae43a-b3fb-4475-9ba2-6d5be8f3759d
    resourceVersion: "56552"
    uid: c649637b-1c8c-4c75-ad20-9f2f49608027
  spec:
    sourcePod: network-check-source-989f8b8dc-lt6r6
    targetEndpoint: a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:36:33Z"
      message: 'load-balancer-api-internal: tcp connection to a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.857574ms
      message: 'load-balancer-api-internal: tcp connection to a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:06:33Z"
    - latency: 6.477064ms
      message: 'load-balancer-api-internal: resolved host name a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:06:33Z"
    - latency: 5.46851ms
      message: 'load-balancer-api-internal: tcp connection to a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:05:33Z"
    - latency: 8.376442ms
      message: 'load-balancer-api-internal: resolved host name a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:05:33Z"
    - latency: 5.566336ms
      message: 'load-balancer-api-internal: tcp connection to a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:04:33Z"
    - latency: 9.406006ms
      message: 'load-balancer-api-internal: resolved host name a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:04:33Z"
    - latency: 5.181579ms
      message: 'load-balancer-api-internal: tcp connection to a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:03:33Z"
    - latency: 7.576319ms
      message: 'load-balancer-api-internal: resolved host name a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:03:33Z"
    - latency: 5.34939ms
      message: 'load-balancer-api-internal: tcp connection to a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:02:33Z"
    - latency: 7.513386ms
      message: 'load-balancer-api-internal: resolved host name a0740e88eb4db4bcca76cfc907d33a9d-ba87ec68f5ee7ede.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:02:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-network-check-target-ip-10-0-136-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: 6ceae43a-b3fb-4475-9ba2-6d5be8f3759d
    resourceVersion: "55532"
    uid: 21ad7e15-b61e-4dc3-97c0-e32f472b8897
  spec:
    sourcePod: network-check-source-989f8b8dc-lt6r6
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:37:33Z"
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.569619ms
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:05:33Z"
    - latency: 907.166µs
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:04:33Z"
    - latency: 1.44343ms
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:03:33Z"
    - latency: 882.495µs
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:02:33Z"
    - latency: 1.099907ms
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:01:33Z"
    - latency: 948.423µs
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:00:33Z"
    - latency: 737.166µs
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:59:33Z"
    - latency: 996.897µs
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:58:33Z"
    - latency: 1.608039ms
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:57:33Z"
    - latency: 1.017728ms
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:56:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-network-check-target-ip-10-0-142-195
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: 6ceae43a-b3fb-4475-9ba2-6d5be8f3759d
    resourceVersion: "55531"
    uid: 8d4e5485-a1d4-4994-9b20-611f2536b15b
  spec:
    sourcePod: network-check-source-989f8b8dc-lt6r6
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:37:33Z"
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.363646ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:05:33Z"
    - latency: 2.379891ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:04:33Z"
    - latency: 2.039677ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:03:33Z"
    - latency: 2.682626ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:02:33Z"
    - latency: 2.473905ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:01:33Z"
    - latency: 2.251435ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:00:33Z"
    - latency: 1.906712ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:59:33Z"
    - latency: 2.14256ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:58:33Z"
    - latency: 2.215131ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:57:33Z"
    - latency: 2.840461ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:56:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-network-check-target-ip-10-0-143-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: 6ceae43a-b3fb-4475-9ba2-6d5be8f3759d
    resourceVersion: "55530"
    uid: d71f4bc1-28f9-4eaf-938e-01a8f4283f54
  spec:
    sourcePod: network-check-source-989f8b8dc-lt6r6
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:37:33Z"
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.386126ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:05:33Z"
    - latency: 2.550007ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:04:33Z"
    - latency: 2.476874ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:03:33Z"
    - latency: 2.835267ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:02:33Z"
    - latency: 2.500991ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:01:33Z"
    - latency: 2.484099ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:00:33Z"
    - latency: 2.313344ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:59:33Z"
    - latency: 2.335417ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:58:33Z"
    - latency: 2.422965ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:57:33Z"
    - latency: 2.392802ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T19:56:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:30:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: 6ceae43a-b3fb-4475-9ba2-6d5be8f3759d
    resourceVersion: "56550"
    uid: 2e64f33a-7683-432a-8b88-09f0a457cdd0
  spec:
    sourcePod: network-check-source-989f8b8dc-lt6r6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:36:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.151387ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:06:33Z"
    - latency: 1.823695ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:06:33Z"
    - latency: 851.697µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:05:33Z"
    - latency: 2.429251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:05:33Z"
    - latency: 1.384238ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:04:33Z"
    - latency: 1.790292ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:04:33Z"
    - latency: 1.10303ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:03:33Z"
    - latency: 1.721642ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:03:33Z"
    - latency: 902.744µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:02:33Z"
    - latency: 1.940079ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:02:33Z"
kind: List
metadata:
  resourceVersion: ""