apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T19:57:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4d19778d-1c4b-4371-a1c0-db9a4d2d35c4
    resourceVersion: "53878"
    uid: 3791515f-b246-4fc1-85a3-c9740462e269
  spec:
    sourcePod: network-check-source-6947749cfc-nwqmb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:04:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.090959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:32:26Z"
    - latency: 996.807µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:31:26Z"
    - latency: 816.672µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:30:26Z"
    - latency: 880.836µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:29:26Z"
    - latency: 1.128187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:28:26Z"
    - latency: 946.401µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:27:26Z"
    - latency: 1.014824ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:26:26Z"
    - latency: 990.663µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:25:26Z"
    - latency: 1.503757ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:24:26Z"
    - latency: 932.145µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:23:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T19:57:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4d19778d-1c4b-4371-a1c0-db9a4d2d35c4
    resourceVersion: "54519"
    uid: 6997f667-019e-4fb5-96eb-324e141542be
  spec:
    sourcePod: network-check-source-6947749cfc-nwqmb
    targetEndpoint: a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:03:26Z"
      message: 'load-balancer-api-external: tcp connection to a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.289572ms
      message: 'load-balancer-api-external: tcp connection to a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:33:26Z"
    - latency: 10.533852ms
      message: 'load-balancer-api-external: resolved host name a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:33:26Z"
    - latency: 5.663852ms
      message: 'load-balancer-api-external: tcp connection to a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:32:26Z"
    - latency: 8.683043ms
      message: 'load-balancer-api-external: resolved host name a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:32:26Z"
    - latency: 5.633473ms
      message: 'load-balancer-api-external: tcp connection to a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:31:26Z"
    - latency: 8.106566ms
      message: 'load-balancer-api-external: resolved host name a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:31:26Z"
    - latency: 4.621544ms
      message: 'load-balancer-api-external: tcp connection to a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:30:26Z"
    - latency: 12.868066ms
      message: 'load-balancer-api-external: resolved host name a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:30:26Z"
    - latency: 3.929748ms
      message: 'load-balancer-api-external: tcp connection to a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:29:26Z"
    - latency: 8.747481ms
      message: 'load-balancer-api-external: resolved host name a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:29:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T19:57:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4d19778d-1c4b-4371-a1c0-db9a4d2d35c4
    resourceVersion: "54520"
    uid: 53ccfca8-2029-43cf-b65d-bd1eff687275
  spec:
    sourcePod: network-check-source-6947749cfc-nwqmb
    targetEndpoint: a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:03:26Z"
      message: 'load-balancer-api-internal: tcp connection to a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.325515ms
      message: 'load-balancer-api-internal: tcp connection to a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:33:26Z"
    - latency: 10.560974ms
      message: 'load-balancer-api-internal: resolved host name a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:33:26Z"
    - latency: 5.606519ms
      message: 'load-balancer-api-internal: tcp connection to a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:32:26Z"
    - latency: 8.657119ms
      message: 'load-balancer-api-internal: resolved host name a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:32:26Z"
    - latency: 5.637574ms
      message: 'load-balancer-api-internal: tcp connection to a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:31:26Z"
    - latency: 8.201425ms
      message: 'load-balancer-api-internal: resolved host name a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:31:26Z"
    - latency: 5.316844ms
      message: 'load-balancer-api-internal: tcp connection to a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:30:26Z"
    - latency: 12.942348ms
      message: 'load-balancer-api-internal: resolved host name a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:30:26Z"
    - latency: 3.91382ms
      message: 'load-balancer-api-internal: tcp connection to a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:29:26Z"
    - latency: 8.707869ms
      message: 'load-balancer-api-internal: resolved host name a0854eedb8ed84c2e8893a70586be98f-87c0c533d1e460e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:29:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T19:57:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-network-check-target-ip-10-0-137-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4d19778d-1c4b-4371-a1c0-db9a4d2d35c4
    resourceVersion: "53876"
    uid: 5ccd53e2-45a5-408c-a242-c290839929b1
  spec:
    sourcePod: network-check-source-6947749cfc-nwqmb
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:04:26Z"
      message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.822508ms
      message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:32:26Z"
    - latency: 1.872299ms
      message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:31:26Z"
    - latency: 1.883418ms
      message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:30:26Z"
    - latency: 1.737325ms
      message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:29:26Z"
    - latency: 1.756877ms
      message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:28:26Z"
    - latency: 1.922916ms
      message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:27:26Z"
    - latency: 1.959552ms
      message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:26:26Z"
    - latency: 1.857334ms
      message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:25:26Z"
    - latency: 1.742122ms
      message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:24:26Z"
    - latency: 1.805359ms
      message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:23:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T19:57:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-network-check-target-ip-10-0-137-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4d19778d-1c4b-4371-a1c0-db9a4d2d35c4
    resourceVersion: "53875"
    uid: 8549de1d-1b50-44b8-bfec-09230d9d9c3e
  spec:
    sourcePod: network-check-source-6947749cfc-nwqmb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:04:26Z"
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.907µs
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:32:26Z"
    - latency: 973.784µs
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:31:26Z"
    - latency: 963.198µs
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:30:26Z"
    - latency: 926.28µs
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:29:26Z"
    - latency: 1.374498ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:28:26Z"
    - latency: 1.095813ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:27:26Z"
    - latency: 1.203257ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:26:26Z"
    - latency: 1.009342ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:25:26Z"
    - latency: 857.72µs
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:24:26Z"
    - latency: 1.049228ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:23:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T19:57:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-network-check-target-ip-10-0-138-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4d19778d-1c4b-4371-a1c0-db9a4d2d35c4
    resourceVersion: "53877"
    uid: b47e6f36-d4d9-4ccb-8180-0d7818b19ce8
  spec:
    sourcePod: network-check-source-6947749cfc-nwqmb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:04:26Z"
      message: 'network-check-target-ip-10-0-138-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.296182ms
      message: 'network-check-target-ip-10-0-138-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:32:26Z"
    - latency: 2.093373ms
      message: 'network-check-target-ip-10-0-138-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:31:26Z"
    - latency: 2.142147ms
      message: 'network-check-target-ip-10-0-138-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:30:26Z"
    - latency: 2.041003ms
      message: 'network-check-target-ip-10-0-138-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:29:26Z"
    - latency: 1.969938ms
      message: 'network-check-target-ip-10-0-138-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:28:26Z"
    - latency: 2.161632ms
      message: 'network-check-target-ip-10-0-138-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:27:26Z"
    - latency: 2.077436ms
      message: 'network-check-target-ip-10-0-138-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:26:26Z"
    - latency: 1.784869ms
      message: 'network-check-target-ip-10-0-138-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:25:26Z"
    - latency: 1.895169ms
      message: 'network-check-target-ip-10-0-138-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:24:26Z"
    - latency: 1.975976ms
      message: 'network-check-target-ip-10-0-138-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:23:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T19:57:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4d19778d-1c4b-4371-a1c0-db9a4d2d35c4
    resourceVersion: "54518"
    uid: 4e3d5ff4-e2ce-453a-a614-05b2969f40ae
  spec:
    sourcePod: network-check-source-6947749cfc-nwqmb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:03:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 885.055µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:33:26Z"
    - latency: 1.80155ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:33:26Z"
    - latency: 927.205µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:32:26Z"
    - latency: 1.798598ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:32:26Z"
    - latency: 1.278159ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:31:26Z"
    - latency: 1.706258ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:31:26Z"
    - latency: 840.144µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:30:26Z"
    - latency: 1.60732ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:30:26Z"
    - latency: 918.411µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:29:26Z"
    - latency: 2.052944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:29:26Z"
kind: List
metadata:
  resourceVersion: ""