apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:27:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-235-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-235.ec2.internal
      uid: a8817a24-8ac0-4f65-aac3-7fac4aeb6c84
    resourceVersion: "22280"
    uid: 018f99dc-6495-404f-ba9e-a945f1afc82b
  spec:
    sourcePod: network-check-source-56499946bc-mdcrp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:34:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.079871ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:48:17Z"
    - latency: 1.122457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:47:17Z"
    - latency: 1.171442ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:17Z"
    - latency: 1.059128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:17Z"
    - latency: 1.065268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:17Z"
    - latency: 1.00986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:17Z"
    - latency: 936.478µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:17Z"
    - latency: 1.006173ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:17Z"
    - latency: 1.022157ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:40:17Z"
    - latency: 1.028432ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:39:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:27:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-235-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-235.ec2.internal
      uid: a8817a24-8ac0-4f65-aac3-7fac4aeb6c84
    resourceVersion: "20893"
    uid: db43600e-ed75-47ad-a6ac-f2014b5c0808
  spec:
    sourcePod: network-check-source-56499946bc-mdcrp
    targetEndpoint: a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:33:17Z"
      message: 'load-balancer-api-external: tcp connection to a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.218189ms
      message: 'load-balancer-api-external: tcp connection to a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:17Z"
    - latency: 6.257134ms
      message: 'load-balancer-api-external: resolved host name a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:45:17Z"
    - latency: 4.564098ms
      message: 'load-balancer-api-external: tcp connection to a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:17Z"
    - latency: 6.867334ms
      message: 'load-balancer-api-external: resolved host name a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:44:17Z"
    - latency: 4.321083ms
      message: 'load-balancer-api-external: tcp connection to a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:17Z"
    - latency: 7.619792ms
      message: 'load-balancer-api-external: resolved host name a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:43:17Z"
    - latency: 5.362862ms
      message: 'load-balancer-api-external: tcp connection to a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:17Z"
    - latency: 6.774086ms
      message: 'load-balancer-api-external: resolved host name a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:42:17Z"
    - latency: 5.144647ms
      message: 'load-balancer-api-external: tcp connection to a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:17Z"
    - latency: 6.812385ms
      message: 'load-balancer-api-external: resolved host name a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:41:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:27:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-235-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-235.ec2.internal
      uid: a8817a24-8ac0-4f65-aac3-7fac4aeb6c84
    resourceVersion: "20894"
    uid: 431269c2-583c-4bd1-bed3-da355af8becf
  spec:
    sourcePod: network-check-source-56499946bc-mdcrp
    targetEndpoint: a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:33:17Z"
      message: 'load-balancer-api-internal: tcp connection to a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.233398ms
      message: 'load-balancer-api-internal: tcp connection to a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:17Z"
    - latency: 6.288002ms
      message: 'load-balancer-api-internal: resolved host name a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:45:17Z"
    - latency: 4.621544ms
      message: 'load-balancer-api-internal: tcp connection to a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:17Z"
    - latency: 6.924313ms
      message: 'load-balancer-api-internal: resolved host name a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:44:17Z"
    - latency: 4.135079ms
      message: 'load-balancer-api-internal: tcp connection to a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:17Z"
    - latency: 7.678593ms
      message: 'load-balancer-api-internal: resolved host name a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:43:17Z"
    - latency: 5.368093ms
      message: 'load-balancer-api-internal: tcp connection to a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:17Z"
    - latency: 6.696614ms
      message: 'load-balancer-api-internal: resolved host name a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:42:17Z"
    - latency: 5.109252ms
      message: 'load-balancer-api-internal: tcp connection to a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:17Z"
    - latency: 6.909383ms
      message: 'load-balancer-api-internal: resolved host name a422f225eeffc421c93fcb6c45c96d86-6f779365d5f73f70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:41:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:27:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-235-to-network-check-target-ip-10-0-131-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-235.ec2.internal
      uid: a8817a24-8ac0-4f65-aac3-7fac4aeb6c84
    resourceVersion: "22277"
    uid: 2b4d0677-1d8f-4535-a804-97d280d0996f
  spec:
    sourcePod: network-check-source-56499946bc-mdcrp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:34:17Z"
      message: 'network-check-target-ip-10-0-131-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.066µs
      message: 'network-check-target-ip-10-0-131-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:48:17Z"
    - latency: 1.694504ms
      message: 'network-check-target-ip-10-0-131-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:47:17Z"
    - latency: 1.296015ms
      message: 'network-check-target-ip-10-0-131-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:17Z"
    - latency: 889.281µs
      message: 'network-check-target-ip-10-0-131-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:17Z"
    - latency: 707.677µs
      message: 'network-check-target-ip-10-0-131-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:17Z"
    - latency: 795.107µs
      message: 'network-check-target-ip-10-0-131-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:17Z"
    - latency: 1.363891ms
      message: 'network-check-target-ip-10-0-131-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:17Z"
    - latency: 1.031059ms
      message: 'network-check-target-ip-10-0-131-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:17Z"
    - latency: 1.0635ms
      message: 'network-check-target-ip-10-0-131-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:40:17Z"
    - latency: 1.21514ms
      message: 'network-check-target-ip-10-0-131-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:39:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:27:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-235-to-network-check-target-ip-10-0-142-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-235.ec2.internal
      uid: a8817a24-8ac0-4f65-aac3-7fac4aeb6c84
    resourceVersion: "22278"
    uid: 235813fe-d2fe-4507-ba91-c2c48a25affd
  spec:
    sourcePod: network-check-source-56499946bc-mdcrp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:34:17Z"
      message: 'network-check-target-ip-10-0-142-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.891311ms
      message: 'network-check-target-ip-10-0-142-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:48:17Z"
    - latency: 2.001164ms
      message: 'network-check-target-ip-10-0-142-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:47:17Z"
    - latency: 1.974833ms
      message: 'network-check-target-ip-10-0-142-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:17Z"
    - latency: 1.885115ms
      message: 'network-check-target-ip-10-0-142-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:17Z"
    - latency: 1.77896ms
      message: 'network-check-target-ip-10-0-142-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:17Z"
    - latency: 1.85049ms
      message: 'network-check-target-ip-10-0-142-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:17Z"
    - latency: 2.101713ms
      message: 'network-check-target-ip-10-0-142-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:17Z"
    - latency: 1.874698ms
      message: 'network-check-target-ip-10-0-142-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:17Z"
    - latency: 1.860002ms
      message: 'network-check-target-ip-10-0-142-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:40:17Z"
    - latency: 1.963447ms
      message: 'network-check-target-ip-10-0-142-179: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:39:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:27:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-235-to-network-check-target-ip-10-0-143-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-235.ec2.internal
      uid: a8817a24-8ac0-4f65-aac3-7fac4aeb6c84
    resourceVersion: "22279"
    uid: 3efc243d-ead7-4d96-993b-bd2364b0a91c
  spec:
    sourcePod: network-check-source-56499946bc-mdcrp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:34:17Z"
      message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.291338ms
      message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:48:17Z"
    - latency: 2.255528ms
      message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:47:17Z"
    - latency: 2.131189ms
      message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:17Z"
    - latency: 2.084529ms
      message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:17Z"
    - latency: 2.141877ms
      message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:17Z"
    - latency: 2.070222ms
      message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:17Z"
    - latency: 2.294824ms
      message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:17Z"
    - latency: 2.266413ms
      message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:17Z"
    - latency: 2.266912ms
      message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:40:17Z"
    - latency: 2.161931ms
      message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:39:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:27:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-235-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-235.ec2.internal
      uid: a8817a24-8ac0-4f65-aac3-7fac4aeb6c84
    resourceVersion: "20892"
    uid: 3617c2bf-99e9-44f0-a2f2-574b5806aea8
  spec:
    sourcePod: network-check-source-56499946bc-mdcrp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:33:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.085737ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:17Z"
    - latency: 1.685421ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:45:17Z"
    - latency: 990.581µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:17Z"
    - latency: 1.736159ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:44:17Z"
    - latency: 867.053µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:17Z"
    - latency: 1.683734ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:43:17Z"
    - latency: 799.191µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:17Z"
    - latency: 2.182553ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:42:17Z"
    - latency: 988.216µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:17Z"
    - latency: 1.858462ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:41:17Z"
kind: List
metadata:
  resourceVersion: ""