apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: d8703970-a39a-48e7-bc4b-c3c9404c2959
    resourceVersion: "60443"
    uid: a5a04ca9-b53d-4e6c-9a81-a41141da34c1
  spec:
    sourcePod: network-check-source-869dcfcdcd-zh6fk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:08:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.204208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:43:22Z"
    - latency: 1.432159ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:42:22Z"
    - latency: 1.201333ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:41:22Z"
    - latency: 1.164217ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:40:22Z"
    - latency: 1.158652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:39:22Z"
    - latency: 947.029µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:38:22Z"
    - latency: 909.73µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:37:22Z"
    - latency: 1.386257ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:36:22Z"
    - latency: 1.146717ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:35:22Z"
    - latency: 1.460161ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:34:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: d8703970-a39a-48e7-bc4b-c3c9404c2959
    resourceVersion: "60445"
    uid: 0f685924-7fc2-4ca8-8d5a-7e03a7ba1acf
  spec:
    sourcePod: network-check-source-869dcfcdcd-zh6fk
    targetEndpoint: a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:07:22Z"
      message: 'load-balancer-api-external: tcp connection to a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.259538ms
      message: 'load-balancer-api-external: tcp connection to a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:43:22Z"
    - latency: 9.421545ms
      message: 'load-balancer-api-external: resolved host name a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:43:22Z"
    - latency: 5.744761ms
      message: 'load-balancer-api-external: tcp connection to a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:42:22Z"
    - latency: 8.921409ms
      message: 'load-balancer-api-external: resolved host name a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:42:22Z"
    - latency: 4.85878ms
      message: 'load-balancer-api-external: tcp connection to a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:41:22Z"
    - latency: 8.059024ms
      message: 'load-balancer-api-external: resolved host name a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:41:22Z"
    - latency: 4.11386ms
      message: 'load-balancer-api-external: tcp connection to a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:40:22Z"
    - latency: 8.803368ms
      message: 'load-balancer-api-external: resolved host name a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:40:22Z"
    - latency: 5.091695ms
      message: 'load-balancer-api-external: tcp connection to a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:39:22Z"
    - latency: 7.926175ms
      message: 'load-balancer-api-external: resolved host name a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:39:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: d8703970-a39a-48e7-bc4b-c3c9404c2959
    resourceVersion: "60444"
    uid: d5bfaa40-0628-4b8e-a5aa-34d5d35436c9
  spec:
    sourcePod: network-check-source-869dcfcdcd-zh6fk
    targetEndpoint: a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:07:22Z"
      message: 'load-balancer-api-internal: tcp connection to a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.252587ms
      message: 'load-balancer-api-internal: tcp connection to a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:43:22Z"
    - latency: 9.514081ms
      message: 'load-balancer-api-internal: resolved host name a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:43:22Z"
    - latency: 5.766559ms
      message: 'load-balancer-api-internal: tcp connection to a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:42:22Z"
    - latency: 8.847322ms
      message: 'load-balancer-api-internal: resolved host name a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:42:22Z"
    - latency: 4.676518ms
      message: 'load-balancer-api-internal: tcp connection to a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:41:22Z"
    - latency: 8.166768ms
      message: 'load-balancer-api-internal: resolved host name a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:41:22Z"
    - latency: 5.439209ms
      message: 'load-balancer-api-internal: tcp connection to a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:40:22Z"
    - latency: 8.873819ms
      message: 'load-balancer-api-internal: resolved host name a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:40:22Z"
    - latency: 5.080042ms
      message: 'load-balancer-api-internal: tcp connection to a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:39:22Z"
    - latency: 8.030998ms
      message: 'load-balancer-api-internal: resolved host name a3fd251aedaf24524bfacf0bcea8b098-2fb32bf69a547683.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:39:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-network-check-target-ip-10-0-128-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: d8703970-a39a-48e7-bc4b-c3c9404c2959
    resourceVersion: "60439"
    uid: 89197a2d-17a7-4b20-b8b9-9e74e15a1dd5
  spec:
    sourcePod: network-check-source-869dcfcdcd-zh6fk
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:08:22Z"
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.05002ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:43:22Z"
    - latency: 1.928854ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:42:22Z"
    - latency: 2.125313ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:41:22Z"
    - latency: 1.595517ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:40:22Z"
    - latency: 2.173957ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:39:22Z"
    - latency: 2.036321ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:38:22Z"
    - latency: 1.721531ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:37:22Z"
    - latency: 2.089983ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:36:22Z"
    - latency: 2.151385ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:35:22Z"
    - latency: 2.049128ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:34:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-network-check-target-ip-10-0-133-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: d8703970-a39a-48e7-bc4b-c3c9404c2959
    resourceVersion: "60440"
    uid: a0c820b7-cadd-4aee-b2ff-6c2019f570d7
  spec:
    sourcePod: network-check-source-869dcfcdcd-zh6fk
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:08:22Z"
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.613237ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:43:22Z"
    - latency: 1.643286ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:42:22Z"
    - latency: 914.421µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:41:22Z"
    - latency: 862.624µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:40:22Z"
    - latency: 827.348µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:39:22Z"
    - latency: 744.262µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:38:22Z"
    - latency: 1.094053ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:37:22Z"
    - latency: 980.82µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:36:22Z"
    - latency: 884.07µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:35:22Z"
    - latency: 768.105µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:34:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-network-check-target-ip-10-0-135-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: d8703970-a39a-48e7-bc4b-c3c9404c2959
    resourceVersion: "60442"
    uid: b2e409cd-98ab-4b6e-95fa-d38672bc2b6e
  spec:
    sourcePod: network-check-source-869dcfcdcd-zh6fk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:08:22Z"
      message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.294063ms
      message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:43:22Z"
    - latency: 2.304691ms
      message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:42:22Z"
    - latency: 2.64823ms
      message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:41:22Z"
    - latency: 2.182853ms
      message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:40:22Z"
    - latency: 2.61189ms
      message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:39:22Z"
    - latency: 2.371213ms
      message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:38:22Z"
    - latency: 2.323508ms
      message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:37:22Z"
    - latency: 2.473574ms
      message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:36:22Z"
    - latency: 2.083128ms
      message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:35:22Z"
    - latency: 2.645704ms
      message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:34:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: d8703970-a39a-48e7-bc4b-c3c9404c2959
    resourceVersion: "60441"
    uid: 08b97df2-652d-4484-837e-0ac1516855d7
  spec:
    sourcePod: network-check-source-869dcfcdcd-zh6fk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:07:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.715µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:43:22Z"
    - latency: 2.040934ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:43:22Z"
    - latency: 859.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:42:22Z"
    - latency: 1.991983ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:42:22Z"
    - latency: 779.828µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:41:22Z"
    - latency: 1.820195ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:41:22Z"
    - latency: 955.406µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:40:22Z"
    - latency: 1.633863ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:40:22Z"
    - latency: 850.627µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:39:22Z"
    - latency: 1.615903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:39:22Z"
kind: List
metadata:
  resourceVersion: ""