apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:34:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-58-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-58.ec2.internal
      uid: efd077bc-bfc4-47de-a7c0-90d651771731
    resourceVersion: "32036"
    uid: ff2409e7-9698-482f-8ba7-52b0cca1190b
  spec:
    sourcePod: network-check-source-dbd9cf844-sbrmf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:41:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.284689ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:48:42Z"
    - latency: 1.074541ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:47:42Z"
    - latency: 944.467µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:46:42Z"
    - latency: 956.848µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:45:42Z"
    - latency: 914.587µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:44:42Z"
    - latency: 892.028µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:43:42Z"
    - latency: 848.478µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:42:42Z"
    - latency: 973.878µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:41:42Z"
    - latency: 861.832µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:40:42Z"
    - latency: 933.386µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:39:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:34:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-58-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-58.ec2.internal
      uid: efd077bc-bfc4-47de-a7c0-90d651771731
    resourceVersion: "35597"
    uid: 599b7eb6-1861-4d00-9f0b-68b5dc4cd5c3
  spec:
    sourcePod: network-check-source-dbd9cf844-sbrmf
    targetEndpoint: aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:40:42Z"
      message: 'load-balancer-api-external: tcp connection to aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.533486ms
      message: 'load-balancer-api-external: tcp connection to aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:52:42Z"
    - latency: 6.225291ms
      message: 'load-balancer-api-external: resolved host name aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:52:42Z"
    - latency: 4.666564ms
      message: 'load-balancer-api-external: tcp connection to aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:51:42Z"
    - latency: 6.780848ms
      message: 'load-balancer-api-external: resolved host name aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:51:42Z"
    - latency: 6.54446ms
      message: 'load-balancer-api-external: tcp connection to aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:50:42Z"
    - latency: 6.33577ms
      message: 'load-balancer-api-external: resolved host name aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:50:42Z"
    - latency: 6.127697ms
      message: 'load-balancer-api-external: tcp connection to aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:49:42Z"
    - latency: 7.258893ms
      message: 'load-balancer-api-external: resolved host name aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:49:42Z"
    - latency: 3.725332ms
      message: 'load-balancer-api-external: tcp connection to aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:48:42Z"
    - latency: 6.63817ms
      message: 'load-balancer-api-external: resolved host name aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:48:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:34:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-58-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-58.ec2.internal
      uid: efd077bc-bfc4-47de-a7c0-90d651771731
    resourceVersion: "35596"
    uid: d2bba512-67da-4e89-b799-6acac18b4d8f
  spec:
    sourcePod: network-check-source-dbd9cf844-sbrmf
    targetEndpoint: aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:40:42Z"
      message: 'load-balancer-api-internal: tcp connection to aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.430615ms
      message: 'load-balancer-api-internal: tcp connection to aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:52:42Z"
    - latency: 6.318194ms
      message: 'load-balancer-api-internal: resolved host name aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:52:42Z"
    - latency: 4.627412ms
      message: 'load-balancer-api-internal: tcp connection to aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:51:42Z"
    - latency: 6.880064ms
      message: 'load-balancer-api-internal: resolved host name aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:51:42Z"
    - latency: 6.376248ms
      message: 'load-balancer-api-internal: tcp connection to aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:50:42Z"
    - latency: 6.448185ms
      message: 'load-balancer-api-internal: resolved host name aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:50:42Z"
    - latency: 5.893665ms
      message: 'load-balancer-api-internal: tcp connection to aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:49:42Z"
    - latency: 7.333636ms
      message: 'load-balancer-api-internal: resolved host name aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:49:42Z"
    - latency: 3.712768ms
      message: 'load-balancer-api-internal: tcp connection to aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:48:42Z"
    - latency: 6.673761ms
      message: 'load-balancer-api-internal: resolved host name aa17e885d34d24062bb74acb0d2cd626-3d94e82218a32b8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:48:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:34:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-58-to-network-check-target-ip-10-0-130-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-58.ec2.internal
      uid: efd077bc-bfc4-47de-a7c0-90d651771731
    resourceVersion: "32034"
    uid: 2569bcc4-2b29-40d9-8b65-b37c11b5a56e
  spec:
    sourcePod: network-check-source-dbd9cf844-sbrmf
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:41:42Z"
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.331114ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:48:42Z"
    - latency: 2.20364ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:47:42Z"
    - latency: 2.212813ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:46:42Z"
    - latency: 2.682971ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:45:42Z"
    - latency: 2.384878ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:44:42Z"
    - latency: 2.150519ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:43:42Z"
    - latency: 2.006624ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:42:42Z"
    - latency: 2.632762ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:41:42Z"
    - latency: 2.398112ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:40:42Z"
    - latency: 2.133789ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:39:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:34:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-58-to-network-check-target-ip-10-0-131-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-58.ec2.internal
      uid: efd077bc-bfc4-47de-a7c0-90d651771731
    resourceVersion: "32033"
    uid: bb74ea61-fe82-4454-a8f3-7e1a67a6a54c
  spec:
    sourcePod: network-check-source-dbd9cf844-sbrmf
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:41:42Z"
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.194169ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:48:42Z"
    - latency: 844.903µs
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:47:42Z"
    - latency: 1.130971ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:46:42Z"
    - latency: 1.186275ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:45:42Z"
    - latency: 868.824µs
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:44:42Z"
    - latency: 941.192µs
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:43:42Z"
    - latency: 830.005µs
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:42:42Z"
    - latency: 922.736µs
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:41:42Z"
    - latency: 806.046µs
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:40:42Z"
    - latency: 881.482µs
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:39:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:34:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-58-to-network-check-target-ip-10-0-140-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-58.ec2.internal
      uid: efd077bc-bfc4-47de-a7c0-90d651771731
    resourceVersion: "32035"
    uid: b64e6bee-839f-4db3-bdbc-41cb473bd867
  spec:
    sourcePod: network-check-source-dbd9cf844-sbrmf
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:41:42Z"
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.307363ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:48:42Z"
    - latency: 1.761337ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:47:42Z"
    - latency: 2.340795ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:46:42Z"
    - latency: 2.195302ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:45:42Z"
    - latency: 2.346848ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:44:42Z"
    - latency: 2.614281ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:43:42Z"
    - latency: 1.977828ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:42:42Z"
    - latency: 2.525507ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:41:42Z"
    - latency: 2.54821ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:40:42Z"
    - latency: 2.68686ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:39:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:34:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-58-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-58.ec2.internal
      uid: efd077bc-bfc4-47de-a7c0-90d651771731
    resourceVersion: "35595"
    uid: 0df5b7fa-e75a-4b6f-a62c-28d52516690d
  spec:
    sourcePod: network-check-source-dbd9cf844-sbrmf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:40:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.046535ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:52:42Z"
    - latency: 1.627909ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:52:42Z"
    - latency: 1.106927ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:51:42Z"
    - latency: 1.756494ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:51:42Z"
    - latency: 908.7µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:50:42Z"
    - latency: 1.794852ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:50:42Z"
    - latency: 847.241µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:49:42Z"
    - latency: 1.647599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:49:42Z"
    - latency: 1.024144ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:48:42Z"
    - latency: 2.27427ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:48:42Z"
kind: List
metadata:
  resourceVersion: ""