apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:03:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-54-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-54.ec2.internal
      uid: 5763ec9f-d1a1-420c-8bf1-ea6edb35054a
    resourceVersion: "69865"
    uid: aa76e37f-663c-4201-9cf9-b39088d817b8
  spec:
    sourcePod: network-check-source-7d88cb55d8-72w9l
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:10:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.065323ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:52:25Z"
    - latency: 1.152082ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:51:25Z"
    - latency: 1.046842ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:50:25Z"
    - latency: 971.506µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:49:25Z"
    - latency: 967.463µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:48:25Z"
    - latency: 1.029014ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:47:25Z"
    - latency: 1.478658ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:46:25Z"
    - latency: 919.729µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:45:25Z"
    - latency: 943.021µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:44:25Z"
    - latency: 967.637µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:43:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:03:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-54-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-54.ec2.internal
      uid: 5763ec9f-d1a1-420c-8bf1-ea6edb35054a
    resourceVersion: "79569"
    uid: 777719de-7e24-4bfd-b0ea-71bc47e964b4
  spec:
    sourcePod: network-check-source-7d88cb55d8-72w9l
    targetEndpoint: aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:09:25Z"
      message: 'load-balancer-api-external: tcp connection to aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.315974ms
      message: 'load-balancer-api-external: tcp connection to aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:57:25Z"
    - latency: 8.809484ms
      message: 'load-balancer-api-external: resolved host name aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:57:25Z"
    - latency: 5.407423ms
      message: 'load-balancer-api-external: tcp connection to aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:56:25Z"
    - latency: 8.107341ms
      message: 'load-balancer-api-external: resolved host name aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:56:25Z"
    - latency: 3.081257ms
      message: 'load-balancer-api-external: tcp connection to aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:55:25Z"
    - latency: 7.951485ms
      message: 'load-balancer-api-external: resolved host name aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:55:25Z"
    - latency: 4.952793ms
      message: 'load-balancer-api-external: tcp connection to aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:54:25Z"
    - latency: 8.293732ms
      message: 'load-balancer-api-external: resolved host name aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:54:25Z"
    - latency: 5.363837ms
      message: 'load-balancer-api-external: tcp connection to aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:53:25Z"
    - latency: 6.369162ms
      message: 'load-balancer-api-external: resolved host name aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:53:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:03:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-54-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-54.ec2.internal
      uid: 5763ec9f-d1a1-420c-8bf1-ea6edb35054a
    resourceVersion: "79568"
    uid: 9d207f0d-c949-47c1-ac41-00431f478b88
  spec:
    sourcePod: network-check-source-7d88cb55d8-72w9l
    targetEndpoint: aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:09:25Z"
      message: 'load-balancer-api-internal: tcp connection to aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.296982ms
      message: 'load-balancer-api-internal: tcp connection to aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:57:25Z"
    - latency: 8.777626ms
      message: 'load-balancer-api-internal: resolved host name aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:57:25Z"
    - latency: 5.367324ms
      message: 'load-balancer-api-internal: tcp connection to aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:56:25Z"
    - latency: 8.15521ms
      message: 'load-balancer-api-internal: resolved host name aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:56:25Z"
    - latency: 5.407056ms
      message: 'load-balancer-api-internal: tcp connection to aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:55:25Z"
    - latency: 8.068689ms
      message: 'load-balancer-api-internal: resolved host name aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:55:25Z"
    - latency: 5.01833ms
      message: 'load-balancer-api-internal: tcp connection to aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:54:25Z"
    - latency: 8.346412ms
      message: 'load-balancer-api-internal: resolved host name aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:54:25Z"
    - latency: 5.382418ms
      message: 'load-balancer-api-internal: tcp connection to aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:53:25Z"
    - latency: 6.282452ms
      message: 'load-balancer-api-internal: resolved host name aeee74fe68e6940b183b23eb778123a6-059361bcf7c2f970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:53:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:03:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-54-to-network-check-target-ip-10-0-128-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-54.ec2.internal
      uid: 5763ec9f-d1a1-420c-8bf1-ea6edb35054a
    resourceVersion: "69864"
    uid: 6b110fd1-a7df-419a-a751-4e301a11d242
  spec:
    sourcePod: network-check-source-7d88cb55d8-72w9l
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:10:25Z"
      message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.496351ms
      message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:52:25Z"
    - latency: 2.34764ms
      message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:51:25Z"
    - latency: 2.488604ms
      message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:50:25Z"
    - latency: 2.484742ms
      message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:49:25Z"
    - latency: 2.394807ms
      message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:48:25Z"
    - latency: 2.021742ms
      message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:47:25Z"
    - latency: 2.223794ms
      message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:46:25Z"
    - latency: 2.460955ms
      message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:45:25Z"
    - latency: 2.078356ms
      message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:44:25Z"
    - latency: 2.326578ms
      message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:43:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:03:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-54-to-network-check-target-ip-10-0-136-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-54.ec2.internal
      uid: 5763ec9f-d1a1-420c-8bf1-ea6edb35054a
    resourceVersion: "69863"
    uid: 128d869a-2467-418f-8c76-874b859c2311
  spec:
    sourcePod: network-check-source-7d88cb55d8-72w9l
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:10:25Z"
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.203925ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:52:25Z"
    - latency: 2.392763ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:51:25Z"
    - latency: 2.424072ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:50:25Z"
    - latency: 2.395281ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:49:25Z"
    - latency: 2.315269ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:48:25Z"
    - latency: 1.884842ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:47:25Z"
    - latency: 2.130886ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:46:25Z"
    - latency: 2.187162ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:45:25Z"
    - latency: 2.622627ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:44:25Z"
    - latency: 2.311498ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:43:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:03:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-54-to-network-check-target-ip-10-0-139-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-54.ec2.internal
      uid: 5763ec9f-d1a1-420c-8bf1-ea6edb35054a
    resourceVersion: "69862"
    uid: b2c32cf1-b3ac-4553-a584-0ba1854b1c78
  spec:
    sourcePod: network-check-source-7d88cb55d8-72w9l
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:10:25Z"
      message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.978µs
      message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:52:25Z"
    - latency: 986.724µs
      message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:51:25Z"
    - latency: 796.018µs
      message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:50:25Z"
    - latency: 904.61µs
      message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:49:25Z"
    - latency: 937.329µs
      message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:48:25Z"
    - latency: 921.023µs
      message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:47:25Z"
    - latency: 883.408µs
      message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:46:25Z"
    - latency: 826.738µs
      message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:45:25Z"
    - latency: 1.026374ms
      message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:44:25Z"
    - latency: 904.757µs
      message: 'network-check-target-ip-10-0-139-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:43:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:03:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-54-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-54.ec2.internal
      uid: 5763ec9f-d1a1-420c-8bf1-ea6edb35054a
    resourceVersion: "79567"
    uid: 15f420cb-df3f-467e-bb02-d588d7cd7ace
  spec:
    sourcePod: network-check-source-7d88cb55d8-72w9l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:09:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 979.369µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:57:25Z"
    - latency: 1.853449ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:57:25Z"
    - latency: 895.78µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:56:25Z"
    - latency: 1.926004ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:56:25Z"
    - latency: 859.044µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:55:25Z"
    - latency: 1.828809ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:55:25Z"
    - latency: 919.409µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:54:25Z"
    - latency: 1.7606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:54:25Z"
    - latency: 812.671µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:53:25Z"
    - latency: 1.812528ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:53:25Z"
kind: List
metadata:
  resourceVersion: ""