apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:13:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: 3e0f78ef-7f94-4b08-9402-499e09cad246
    resourceVersion: "15522"
    uid: 400300cf-fb79-4c2b-b450-651be6075d35
  spec:
    sourcePod: network-check-source-685456655f-zztm9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:20:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.985µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:34:13Z"
    - latency: 1.390735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:33:13Z"
    - latency: 1.389138ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:32:13Z"
    - latency: 997.208µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:31:13Z"
    - latency: 1.652692ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:30:13Z"
    - latency: 980.125µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:29:13Z"
    - latency: 1.431927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:28:13Z"
    - latency: 971.724µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:27:13Z"
    - latency: 1.264294ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:26:13Z"
    - latency: 879.75µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:25:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:13:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: 3e0f78ef-7f94-4b08-9402-499e09cad246
    resourceVersion: "16274"
    uid: 78dbdf4c-dd28-4f6c-a73f-21737fc45b22
  spec:
    sourcePod: network-check-source-685456655f-zztm9
    targetEndpoint: a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:19:13Z"
      message: 'load-balancer-api-external: tcp connection to a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.023963ms
      message: 'load-balancer-api-external: tcp connection to a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:37:13Z"
    - latency: 7.118989ms
      message: 'load-balancer-api-external: resolved host name a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:37:13Z"
    - latency: 3.660102ms
      message: 'load-balancer-api-external: tcp connection to a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:36:13Z"
    - latency: 7.273074ms
      message: 'load-balancer-api-external: resolved host name a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:36:13Z"
    - latency: 10.888646ms
      message: 'load-balancer-api-external: tcp connection to a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:35:13Z"
    - latency: 13.157188ms
      message: 'load-balancer-api-external: resolved host name a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:35:13Z"
    - latency: 7.230915ms
      message: 'load-balancer-api-external: tcp connection to a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:34:13Z"
    - latency: 7.080956ms
      message: 'load-balancer-api-external: resolved host name a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:34:13Z"
    - latency: 4.543085ms
      message: 'load-balancer-api-external: tcp connection to a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:33:13Z"
    - latency: 6.32362ms
      message: 'load-balancer-api-external: resolved host name a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:33:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:13:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: 3e0f78ef-7f94-4b08-9402-499e09cad246
    resourceVersion: "16275"
    uid: 886ec537-d935-4768-8f7e-dce308816212
  spec:
    sourcePod: network-check-source-685456655f-zztm9
    targetEndpoint: a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:19:13Z"
      message: 'load-balancer-api-internal: tcp connection to a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.044678ms
      message: 'load-balancer-api-internal: tcp connection to a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:37:13Z"
    - latency: 7.053755ms
      message: 'load-balancer-api-internal: resolved host name a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:37:13Z"
    - latency: 3.665477ms
      message: 'load-balancer-api-internal: tcp connection to a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:36:13Z"
    - latency: 7.243853ms
      message: 'load-balancer-api-internal: resolved host name a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:36:13Z"
    - latency: 6.350982ms
      message: 'load-balancer-api-internal: tcp connection to a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:35:13Z"
    - latency: 13.233796ms
      message: 'load-balancer-api-internal: resolved host name a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:35:13Z"
    - latency: 6.550208ms
      message: 'load-balancer-api-internal: tcp connection to a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:34:13Z"
    - latency: 7.123388ms
      message: 'load-balancer-api-internal: resolved host name a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:34:13Z"
    - latency: 4.452096ms
      message: 'load-balancer-api-internal: tcp connection to a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:33:13Z"
    - latency: 6.382681ms
      message: 'load-balancer-api-internal: resolved host name a6b8d9cae8c34409d96bd2be7c80169c-5227e051f2a3340d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:33:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:13:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-network-check-target-ip-10-0-136-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: 3e0f78ef-7f94-4b08-9402-499e09cad246
    resourceVersion: "15519"
    uid: bb453b48-27dd-4949-a2fa-5d94f943395f
  spec:
    sourcePod: network-check-source-685456655f-zztm9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:20:13Z"
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 790.864µs
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:34:13Z"
    - latency: 860.624µs
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:33:13Z"
    - latency: 852.676µs
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:32:13Z"
    - latency: 886.471µs
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:31:13Z"
    - latency: 1.023541ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:30:13Z"
    - latency: 867.284µs
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:29:13Z"
    - latency: 814.731µs
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:28:13Z"
    - latency: 903.786µs
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:27:13Z"
    - latency: 789.434µs
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:26:13Z"
    - latency: 1.108474ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:25:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:13:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-network-check-target-ip-10-0-138-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: 3e0f78ef-7f94-4b08-9402-499e09cad246
    resourceVersion: "15520"
    uid: 823baa86-7e7f-4252-b8d4-9416f432e444
  spec:
    sourcePod: network-check-source-685456655f-zztm9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:20:13Z"
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.000655ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:34:13Z"
    - latency: 2.44614ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:33:13Z"
    - latency: 2.004779ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:32:13Z"
    - latency: 1.946645ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:31:13Z"
    - latency: 2.053563ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:30:13Z"
    - latency: 1.849141ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:29:13Z"
    - latency: 1.925009ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:28:13Z"
    - latency: 1.86166ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:27:13Z"
    - latency: 1.776215ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:26:13Z"
    - latency: 1.995689ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:25:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:13:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-network-check-target-ip-10-0-143-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: 3e0f78ef-7f94-4b08-9402-499e09cad246
    resourceVersion: "15521"
    uid: 78a8eab4-c079-48d0-8424-84c11589b411
  spec:
    sourcePod: network-check-source-685456655f-zztm9
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:20:13Z"
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.164951ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:34:13Z"
    - latency: 1.872581ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:33:13Z"
    - latency: 1.887021ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:32:13Z"
    - latency: 2.10596ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:31:13Z"
    - latency: 2.129533ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:30:13Z"
    - latency: 1.854745ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:29:13Z"
    - latency: 2.195095ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:28:13Z"
    - latency: 2.041432ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:27:13Z"
    - latency: 2.38753ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:26:13Z"
    - latency: 2.165746ms
      message: 'network-check-target-ip-10-0-143-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:25:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T17:13:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-167-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-167.ec2.internal
      uid: 3e0f78ef-7f94-4b08-9402-499e09cad246
    resourceVersion: "16273"
    uid: 3b30adce-fced-4850-acb4-fbffaeafaad4
  spec:
    sourcePod: network-check-source-685456655f-zztm9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:19:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 767.232µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:37:13Z"
    - latency: 1.76287ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:37:13Z"
    - latency: 966.701µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:36:13Z"
    - latency: 1.978994ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:36:13Z"
    - latency: 1.137927ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:35:13Z"
    - latency: 1.668398ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:35:13Z"
    - latency: 1.146397ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:34:13Z"
    - latency: 1.806256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:34:13Z"
    - latency: 816.747µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:33:13Z"
    - latency: 1.80294ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:33:13Z"
kind: List
metadata:
  resourceVersion: ""