apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T17:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: 78b046c0-bc4d-48d5-bda1-fa53101b1e84
    resourceVersion: "61348"
    uid: 94586e5c-6ff3-43f6-bd99-033c3c6f7d4c
  spec:
    sourcePod: network-check-source-869dcfcdcd-nq4wv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T17:31:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 876.497µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:06:06Z"
    - latency: 1.135452ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:05:06Z"
    - latency: 990.048µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:04:06Z"
    - latency: 1.138969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:03:06Z"
    - latency: 1.17287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:02:06Z"
    - latency: 889.729µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:01:06Z"
    - latency: 867.53µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:00:06Z"
    - latency: 740.112µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:59:06Z"
    - latency: 965.075µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:58:06Z"
    - latency: 1.226132ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:57:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T17:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: 78b046c0-bc4d-48d5-bda1-fa53101b1e84
    resourceVersion: "61350"
    uid: 82f64154-971c-4e4c-982a-dbc92ebbd49d
  spec:
    sourcePod: network-check-source-869dcfcdcd-nq4wv
    targetEndpoint: a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T17:30:06Z"
      message: 'load-balancer-api-external: tcp connection to a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.245147ms
      message: 'load-balancer-api-external: tcp connection to a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:06:06Z"
    - latency: 7.507403ms
      message: 'load-balancer-api-external: resolved host name a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:06:06Z"
    - latency: 5.730332ms
      message: 'load-balancer-api-external: tcp connection to a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:05:06Z"
    - latency: 6.962823ms
      message: 'load-balancer-api-external: resolved host name a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:05:06Z"
    - latency: 5.591315ms
      message: 'load-balancer-api-external: tcp connection to a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:04:06Z"
    - latency: 6.768586ms
      message: 'load-balancer-api-external: resolved host name a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:04:06Z"
    - latency: 5.06585ms
      message: 'load-balancer-api-external: tcp connection to a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:03:06Z"
    - latency: 6.62628ms
      message: 'load-balancer-api-external: resolved host name a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:03:06Z"
    - latency: 4.518089ms
      message: 'load-balancer-api-external: tcp connection to a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:02:06Z"
    - latency: 6.939595ms
      message: 'load-balancer-api-external: resolved host name a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:02:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T17:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: 78b046c0-bc4d-48d5-bda1-fa53101b1e84
    resourceVersion: "61349"
    uid: 3e7cfde2-1485-44e0-a22b-3499cb267e01
  spec:
    sourcePod: network-check-source-869dcfcdcd-nq4wv
    targetEndpoint: a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T17:30:06Z"
      message: 'load-balancer-api-internal: tcp connection to a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.31347ms
      message: 'load-balancer-api-internal: tcp connection to a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:06:06Z"
    - latency: 7.457182ms
      message: 'load-balancer-api-internal: resolved host name a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:06:06Z"
    - latency: 5.780513ms
      message: 'load-balancer-api-internal: tcp connection to a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:05:06Z"
    - latency: 6.886642ms
      message: 'load-balancer-api-internal: resolved host name a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:05:06Z"
    - latency: 5.555596ms
      message: 'load-balancer-api-internal: tcp connection to a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:04:06Z"
    - latency: 6.861342ms
      message: 'load-balancer-api-internal: resolved host name a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:04:06Z"
    - latency: 4.409151ms
      message: 'load-balancer-api-internal: tcp connection to a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:03:06Z"
    - latency: 6.682448ms
      message: 'load-balancer-api-internal: resolved host name a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:03:06Z"
    - latency: 4.672068ms
      message: 'load-balancer-api-internal: tcp connection to a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:02:06Z"
    - latency: 6.916005ms
      message: 'load-balancer-api-internal: resolved host name a880f5a4aff3b48e09830f94f9eb529f-3a789dda0551d3a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:02:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T17:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-network-check-target-ip-10-0-134-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: 78b046c0-bc4d-48d5-bda1-fa53101b1e84
    resourceVersion: "61344"
    uid: d7522121-f8fe-444e-b02f-99a9b5a6e0dd
  spec:
    sourcePod: network-check-source-869dcfcdcd-nq4wv
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T17:31:06Z"
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 821.699µs
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:06:06Z"
    - latency: 985.89µs
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:05:06Z"
    - latency: 1.042367ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:04:06Z"
    - latency: 1.053623ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:03:06Z"
    - latency: 1.020012ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:02:06Z"
    - latency: 1.011722ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:01:06Z"
    - latency: 945.452µs
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:00:06Z"
    - latency: 717.762µs
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:59:06Z"
    - latency: 835.992µs
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:58:06Z"
    - latency: 1.30038ms
      message: 'network-check-target-ip-10-0-134-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:57:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T17:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-network-check-target-ip-10-0-141-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: 78b046c0-bc4d-48d5-bda1-fa53101b1e84
    resourceVersion: "61345"
    uid: 77449100-a5f5-426b-afa1-bfa8b037c847
  spec:
    sourcePod: network-check-source-869dcfcdcd-nq4wv
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T17:31:06Z"
      message: 'network-check-target-ip-10-0-141-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.554017ms
      message: 'network-check-target-ip-10-0-141-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:06:06Z"
    - latency: 2.5015ms
      message: 'network-check-target-ip-10-0-141-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:05:06Z"
    - latency: 2.459364ms
      message: 'network-check-target-ip-10-0-141-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:04:06Z"
    - latency: 2.418532ms
      message: 'network-check-target-ip-10-0-141-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:03:06Z"
    - latency: 2.097492ms
      message: 'network-check-target-ip-10-0-141-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:02:06Z"
    - latency: 2.168961ms
      message: 'network-check-target-ip-10-0-141-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:01:06Z"
    - latency: 2.585243ms
      message: 'network-check-target-ip-10-0-141-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:00:06Z"
    - latency: 2.416613ms
      message: 'network-check-target-ip-10-0-141-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:59:06Z"
    - latency: 2.296875ms
      message: 'network-check-target-ip-10-0-141-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:58:06Z"
    - latency: 2.362701ms
      message: 'network-check-target-ip-10-0-141-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:57:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T17:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-network-check-target-ip-10-0-143-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: 78b046c0-bc4d-48d5-bda1-fa53101b1e84
    resourceVersion: "61346"
    uid: 37903062-79c8-42f7-857e-9f396eff7fa7
  spec:
    sourcePod: network-check-source-869dcfcdcd-nq4wv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T17:31:06Z"
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.801797ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:06:06Z"
    - latency: 2.495819ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:05:06Z"
    - latency: 2.115094ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:04:06Z"
    - latency: 2.347858ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:03:06Z"
    - latency: 2.191638ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:02:06Z"
    - latency: 2.150189ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:01:06Z"
    - latency: 2.06212ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:00:06Z"
    - latency: 1.793125ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:59:06Z"
    - latency: 2.288558ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:58:06Z"
    - latency: 2.50774ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:57:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T17:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-215-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-215.ec2.internal
      uid: 78b046c0-bc4d-48d5-bda1-fa53101b1e84
    resourceVersion: "61347"
    uid: 1701bcf8-9d61-484e-9d80-69dada208910
  spec:
    sourcePod: network-check-source-869dcfcdcd-nq4wv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T17:30:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.282µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:06:06Z"
    - latency: 2.015802ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:06:06Z"
    - latency: 1.252958ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:05:06Z"
    - latency: 1.867712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:05:06Z"
    - latency: 906.081µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:04:06Z"
    - latency: 1.795022ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:04:06Z"
    - latency: 1.386398ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:03:06Z"
    - latency: 1.833864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:03:06Z"
    - latency: 1.0481ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T18:02:06Z"
    - latency: 1.817818ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T18:02:06Z"
kind: List
metadata:
  resourceVersion: ""