apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: c4225703-4ced-440f-869a-01f82db709d0
    resourceVersion: "37939"
    uid: 46e227a9-1bcc-4e19-985b-d0b983f7f0bf
  spec:
    sourcePod: network-check-source-7f44b6dd87-frn7j
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:28: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.712014ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:49:37Z"
    - latency: 1.979212ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:48:37Z"
    - latency: 1.419671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:47:37Z"
    - latency: 923.519µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:46:37Z"
    - latency: 1.030814ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:45:37Z"
    - latency: 914.472µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:44:37Z"
    - latency: 1.000488ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:43:37Z"
    - latency: 1.447716ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:42:37Z"
    - latency: 1.041535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:41:37Z"
    - latency: 1.15069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:40:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: c4225703-4ced-440f-869a-01f82db709d0
    resourceVersion: "39957"
    uid: c2d02872-5182-4a33-9cc4-b20cc5108336
  spec:
    sourcePod: network-check-source-7f44b6dd87-frn7j
    targetEndpoint: aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:27:37Z"
      message: 'load-balancer-api-external: tcp connection to aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.357598ms
      message: 'load-balancer-api-external: tcp connection to aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:51:37Z"
    - latency: 7.100846ms
      message: 'load-balancer-api-external: resolved host name aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:51:37Z"
    - latency: 4.570065ms
      message: 'load-balancer-api-external: tcp connection to aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:50:37Z"
    - latency: 8.155978ms
      message: 'load-balancer-api-external: resolved host name aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:50:37Z"
    - latency: 3.449657ms
      message: 'load-balancer-api-external: tcp connection to aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:49:37Z"
    - latency: 6.68364ms
      message: 'load-balancer-api-external: resolved host name aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:49:37Z"
    - latency: 6.686554ms
      message: 'load-balancer-api-external: tcp connection to aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:48:37Z"
    - latency: 7.718414ms
      message: 'load-balancer-api-external: resolved host name aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:48:37Z"
    - latency: 5.803812ms
      message: 'load-balancer-api-external: tcp connection to aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:47:37Z"
    - latency: 10.950405ms
      message: 'load-balancer-api-external: resolved host name aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:47:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: c4225703-4ced-440f-869a-01f82db709d0
    resourceVersion: "39958"
    uid: c802b7c6-78cb-4d2e-9fa6-1b75791ee95d
  spec:
    sourcePod: network-check-source-7f44b6dd87-frn7j
    targetEndpoint: aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:27:37Z"
      message: 'load-balancer-api-internal: tcp connection to aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.420183ms
      message: 'load-balancer-api-internal: tcp connection to aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:51:37Z"
    - latency: 8.420159ms
      message: 'load-balancer-api-internal: resolved host name aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:51:37Z"
    - latency: 6.026237ms
      message: 'load-balancer-api-internal: tcp connection to aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:50:37Z"
    - latency: 7.771964ms
      message: 'load-balancer-api-internal: resolved host name aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:50:37Z"
    - latency: 3.447844ms
      message: 'load-balancer-api-internal: tcp connection to aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:49:37Z"
    - latency: 6.76067ms
      message: 'load-balancer-api-internal: resolved host name aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:49:37Z"
    - latency: 4.210338ms
      message: 'load-balancer-api-internal: tcp connection to aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:48:37Z"
    - latency: 7.592131ms
      message: 'load-balancer-api-internal: resolved host name aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:48:37Z"
    - latency: 5.255462ms
      message: 'load-balancer-api-internal: tcp connection to aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:47:37Z"
    - latency: 7.673195ms
      message: 'load-balancer-api-internal: resolved host name aa7900aef1d05442d9e2488690e1d343-49d0cdc12b3652d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:47:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-network-check-target-ip-10-0-132-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: c4225703-4ced-440f-869a-01f82db709d0
    resourceVersion: "37936"
    uid: a30697df-ad37-4224-a884-f568dc61aeb8
  spec:
    sourcePod: network-check-source-7f44b6dd87-frn7j
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:28:37Z"
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.314µs
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:49:37Z"
    - latency: 2.10175ms
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:48:37Z"
    - latency: 2.244076ms
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:47:37Z"
    - latency: 859.707µs
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:46:37Z"
    - latency: 745.524µs
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:45:37Z"
    - latency: 983.418µs
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:44:37Z"
    - latency: 1.962317ms
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:43:37Z"
    - latency: 912.444µs
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:42:37Z"
    - latency: 1.199533ms
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:41:37Z"
    - latency: 1.454937ms
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:40:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-network-check-target-ip-10-0-143-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: c4225703-4ced-440f-869a-01f82db709d0
    resourceVersion: "37937"
    uid: 4f8afad1-03b8-4cee-a351-4e579b8c9b0f
  spec:
    sourcePod: network-check-source-7f44b6dd87-frn7j
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:28:37Z"
      message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.108708ms
      message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:49:37Z"
    - latency: 2.986147ms
      message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:48:37Z"
    - latency: 2.257111ms
      message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:47:37Z"
    - latency: 1.866216ms
      message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:46:37Z"
    - latency: 2.444272ms
      message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:45:37Z"
    - latency: 2.129711ms
      message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:44:37Z"
    - latency: 2.519276ms
      message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:43:37Z"
    - latency: 2.473632ms
      message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:42:37Z"
    - latency: 2.266788ms
      message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:41:37Z"
    - latency: 2.030998ms
      message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:40:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-network-check-target-ip-10-0-143-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: c4225703-4ced-440f-869a-01f82db709d0
    resourceVersion: "37938"
    uid: 0d0c3a5d-599a-45ff-96d8-37b8814d3269
  spec:
    sourcePod: network-check-source-7f44b6dd87-frn7j
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:28:37Z"
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.564342ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:49:37Z"
    - latency: 2.66862ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:48:37Z"
    - latency: 7.631617ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:47:37Z"
    - latency: 2.356198ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:46:37Z"
    - latency: 2.240767ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:45:37Z"
    - latency: 2.328236ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:44:37Z"
    - latency: 2.553317ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:43:37Z"
    - latency: 2.409924ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:42:37Z"
    - latency: 2.633668ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:41:37Z"
    - latency: 2.45998ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:40:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T11:21:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: c4225703-4ced-440f-869a-01f82db709d0
    resourceVersion: "39956"
    uid: ce2a9273-7270-48cc-8491-3da044ababbb
  spec:
    sourcePod: network-check-source-7f44b6dd87-frn7j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:27:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.89µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:51:37Z"
    - latency: 2.368394ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:51:37Z"
    - latency: 804.276µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:50:37Z"
    - latency: 2.184679ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:50:37Z"
    - latency: 799.772µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:49:37Z"
    - latency: 2.070563ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:49:37Z"
    - latency: 903.769µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:48:37Z"
    - latency: 2.475517ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:48:37Z"
    - latency: 1.880333ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:47:37Z"
    - latency: 1.183949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:47:37Z"
kind: List
metadata:
  resourceVersion: ""