apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-41-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-41.ec2.internal
      uid: 6df5675e-8508-4381-a7eb-d65e8d1d0d35
    resourceVersion: "33848"
    uid: be7659bd-77c5-47f1-bbc6-a4639d4d97ea
  spec:
    sourcePod: network-check-source-7cbc45fddc-gxdnl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:07:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 914.527µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:42:40Z"
    - latency: 1.053952ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:41:40Z"
    - latency: 1.238134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:40:40Z"
    - latency: 1.017957ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:39:40Z"
    - latency: 943.696µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:38:40Z"
    - latency: 825.145µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:37:40Z"
    - latency: 1.067969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:36:40Z"
    - latency: 851.689µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:35:40Z"
    - latency: 1.071649ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:34:40Z"
    - latency: 1.262019ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:33:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-41-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-41.ec2.internal
      uid: 6df5675e-8508-4381-a7eb-d65e8d1d0d35
    resourceVersion: "33849"
    uid: c060dc09-73be-4ad4-8b05-493567c4c074
  spec:
    sourcePod: network-check-source-7cbc45fddc-gxdnl
    targetEndpoint: a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:06:40Z"
      message: 'load-balancer-api-external: tcp connection to a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.118172ms
      message: 'load-balancer-api-external: tcp connection to a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:42:40Z"
    - latency: 8.824976ms
      message: 'load-balancer-api-external: resolved host name a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:42:40Z"
    - latency: 4.868196ms
      message: 'load-balancer-api-external: tcp connection to a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:41:40Z"
    - latency: 8.119089ms
      message: 'load-balancer-api-external: resolved host name a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:41:40Z"
    - latency: 3.917164ms
      message: 'load-balancer-api-external: tcp connection to a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:40:40Z"
    - latency: 8.097942ms
      message: 'load-balancer-api-external: resolved host name a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:40:40Z"
    - latency: 4.041494ms
      message: 'load-balancer-api-external: tcp connection to a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:39:40Z"
    - latency: 8.178233ms
      message: 'load-balancer-api-external: resolved host name a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:39:40Z"
    - latency: 4.661675ms
      message: 'load-balancer-api-external: tcp connection to a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:38:40Z"
    - latency: 8.056982ms
      message: 'load-balancer-api-external: resolved host name a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:38:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-41-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-41.ec2.internal
      uid: 6df5675e-8508-4381-a7eb-d65e8d1d0d35
    resourceVersion: "33850"
    uid: 38f469ed-8c98-4a27-9cfc-5a00b21bffee
  spec:
    sourcePod: network-check-source-7cbc45fddc-gxdnl
    targetEndpoint: a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:06:40Z"
      message: 'load-balancer-api-internal: tcp connection to a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.091568ms
      message: 'load-balancer-api-internal: tcp connection to a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:42:40Z"
    - latency: 8.815181ms
      message: 'load-balancer-api-internal: resolved host name a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:42:40Z"
    - latency: 4.650802ms
      message: 'load-balancer-api-internal: tcp connection to a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:41:40Z"
    - latency: 8.166735ms
      message: 'load-balancer-api-internal: resolved host name a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:41:40Z"
    - latency: 3.720197ms
      message: 'load-balancer-api-internal: tcp connection to a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:40:40Z"
    - latency: 8.176339ms
      message: 'load-balancer-api-internal: resolved host name a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:40:40Z"
    - latency: 5.540566ms
      message: 'load-balancer-api-internal: tcp connection to a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:39:40Z"
    - latency: 8.198524ms
      message: 'load-balancer-api-internal: resolved host name a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:39:40Z"
    - latency: 4.704243ms
      message: 'load-balancer-api-internal: tcp connection to a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:38:40Z"
    - latency: 8.139777ms
      message: 'load-balancer-api-internal: resolved host name a8581b5aeab4648bb961a726525ca22a-3a9aabd06ff1da41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:38:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-41-to-network-check-target-ip-10-0-132-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-41.ec2.internal
      uid: 6df5675e-8508-4381-a7eb-d65e8d1d0d35
    resourceVersion: "33847"
    uid: 0c773042-9f08-4ae5-8c1d-5b8c244dbbe2
  spec:
    sourcePod: network-check-source-7cbc45fddc-gxdnl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:07:40Z"
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 893.529µs
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:42:40Z"
    - latency: 857.64µs
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:41:40Z"
    - latency: 755.892µs
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:40:40Z"
    - latency: 920.755µs
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:39:40Z"
    - latency: 827.365µs
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:38:40Z"
    - latency: 866.376µs
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:37:40Z"
    - latency: 865.338µs
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:36:40Z"
    - latency: 782.856µs
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:35:40Z"
    - latency: 1.092296ms
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:34:40Z"
    - latency: 846.739µs
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:33:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-41-to-network-check-target-ip-10-0-135-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-41.ec2.internal
      uid: 6df5675e-8508-4381-a7eb-d65e8d1d0d35
    resourceVersion: "33845"
    uid: a1db73b1-f002-474b-a6f3-7d14071263e8
  spec:
    sourcePod: network-check-source-7cbc45fddc-gxdnl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:07:40Z"
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.331737ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:42:40Z"
    - latency: 2.297342ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:41:40Z"
    - latency: 2.312058ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:40:40Z"
    - latency: 2.391922ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:39:40Z"
    - latency: 2.353525ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:38:40Z"
    - latency: 2.289811ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:37:40Z"
    - latency: 2.274671ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:36:40Z"
    - latency: 2.15514ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:35:40Z"
    - latency: 2.290982ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:34:40Z"
    - latency: 2.063276ms
      message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:33:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-41-to-network-check-target-ip-10-0-142-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-41.ec2.internal
      uid: 6df5675e-8508-4381-a7eb-d65e8d1d0d35
    resourceVersion: "33844"
    uid: 1eec6d86-a08e-45f1-9c43-50e8364f7267
  spec:
    sourcePod: network-check-source-7cbc45fddc-gxdnl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:07:40Z"
      message: 'network-check-target-ip-10-0-142-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.91892ms
      message: 'network-check-target-ip-10-0-142-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:42:40Z"
    - latency: 1.933475ms
      message: 'network-check-target-ip-10-0-142-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:41:40Z"
    - latency: 2.038211ms
      message: 'network-check-target-ip-10-0-142-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:40:40Z"
    - latency: 2.078185ms
      message: 'network-check-target-ip-10-0-142-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:39:40Z"
    - latency: 2.151721ms
      message: 'network-check-target-ip-10-0-142-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:38:40Z"
    - latency: 1.965981ms
      message: 'network-check-target-ip-10-0-142-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:37:40Z"
    - latency: 1.978672ms
      message: 'network-check-target-ip-10-0-142-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:36:40Z"
    - latency: 1.959417ms
      message: 'network-check-target-ip-10-0-142-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:35:40Z"
    - latency: 2.067533ms
      message: 'network-check-target-ip-10-0-142-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:34:40Z"
    - latency: 2.041659ms
      message: 'network-check-target-ip-10-0-142-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:33:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-41-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-41.ec2.internal
      uid: 6df5675e-8508-4381-a7eb-d65e8d1d0d35
    resourceVersion: "33846"
    uid: 85852191-0193-4be2-89ed-6e27e1373b4d
  spec:
    sourcePod: network-check-source-7cbc45fddc-gxdnl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:06:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.313336ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:42:40Z"
    - latency: 1.695065ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:42:40Z"
    - latency: 921.212µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:41:40Z"
    - latency: 1.743389ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:41:40Z"
    - latency: 863.484µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:40:40Z"
    - latency: 1.622756ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:40:40Z"
    - latency: 909.289µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:39:40Z"
    - latency: 1.537871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:39:40Z"
    - latency: 871.446µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:38:40Z"
    - latency: 1.636041ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:38:40Z"
kind: List
metadata:
  resourceVersion: ""