apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T23:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-89-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-89.ec2.internal
      uid: 79c70eb8-8919-4282-97ee-de445f67adb0
    resourceVersion: "19410"
    uid: 0609da91-3ad1-41dd-9582-7b28c9cfb6ca
  spec:
    sourcePod: network-check-source-7f44b6dd87-l5jqf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T23:52:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.218634ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:06:37Z"
    - latency: 1.392254ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:05:37Z"
    - latency: 1.089742ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:04:37Z"
    - latency: 894.238µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:03:37Z"
    - latency: 1.204553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:02:37Z"
    - latency: 997.333µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:01:37Z"
    - latency: 756.808µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:00:37Z"
    - latency: 1.16966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T23:59:37Z"
    - latency: 975.066µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T23:58:37Z"
    - latency: 951.573µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T23:57:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T23:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-89-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-89.ec2.internal
      uid: 79c70eb8-8919-4282-97ee-de445f67adb0
    resourceVersion: "20645"
    uid: 98eb9253-ee2c-41a1-a3d5-a77a6cd0652c
  spec:
    sourcePod: network-check-source-7f44b6dd87-l5jqf
    targetEndpoint: a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T23:51:37Z"
      message: 'load-balancer-api-external: tcp connection to a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.287241ms
      message: 'load-balancer-api-external: tcp connection to a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:09:37Z"
    - latency: 7.899569ms
      message: 'load-balancer-api-external: resolved host name a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:09:37Z"
    - latency: 6.165601ms
      message: 'load-balancer-api-external: tcp connection to a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:08:37Z"
    - latency: 8.498923ms
      message: 'load-balancer-api-external: resolved host name a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:08:37Z"
    - latency: 4.924884ms
      message: 'load-balancer-api-external: tcp connection to a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:07:37Z"
    - latency: 6.987458ms
      message: 'load-balancer-api-external: resolved host name a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:07:37Z"
    - latency: 5.249081ms
      message: 'load-balancer-api-external: tcp connection to a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:06:37Z"
    - latency: 8.886348ms
      message: 'load-balancer-api-external: resolved host name a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:06:37Z"
    - latency: 8.822559ms
      message: 'load-balancer-api-external: tcp connection to a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:05:37Z"
    - latency: 7.597769ms
      message: 'load-balancer-api-external: resolved host name a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:05:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T23:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-89-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-89.ec2.internal
      uid: 79c70eb8-8919-4282-97ee-de445f67adb0
    resourceVersion: "20646"
    uid: 594c2c24-6a97-48d3-accb-ba3a85a1ee45
  spec:
    sourcePod: network-check-source-7f44b6dd87-l5jqf
    targetEndpoint: a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T23:51:37Z"
      message: 'load-balancer-api-internal: tcp connection to a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.463305ms
      message: 'load-balancer-api-internal: tcp connection to a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:09:37Z"
    - latency: 7.861374ms
      message: 'load-balancer-api-internal: resolved host name a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:09:37Z"
    - latency: 4.354949ms
      message: 'load-balancer-api-internal: tcp connection to a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:08:37Z"
    - latency: 8.407203ms
      message: 'load-balancer-api-internal: resolved host name a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:08:37Z"
    - latency: 4.187498ms
      message: 'load-balancer-api-internal: tcp connection to a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:07:37Z"
    - latency: 6.87043ms
      message: 'load-balancer-api-internal: resolved host name a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:07:37Z"
    - latency: 4.518653ms
      message: 'load-balancer-api-internal: tcp connection to a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:06:37Z"
    - latency: 8.810435ms
      message: 'load-balancer-api-internal: resolved host name a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:06:37Z"
    - latency: 3.59811ms
      message: 'load-balancer-api-internal: tcp connection to a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:05:37Z"
    - latency: 7.520439ms
      message: 'load-balancer-api-internal: resolved host name a95dc19e4fef84734a419e7c3fd2cb5a-0475b373a272f480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:05:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T23:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-89-to-network-check-target-ip-10-0-128-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-89.ec2.internal
      uid: 79c70eb8-8919-4282-97ee-de445f67adb0
    resourceVersion: "19408"
    uid: f05b817e-b00c-4f8c-92df-b40ff05227cb
  spec:
    sourcePod: network-check-source-7f44b6dd87-l5jqf
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T23:52:37Z"
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.086258ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:06:37Z"
    - latency: 2.004892ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:05:37Z"
    - latency: 1.970596ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:04:37Z"
    - latency: 1.799478ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:03:37Z"
    - latency: 2.056334ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:02:37Z"
    - latency: 2.086973ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:01:37Z"
    - latency: 2.312713ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:00:37Z"
    - latency: 2.088255ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T23:59:37Z"
    - latency: 1.924105ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T23:58:37Z"
    - latency: 2.039662ms
      message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T23:57:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T23:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-89-to-network-check-target-ip-10-0-133-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-89.ec2.internal
      uid: 79c70eb8-8919-4282-97ee-de445f67adb0
    resourceVersion: "19407"
    uid: a77ce3a0-9460-43b5-b0f1-5e93f49cf448
  spec:
    sourcePod: network-check-source-7f44b6dd87-l5jqf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T23:52:37Z"
      message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.998479ms
      message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:06:37Z"
    - latency: 2.284065ms
      message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:05:37Z"
    - latency: 1.860554ms
      message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:04:37Z"
    - latency: 1.95622ms
      message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:03:37Z"
    - latency: 2.158881ms
      message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:02:37Z"
    - latency: 1.760272ms
      message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:01:37Z"
    - latency: 1.671461ms
      message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:00:37Z"
    - latency: 2.023599ms
      message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T23:59:37Z"
    - latency: 1.833385ms
      message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T23:58:37Z"
    - latency: 1.90327ms
      message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T23:57:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T23:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-89-to-network-check-target-ip-10-0-135-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-89.ec2.internal
      uid: 79c70eb8-8919-4282-97ee-de445f67adb0
    resourceVersion: "19409"
    uid: 5e07d9c7-b2d1-4903-92f4-ac196d0038a8
  spec:
    sourcePod: network-check-source-7f44b6dd87-l5jqf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T23:52:37Z"
      message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 746.37µs
      message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:06:37Z"
    - latency: 755.423µs
      message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:05:37Z"
    - latency: 1.26228ms
      message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:04:37Z"
    - latency: 968.182µs
      message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:03:37Z"
    - latency: 1.276513ms
      message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:02:37Z"
    - latency: 839.715µs
      message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:01:37Z"
    - latency: 1.50081ms
      message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:00:37Z"
    - latency: 859.298µs
      message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T23:59:37Z"
    - latency: 741.858µs
      message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T23:58:37Z"
    - latency: 1.301961ms
      message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T23:57:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T23:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-89-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-89.ec2.internal
      uid: 79c70eb8-8919-4282-97ee-de445f67adb0
    resourceVersion: "20644"
    uid: 8905b350-d241-4cee-abb2-0d7d2c65431e
  spec:
    sourcePod: network-check-source-7f44b6dd87-l5jqf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T23:51:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.075987ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:09:37Z"
    - latency: 1.535913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:09:37Z"
    - latency: 850.965µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:08:37Z"
    - latency: 1.838789ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:08:37Z"
    - latency: 900.764µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:07:37Z"
    - latency: 1.708258ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:07:37Z"
    - latency: 766.808µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:06:37Z"
    - latency: 2.059746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:06:37Z"
    - latency: 1.169638ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T00:05:37Z"
    - latency: 1.547905ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T00:05:37Z"
kind: List
metadata:
  resourceVersion: ""