apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-6-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-6.ec2.internal
      uid: ff44847b-be9d-44e8-8d10-8aa9ff6b272a
    resourceVersion: "56046"
    uid: 385deda1-469c-475c-8b31-5a845457a337
  spec:
    sourcePod: network-check-source-65bdbbff45-9gwn8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:04:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 914.755µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:39:52Z"
    - latency: 1.030875ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:38:52Z"
    - latency: 1.025744ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:37:52Z"
    - latency: 1.369256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:36:52Z"
    - latency: 1.093902ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:35:52Z"
    - latency: 918.715µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:34:52Z"
    - latency: 931.058µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:33:52Z"
    - latency: 1.306808ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:32:52Z"
    - latency: 1.062701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:31:52Z"
    - latency: 1.044967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:30:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-6-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-6.ec2.internal
      uid: ff44847b-be9d-44e8-8d10-8aa9ff6b272a
    resourceVersion: "56048"
    uid: c6a48024-10da-4087-a094-8b6ac44a7388
  spec:
    sourcePod: network-check-source-65bdbbff45-9gwn8
    targetEndpoint: a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:03:52Z"
      message: 'load-balancer-api-external: tcp connection to a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.312567ms
      message: 'load-balancer-api-external: tcp connection to a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:39:52Z"
    - latency: 6.743219ms
      message: 'load-balancer-api-external: resolved host name a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:39:52Z"
    - latency: 4.348043ms
      message: 'load-balancer-api-external: tcp connection to a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:38:52Z"
    - latency: 6.602016ms
      message: 'load-balancer-api-external: resolved host name a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:38:52Z"
    - latency: 4.111246ms
      message: 'load-balancer-api-external: tcp connection to a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:37:52Z"
    - latency: 5.984378ms
      message: 'load-balancer-api-external: resolved host name a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:37:52Z"
    - latency: 4.640202ms
      message: 'load-balancer-api-external: tcp connection to a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:36:52Z"
    - latency: 7.277122ms
      message: 'load-balancer-api-external: resolved host name a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:36:52Z"
    - latency: 4.441042ms
      message: 'load-balancer-api-external: tcp connection to a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:35:52Z"
    - latency: 7.151974ms
      message: 'load-balancer-api-external: resolved host name a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-6-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-6.ec2.internal
      uid: ff44847b-be9d-44e8-8d10-8aa9ff6b272a
    resourceVersion: "56047"
    uid: 3e8f5157-72a5-48a8-bad1-45bc13b6ee49
  spec:
    sourcePod: network-check-source-65bdbbff45-9gwn8
    targetEndpoint: a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:03:52Z"
      message: 'load-balancer-api-internal: tcp connection to a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.731332ms
      message: 'load-balancer-api-internal: tcp connection to a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:39:52Z"
    - latency: 6.824416ms
      message: 'load-balancer-api-internal: resolved host name a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:39:52Z"
    - latency: 4.337244ms
      message: 'load-balancer-api-internal: tcp connection to a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:38:52Z"
    - latency: 6.575043ms
      message: 'load-balancer-api-internal: resolved host name a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:38:52Z"
    - latency: 4.205384ms
      message: 'load-balancer-api-internal: tcp connection to a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:37:52Z"
    - latency: 5.917936ms
      message: 'load-balancer-api-internal: resolved host name a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:37:52Z"
    - latency: 4.632034ms
      message: 'load-balancer-api-internal: tcp connection to a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:36:52Z"
    - latency: 7.338464ms
      message: 'load-balancer-api-internal: resolved host name a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:36:52Z"
    - latency: 4.444212ms
      message: 'load-balancer-api-internal: tcp connection to a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:35:52Z"
    - latency: 7.261325ms
      message: 'load-balancer-api-internal: resolved host name a9399d257de8646089293bdad4c363b0-dc42a09034a0708b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-6-to-network-check-target-ip-10-0-129-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-6.ec2.internal
      uid: ff44847b-be9d-44e8-8d10-8aa9ff6b272a
    resourceVersion: "56043"
    uid: 75664710-a45b-4c3c-96ff-8af22de10bfd
  spec:
    sourcePod: network-check-source-65bdbbff45-9gwn8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:04:52Z"
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.100989ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:39:52Z"
    - latency: 2.389393ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:38:52Z"
    - latency: 2.264253ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:37:52Z"
    - latency: 2.388054ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:36:52Z"
    - latency: 2.388888ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:35:52Z"
    - latency: 2.272392ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:34:52Z"
    - latency: 2.14265ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:33:52Z"
    - latency: 2.215331ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:32:52Z"
    - latency: 2.589004ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:31:52Z"
    - latency: 2.527531ms
      message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:30:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-6-to-network-check-target-ip-10-0-143-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-6.ec2.internal
      uid: ff44847b-be9d-44e8-8d10-8aa9ff6b272a
    resourceVersion: "56044"
    uid: 0c22f7a4-1a85-4d4b-84cb-bbadc2598015
  spec:
    sourcePod: network-check-source-65bdbbff45-9gwn8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:04:52Z"
      message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.372803ms
      message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:39:52Z"
    - latency: 2.328673ms
      message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:38:52Z"
    - latency: 2.326544ms
      message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:37:52Z"
    - latency: 2.78505ms
      message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:36:52Z"
    - latency: 2.331152ms
      message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:35:52Z"
    - latency: 2.118714ms
      message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:34:52Z"
    - latency: 1.984307ms
      message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:33:52Z"
    - latency: 2.313857ms
      message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:32:52Z"
    - latency: 2.48272ms
      message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:31:52Z"
    - latency: 2.53542ms
      message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:30:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-6-to-network-check-target-ip-10-0-143-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-6.ec2.internal
      uid: ff44847b-be9d-44e8-8d10-8aa9ff6b272a
    resourceVersion: "56042"
    uid: bfe95f8b-b55f-4663-81d7-b5e5d99033aa
  spec:
    sourcePod: network-check-source-65bdbbff45-9gwn8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:04:52Z"
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 993.903µs
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:39:52Z"
    - latency: 1.029532ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:38:52Z"
    - latency: 884.829µs
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:37:52Z"
    - latency: 920.254µs
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:36:52Z"
    - latency: 893.455µs
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:35:52Z"
    - latency: 938.241µs
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:34:52Z"
    - latency: 889.101µs
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:33:52Z"
    - latency: 1.330197ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:32:52Z"
    - latency: 929.943µs
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:31:52Z"
    - latency: 904.823µs
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:30:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:57:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-6-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-6.ec2.internal
      uid: ff44847b-be9d-44e8-8d10-8aa9ff6b272a
    resourceVersion: "56045"
    uid: 9e88b90a-c747-420a-93b8-46d5a7d70dd0
  spec:
    sourcePod: network-check-source-65bdbbff45-9gwn8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:03:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.230846ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:39:52Z"
    - latency: 1.766712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:39:52Z"
    - latency: 869.208µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:38:52Z"
    - latency: 1.567676ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:38:52Z"
    - latency: 791.563µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:37:52Z"
    - latency: 1.62806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:37:52Z"
    - latency: 1.079691ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:36:52Z"
    - latency: 1.874551ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:36:52Z"
    - latency: 1.028092ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T20:35:52Z"
    - latency: 1.622292ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T20:35:52Z"
kind: List
metadata:
  resourceVersion: ""