apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T18:03:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 89cafa67-887b-46b2-8b8c-f267f8ffa7d8
    resourceVersion: "40925"
    uid: 1088047e-066d-4f28-8c0e-be13315f741c
  spec:
    sourcePod: network-check-source-8894fc9bd-xfl9g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:10:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 991.664µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:59:03Z"
    - latency: 1.103338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:58:03Z"
    - latency: 1.143391ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:57:03Z"
    - latency: 1.340306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:56:03Z"
    - latency: 943.936µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:55:03Z"
    - latency: 1.326595ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:54:03Z"
    - latency: 951.714µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:53:03Z"
    - latency: 994.53µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:52:03Z"
    - latency: 1.031236ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:51:03Z"
    - latency: 1.171927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:50:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T18:03:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 89cafa67-887b-46b2-8b8c-f267f8ffa7d8
    resourceVersion: "43095"
    uid: 64a357c6-6596-4146-a4c2-271350107c4b
  spec:
    sourcePod: network-check-source-8894fc9bd-xfl9g
    targetEndpoint: a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:09:03Z"
      message: 'load-balancer-api-external: tcp connection to a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.553027ms
      message: 'load-balancer-api-external: tcp connection to a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:03:03Z"
    - latency: 8.753754ms
      message: 'load-balancer-api-external: resolved host name a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:03:03Z"
    - latency: 6.980307ms
      message: 'load-balancer-api-external: tcp connection to a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:02:03Z"
    - latency: 7.080534ms
      message: 'load-balancer-api-external: resolved host name a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:02:03Z"
    - latency: 8.001199ms
      message: 'load-balancer-api-external: tcp connection to a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:01:03Z"
    - latency: 7.028058ms
      message: 'load-balancer-api-external: resolved host name a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:01:03Z"
    - latency: 5.638835ms
      message: 'load-balancer-api-external: tcp connection to a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:00:03Z"
    - latency: 8.223333ms
      message: 'load-balancer-api-external: resolved host name a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:00:03Z"
    - latency: 4.804751ms
      message: 'load-balancer-api-external: tcp connection to a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:59:03Z"
    - latency: 8.913519ms
      message: 'load-balancer-api-external: resolved host name a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:59:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T18:03:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 89cafa67-887b-46b2-8b8c-f267f8ffa7d8
    resourceVersion: "43094"
    uid: 75aceabe-2aa0-4f77-a915-198cd9467858
  spec:
    sourcePod: network-check-source-8894fc9bd-xfl9g
    targetEndpoint: a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:09:03Z"
      message: 'load-balancer-api-internal: tcp connection to a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.560915ms
      message: 'load-balancer-api-internal: tcp connection to a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:03:03Z"
    - latency: 8.651165ms
      message: 'load-balancer-api-internal: resolved host name a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:03:03Z"
    - latency: 7.02319ms
      message: 'load-balancer-api-internal: tcp connection to a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:02:03Z"
    - latency: 7.030339ms
      message: 'load-balancer-api-internal: resolved host name a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:02:03Z"
    - latency: 7.993409ms
      message: 'load-balancer-api-internal: tcp connection to a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:01:03Z"
    - latency: 7.071989ms
      message: 'load-balancer-api-internal: resolved host name a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:01:03Z"
    - latency: 5.626341ms
      message: 'load-balancer-api-internal: tcp connection to a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:00:03Z"
    - latency: 8.287763ms
      message: 'load-balancer-api-internal: resolved host name a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:00:03Z"
    - latency: 4.774139ms
      message: 'load-balancer-api-internal: tcp connection to a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:59:03Z"
    - latency: 8.943664ms
      message: 'load-balancer-api-internal: resolved host name a5dcde1da636f43a1b1c5549d9bfb584-ef6d2a28a4874ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:59:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T18:03:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-network-check-target-ip-10-0-128-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 89cafa67-887b-46b2-8b8c-f267f8ffa7d8
    resourceVersion: "40924"
    uid: 0b179284-866a-43c0-8ed4-83dd0e23157a
  spec:
    sourcePod: network-check-source-8894fc9bd-xfl9g
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:10:03Z"
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.262368ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:59:03Z"
    - latency: 2.279366ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:58:03Z"
    - latency: 2.179457ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:57:03Z"
    - latency: 2.332164ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:56:03Z"
    - latency: 2.216135ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:55:03Z"
    - latency: 2.480997ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:54:03Z"
    - latency: 2.287245ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:53:03Z"
    - latency: 2.30665ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:52:03Z"
    - latency: 2.387012ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:51:03Z"
    - latency: 2.484001ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:50:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T18:03:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-network-check-target-ip-10-0-137-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 89cafa67-887b-46b2-8b8c-f267f8ffa7d8
    resourceVersion: "40923"
    uid: 6a4dbaa7-ec2e-4aec-bab4-d0b54ab2f917
  spec:
    sourcePod: network-check-source-8894fc9bd-xfl9g
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:10:03Z"
      message: 'network-check-target-ip-10-0-137-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.31183ms
      message: 'network-check-target-ip-10-0-137-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:59:03Z"
    - latency: 2.275272ms
      message: 'network-check-target-ip-10-0-137-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:58:03Z"
    - latency: 2.292407ms
      message: 'network-check-target-ip-10-0-137-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:57:03Z"
    - latency: 2.339376ms
      message: 'network-check-target-ip-10-0-137-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:56:03Z"
    - latency: 1.921359ms
      message: 'network-check-target-ip-10-0-137-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:55:03Z"
    - latency: 2.197413ms
      message: 'network-check-target-ip-10-0-137-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:54:03Z"
    - latency: 2.07779ms
      message: 'network-check-target-ip-10-0-137-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:53:03Z"
    - latency: 2.217366ms
      message: 'network-check-target-ip-10-0-137-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:52:03Z"
    - latency: 2.326486ms
      message: 'network-check-target-ip-10-0-137-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:51:03Z"
    - latency: 2.488696ms
      message: 'network-check-target-ip-10-0-137-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:50:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T18:03:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-network-check-target-ip-10-0-143-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 89cafa67-887b-46b2-8b8c-f267f8ffa7d8
    resourceVersion: "40922"
    uid: 8f912ffc-0b38-45d3-a25d-05f7157069e1
  spec:
    sourcePod: network-check-source-8894fc9bd-xfl9g
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:10:03Z"
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.001976ms
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:59:03Z"
    - latency: 948.47µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:58:03Z"
    - latency: 925.153µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:57:03Z"
    - latency: 729.473µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:56:03Z"
    - latency: 1.18919ms
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:55:03Z"
    - latency: 906.012µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:54:03Z"
    - latency: 1.50427ms
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:53:03Z"
    - latency: 945.331µs
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:52:03Z"
    - latency: 1.435727ms
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:51:03Z"
    - latency: 1.4775ms
      message: 'network-check-target-ip-10-0-143-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:50:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T18:03:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-63-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-63.ec2.internal
      uid: 89cafa67-887b-46b2-8b8c-f267f8ffa7d8
    resourceVersion: "43093"
    uid: 8573a8c6-fac4-47a9-bb6d-f3d5cc7e8276
  spec:
    sourcePod: network-check-source-8894fc9bd-xfl9g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:09:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.163528ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:03:03Z"
    - latency: 1.817856ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:03:03Z"
    - latency: 954.952µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:02:03Z"
    - latency: 1.979622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:02:03Z"
    - latency: 1.113748ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:01:03Z"
    - latency: 1.721346ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:01:03Z"
    - latency: 759.186µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T19:00:03Z"
    - latency: 1.507182ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T19:00:03Z"
    - latency: 1.113861ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:59:03Z"
    - latency: 1.804176ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:59:03Z"
kind: List
metadata:
  resourceVersion: ""