apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T23:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-239-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-239.ec2.internal
      uid: 46df23b4-1190-420d-94a5-ac3a92cf20c7
    resourceVersion: "55270"
    uid: e24b62d2-269c-4c46-b760-7695230c3788
  spec:
    sourcePod: network-check-source-869dcfcdcd-dg56q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T23:09:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.059283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:37:27Z"
    - latency: 914.552µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:36:27Z"
    - latency: 1.189883ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:35:27Z"
    - latency: 1.23557ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:34:27Z"
    - latency: 1.707928ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:33:27Z"
    - latency: 1.258941ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:32:27Z"
    - latency: 982.316µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:31:27Z"
    - latency: 1.226099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:30:27Z"
    - latency: 915.12µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:29:27Z"
    - latency: 1.036487ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:28:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T23:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-239-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-239.ec2.internal
      uid: 46df23b4-1190-420d-94a5-ac3a92cf20c7
    resourceVersion: "56205"
    uid: d3564125-5dce-425e-879e-05518643e5db
  spec:
    sourcePod: network-check-source-869dcfcdcd-dg56q
    targetEndpoint: a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T23:08:27Z"
      message: 'load-balancer-api-external: tcp connection to a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.410664ms
      message: 'load-balancer-api-external: tcp connection to a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:38:27Z"
    - latency: 8.437859ms
      message: 'load-balancer-api-external: resolved host name a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:38:27Z"
    - latency: 4.849542ms
      message: 'load-balancer-api-external: tcp connection to a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:37:27Z"
    - latency: 6.997878ms
      message: 'load-balancer-api-external: resolved host name a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:37:27Z"
    - latency: 4.102289ms
      message: 'load-balancer-api-external: tcp connection to a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:36:27Z"
    - latency: 7.746533ms
      message: 'load-balancer-api-external: resolved host name a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:36:27Z"
    - latency: 3.523523ms
      message: 'load-balancer-api-external: tcp connection to a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:35:27Z"
    - latency: 6.930263ms
      message: 'load-balancer-api-external: resolved host name a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:35:27Z"
    - latency: 5.036689ms
      message: 'load-balancer-api-external: tcp connection to a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:34:27Z"
    - latency: 6.81734ms
      message: 'load-balancer-api-external: resolved host name a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T23:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-239-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-239.ec2.internal
      uid: 46df23b4-1190-420d-94a5-ac3a92cf20c7
    resourceVersion: "56204"
    uid: 667f57e8-fdf9-49d0-9cf1-0d316d7cbc9e
  spec:
    sourcePod: network-check-source-869dcfcdcd-dg56q
    targetEndpoint: a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T23:08:27Z"
      message: 'load-balancer-api-internal: tcp connection to a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.608051ms
      message: 'load-balancer-api-internal: tcp connection to a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:38:27Z"
    - latency: 8.480931ms
      message: 'load-balancer-api-internal: resolved host name a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:38:27Z"
    - latency: 4.942109ms
      message: 'load-balancer-api-internal: tcp connection to a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:37:27Z"
    - latency: 6.948914ms
      message: 'load-balancer-api-internal: resolved host name a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:37:27Z"
    - latency: 4.125402ms
      message: 'load-balancer-api-internal: tcp connection to a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:36:27Z"
    - latency: 7.613635ms
      message: 'load-balancer-api-internal: resolved host name a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:36:27Z"
    - latency: 3.534076ms
      message: 'load-balancer-api-internal: tcp connection to a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:35:27Z"
    - latency: 6.852705ms
      message: 'load-balancer-api-internal: resolved host name a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:35:27Z"
    - latency: 5.013143ms
      message: 'load-balancer-api-internal: tcp connection to a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:34:27Z"
    - latency: 6.774361ms
      message: 'load-balancer-api-internal: resolved host name a9c740c3c104d4725854dbc2db9b651d-6ff53aeb39ff35f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T23:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-239-to-network-check-target-ip-10-0-135-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-239.ec2.internal
      uid: 46df23b4-1190-420d-94a5-ac3a92cf20c7
    resourceVersion: "55269"
    uid: 57ac1277-57fa-4853-8538-bd14e875357c
  spec:
    sourcePod: network-check-source-869dcfcdcd-dg56q
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T23:09:27Z"
      message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.196425ms
      message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:37:27Z"
    - latency: 2.194633ms
      message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:36:27Z"
    - latency: 2.260996ms
      message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:35:27Z"
    - latency: 2.087652ms
      message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:34:27Z"
    - latency: 2.60874ms
      message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:33:27Z"
    - latency: 2.298601ms
      message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:32:27Z"
    - latency: 2.260321ms
      message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:31:27Z"
    - latency: 2.195277ms
      message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:30:27Z"
    - latency: 2.231446ms
      message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:29:27Z"
    - latency: 2.348502ms
      message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:28:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T23:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-239-to-network-check-target-ip-10-0-139-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-239.ec2.internal
      uid: 46df23b4-1190-420d-94a5-ac3a92cf20c7
    resourceVersion: "55268"
    uid: ec45af78-12e4-4864-96d7-21ff5208e008
  spec:
    sourcePod: network-check-source-869dcfcdcd-dg56q
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T23:09:27Z"
      message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.189902ms
      message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:37:27Z"
    - latency: 2.383087ms
      message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:36:27Z"
    - latency: 2.425016ms
      message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:35:27Z"
    - latency: 2.271356ms
      message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:34:27Z"
    - latency: 2.869101ms
      message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:33:27Z"
    - latency: 2.417893ms
      message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:32:27Z"
    - latency: 2.265761ms
      message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:31:27Z"
    - latency: 2.549197ms
      message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:30:27Z"
    - latency: 2.193978ms
      message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:29:27Z"
    - latency: 2.437129ms
      message: 'network-check-target-ip-10-0-139-179: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:28:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T23:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-239-to-network-check-target-ip-10-0-141-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-239.ec2.internal
      uid: 46df23b4-1190-420d-94a5-ac3a92cf20c7
    resourceVersion: "55267"
    uid: 2decbf7a-b712-4096-b545-5c5204876639
  spec:
    sourcePod: network-check-source-869dcfcdcd-dg56q
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T23:09:27Z"
      message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.242µs
      message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:37:27Z"
    - latency: 891.41µs
      message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:36:27Z"
    - latency: 1.173934ms
      message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:35:27Z"
    - latency: 1.062833ms
      message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:34:27Z"
    - latency: 2.071276ms
      message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:33:27Z"
    - latency: 806.246µs
      message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:32:27Z"
    - latency: 980.463µs
      message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:31:27Z"
    - latency: 888.066µs
      message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:30:27Z"
    - latency: 977.892µs
      message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:29:27Z"
    - latency: 902.253µs
      message: 'network-check-target-ip-10-0-141-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:28:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T23:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-239-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-239.ec2.internal
      uid: 46df23b4-1190-420d-94a5-ac3a92cf20c7
    resourceVersion: "56203"
    uid: 2c74d9cc-d848-4cc4-8bc2-d56b48d07a25
  spec:
    sourcePod: network-check-source-869dcfcdcd-dg56q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T23:08:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 824.977µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:38:27Z"
    - latency: 1.613223ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:38:27Z"
    - latency: 1.538165ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:37:27Z"
    - latency: 1.708497ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:37:27Z"
    - latency: 803.541µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:36:27Z"
    - latency: 1.657452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:36:27Z"
    - latency: 932.902µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:35:27Z"
    - latency: 1.831803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:35:27Z"
    - latency: 895.616µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T23:34:27Z"
    - latency: 1.695308ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T23:34:27Z"
kind: List
metadata:
  resourceVersion: ""