apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:57:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-182-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-182.ec2.internal
      uid: ab9639f5-51ba-4c9a-8842-e80385e68d91
    resourceVersion: "70143"
    uid: 30d69b07-3074-45b9-b48a-0e66e7403699
  spec:
    sourcePod: network-check-source-7d88cb55d8-nwh74
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:04:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.355689ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:46:23Z"
    - latency: 888.393µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:45:23Z"
    - latency: 1.052659ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:44:23Z"
    - latency: 909.381µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:43:23Z"
    - latency: 987.259µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:42:23Z"
    - latency: 1.124925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:41:23Z"
    - latency: 1.107946ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:40:23Z"
    - latency: 986.709µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:39:23Z"
    - latency: 1.468165ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:38:23Z"
    - latency: 1.315749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:37:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:57:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-182-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-182.ec2.internal
      uid: ab9639f5-51ba-4c9a-8842-e80385e68d91
    resourceVersion: "68961"
    uid: 66951f93-ceeb-48c0-9614-fd2f8eb73e3a
  spec:
    sourcePod: network-check-source-7d88cb55d8-nwh74
    targetEndpoint: a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:03:23Z"
      message: 'load-balancer-api-external: tcp connection to a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.458276ms
      message: 'load-balancer-api-external: tcp connection to a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:45:23Z"
    - latency: 9.351918ms
      message: 'load-balancer-api-external: resolved host name a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:45:23Z"
    - latency: 5.626892ms
      message: 'load-balancer-api-external: tcp connection to a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:44:23Z"
    - latency: 9.612612ms
      message: 'load-balancer-api-external: resolved host name a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:44:23Z"
    - latency: 5.493364ms
      message: 'load-balancer-api-external: tcp connection to a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:43:23Z"
    - latency: 12.784999ms
      message: 'load-balancer-api-external: resolved host name a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:43:23Z"
    - latency: 5.026942ms
      message: 'load-balancer-api-external: tcp connection to a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:42:23Z"
    - latency: 9.594001ms
      message: 'load-balancer-api-external: resolved host name a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:42:23Z"
    - latency: 4.169668ms
      message: 'load-balancer-api-external: tcp connection to a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:41:23Z"
    - latency: 8.006511ms
      message: 'load-balancer-api-external: resolved host name a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:41:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:57:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-182-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-182.ec2.internal
      uid: ab9639f5-51ba-4c9a-8842-e80385e68d91
    resourceVersion: "68959"
    uid: 749fe27e-a8ea-451e-bff9-6d771968e909
  spec:
    sourcePod: network-check-source-7d88cb55d8-nwh74
    targetEndpoint: a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:03:23Z"
      message: 'load-balancer-api-internal: tcp connection to a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.435909ms
      message: 'load-balancer-api-internal: tcp connection to a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:45:23Z"
    - latency: 9.377409ms
      message: 'load-balancer-api-internal: resolved host name a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:45:23Z"
    - latency: 5.620087ms
      message: 'load-balancer-api-internal: tcp connection to a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:44:23Z"
    - latency: 9.732013ms
      message: 'load-balancer-api-internal: resolved host name a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:44:23Z"
    - latency: 5.486292ms
      message: 'load-balancer-api-internal: tcp connection to a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:43:23Z"
    - latency: 12.740661ms
      message: 'load-balancer-api-internal: resolved host name a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:43:23Z"
    - latency: 4.881968ms
      message: 'load-balancer-api-internal: tcp connection to a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:42:23Z"
    - latency: 9.649581ms
      message: 'load-balancer-api-internal: resolved host name a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:42:23Z"
    - latency: 6.941327ms
      message: 'load-balancer-api-internal: tcp connection to a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:41:23Z"
    - latency: 8.166972ms
      message: 'load-balancer-api-internal: resolved host name a3daaeea1a5a04e66baf953b9d782375-3a816c607c7a18bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:41:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:57:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-182-to-network-check-target-ip-10-0-130-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-182.ec2.internal
      uid: ab9639f5-51ba-4c9a-8842-e80385e68d91
    resourceVersion: "70142"
    uid: 0e92eeec-02b6-4759-aeaa-d3dd586c4ac8
  spec:
    sourcePod: network-check-source-7d88cb55d8-nwh74
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:04:23Z"
      message: 'network-check-target-ip-10-0-130-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.712596ms
      message: 'network-check-target-ip-10-0-130-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:46:23Z"
    - latency: 2.560412ms
      message: 'network-check-target-ip-10-0-130-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:45:23Z"
    - latency: 2.030281ms
      message: 'network-check-target-ip-10-0-130-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:44:23Z"
    - latency: 1.8566ms
      message: 'network-check-target-ip-10-0-130-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:43:23Z"
    - latency: 2.452747ms
      message: 'network-check-target-ip-10-0-130-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:42:23Z"
    - latency: 2.256669ms
      message: 'network-check-target-ip-10-0-130-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:41:23Z"
    - latency: 2.148251ms
      message: 'network-check-target-ip-10-0-130-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:40:23Z"
    - latency: 2.340131ms
      message: 'network-check-target-ip-10-0-130-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:39:23Z"
    - latency: 2.150062ms
      message: 'network-check-target-ip-10-0-130-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:38:23Z"
    - latency: 2.738038ms
      message: 'network-check-target-ip-10-0-130-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:37:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:57:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-182-to-network-check-target-ip-10-0-138-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-182.ec2.internal
      uid: ab9639f5-51ba-4c9a-8842-e80385e68d91
    resourceVersion: "70141"
    uid: f462894e-223d-461e-8238-86b64546f684
  spec:
    sourcePod: network-check-source-7d88cb55d8-nwh74
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:04:23Z"
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.402108ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:46:23Z"
    - latency: 2.277524ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:45:23Z"
    - latency: 2.169441ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:44:23Z"
    - latency: 2.349279ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:43:23Z"
    - latency: 2.308869ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:42:23Z"
    - latency: 2.569732ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:41:23Z"
    - latency: 2.188964ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:40:23Z"
    - latency: 1.996251ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:39:23Z"
    - latency: 2.582021ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:38:23Z"
    - latency: 2.722312ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:37:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:57:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-182-to-network-check-target-ip-10-0-142-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-182.ec2.internal
      uid: ab9639f5-51ba-4c9a-8842-e80385e68d91
    resourceVersion: "70140"
    uid: e44f1aef-ae37-492b-95c6-f689d96b0642
  spec:
    sourcePod: network-check-source-7d88cb55d8-nwh74
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:04:23Z"
      message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.856µs
      message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:46:23Z"
    - latency: 1.847316ms
      message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:45:23Z"
    - latency: 1.438445ms
      message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:44:23Z"
    - latency: 878.936µs
      message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:43:23Z"
    - latency: 1.134172ms
      message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:42:23Z"
    - latency: 1.064205ms
      message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:41:23Z"
    - latency: 873.877µs
      message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:40:23Z"
    - latency: 865.657µs
      message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:39:23Z"
    - latency: 871.654µs
      message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:38:23Z"
    - latency: 1.549703ms
      message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:37:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T17:57:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-182-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-182.ec2.internal
      uid: ab9639f5-51ba-4c9a-8842-e80385e68d91
    resourceVersion: "68958"
    uid: 40e5a4e7-a14a-4c1a-ac78-e34bd78326bb
  spec:
    sourcePod: network-check-source-7d88cb55d8-nwh74
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:03:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.629µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:45:23Z"
    - latency: 2.233703ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:45:23Z"
    - latency: 911.326µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:44:23Z"
    - latency: 1.813908ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:44:23Z"
    - latency: 949.421µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:43:23Z"
    - latency: 1.903639ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:43:23Z"
    - latency: 963.337µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:42:23Z"
    - latency: 1.926298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:42:23Z"
    - latency: 1.245266ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T18:41:23Z"
    - latency: 2.183962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T18:41:23Z"
kind: List
metadata:
  resourceVersion: ""