apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T03:41:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-241-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-241.ec2.internal
      uid: 0d8e4481-21ab-4387-9a7e-8efb4549a5a0
    resourceVersion: "75627"
    uid: 177e0716-6e4f-4d57-9f3f-b095c1b8be67
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvl2b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T03:48:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.679895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:37:17Z"
    - latency: 1.038355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:36:17Z"
    - latency: 1.03006ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:35:17Z"
    - latency: 917.152µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:34:17Z"
    - latency: 934.279µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:33:17Z"
    - latency: 992.778µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:32:17Z"
    - latency: 960.416µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:31:17Z"
    - latency: 1.284644ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:30:17Z"
    - latency: 908.034µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:29:17Z"
    - latency: 1.164031ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:28:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T03:41:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-241-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-241.ec2.internal
      uid: 0d8e4481-21ab-4387-9a7e-8efb4549a5a0
    resourceVersion: "80098"
    uid: 7c542a67-5a1f-4118-9f66-3329b64064e1
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvl2b
    targetEndpoint: aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T03:47:17Z"
      message: 'load-balancer-api-external: tcp connection to aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.23788ms
      message: 'load-balancer-api-external: tcp connection to aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:41:17Z"
    - latency: 10.114705ms
      message: 'load-balancer-api-external: resolved host name aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:41:17Z"
    - latency: 5.268331ms
      message: 'load-balancer-api-external: tcp connection to aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:40:17Z"
    - latency: 11.63485ms
      message: 'load-balancer-api-external: resolved host name aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:40:17Z"
    - latency: 4.80317ms
      message: 'load-balancer-api-external: tcp connection to aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:39:17Z"
    - latency: 13.827493ms
      message: 'load-balancer-api-external: resolved host name aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:39:17Z"
    - latency: 2.961914ms
      message: 'load-balancer-api-external: tcp connection to aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:38:17Z"
    - latency: 9.427611ms
      message: 'load-balancer-api-external: resolved host name aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:38:17Z"
    - latency: 4.493341ms
      message: 'load-balancer-api-external: tcp connection to aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:37:17Z"
    - latency: 12.298227ms
      message: 'load-balancer-api-external: resolved host name aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:37:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T03:41:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-241-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-241.ec2.internal
      uid: 0d8e4481-21ab-4387-9a7e-8efb4549a5a0
    resourceVersion: "80097"
    uid: 1a4708ef-6482-40b0-813e-73d6a7e457ee
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvl2b
    targetEndpoint: aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T03:47:17Z"
      message: 'load-balancer-api-internal: tcp connection to aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.212448ms
      message: 'load-balancer-api-internal: tcp connection to aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:41:17Z"
    - latency: 10.024995ms
      message: 'load-balancer-api-internal: resolved host name aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:41:17Z"
    - latency: 5.067681ms
      message: 'load-balancer-api-internal: tcp connection to aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:40:17Z"
    - latency: 11.616546ms
      message: 'load-balancer-api-internal: resolved host name aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:40:17Z"
    - latency: 5.151226ms
      message: 'load-balancer-api-internal: tcp connection to aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:39:17Z"
    - latency: 13.91559ms
      message: 'load-balancer-api-internal: resolved host name aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:39:17Z"
    - latency: 2.951446ms
      message: 'load-balancer-api-internal: tcp connection to aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:38:17Z"
    - latency: 9.480934ms
      message: 'load-balancer-api-internal: resolved host name aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:38:17Z"
    - latency: 3.925825ms
      message: 'load-balancer-api-internal: tcp connection to aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:37:17Z"
    - latency: 12.347816ms
      message: 'load-balancer-api-internal: resolved host name aa7f4fa0b038e43dda46720d3d759a45-21c34447dab734ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:37:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T03:41:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-241-to-network-check-target-ip-10-0-136-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-241.ec2.internal
      uid: 0d8e4481-21ab-4387-9a7e-8efb4549a5a0
    resourceVersion: "75624"
    uid: 87a42a9b-f1bd-4b4d-9bbe-bb7bd060c1f7
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvl2b
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T03:48:17Z"
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.081923ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:37:17Z"
    - latency: 981.032µs
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:36:17Z"
    - latency: 1.221599ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:35:17Z"
    - latency: 851.953µs
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:34:17Z"
    - latency: 1.206005ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:33:17Z"
    - latency: 1.455323ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:32:17Z"
    - latency: 1.244124ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:31:17Z"
    - latency: 1.214913ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:30:17Z"
    - latency: 1.102597ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:29:17Z"
    - latency: 846.531µs
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:28:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T03:41:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-241-to-network-check-target-ip-10-0-137-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-241.ec2.internal
      uid: 0d8e4481-21ab-4387-9a7e-8efb4549a5a0
    resourceVersion: "75625"
    uid: 8bea1f8d-897c-439e-b5fb-d64d6af4e0b3
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvl2b
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T03:48:17Z"
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.33101ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:37:17Z"
    - latency: 2.291197ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:36:17Z"
    - latency: 2.571183ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:35:17Z"
    - latency: 2.42305ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:34:17Z"
    - latency: 2.308435ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:33:17Z"
    - latency: 2.71843ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:32:17Z"
    - latency: 2.354256ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:31:17Z"
    - latency: 2.750447ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:30:17Z"
    - latency: 2.335145ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:29:17Z"
    - latency: 2.640795ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:28:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T03:41:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-241-to-network-check-target-ip-10-0-143-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-241.ec2.internal
      uid: 0d8e4481-21ab-4387-9a7e-8efb4549a5a0
    resourceVersion: "75626"
    uid: 6820aebd-11b0-47ba-9caf-6632f0b72b5d
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvl2b
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T03:48:17Z"
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.060776ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:37:17Z"
    - latency: 2.301185ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:36:17Z"
    - latency: 2.31028ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:35:17Z"
    - latency: 2.025489ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:34:17Z"
    - latency: 2.409824ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:33:17Z"
    - latency: 2.041523ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:32:17Z"
    - latency: 2.273609ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:31:17Z"
    - latency: 2.210389ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:30:17Z"
    - latency: 2.280219ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:29:17Z"
    - latency: 2.380119ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:28:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T03:41:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-241-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-241.ec2.internal
      uid: 0d8e4481-21ab-4387-9a7e-8efb4549a5a0
    resourceVersion: "80096"
    uid: 2fc5cd4b-f872-4a7a-a77c-d5bca06ea160
  spec:
    sourcePod: network-check-source-7d88cb55d8-nvl2b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T03:47:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.144738ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:41:17Z"
    - latency: 1.947584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:41:17Z"
    - latency: 946.173µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:40:17Z"
    - latency: 1.737363ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:40:17Z"
    - latency: 900.338µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:39:17Z"
    - latency: 1.786541ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:39:17Z"
    - latency: 870.913µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:38:17Z"
    - latency: 2.258192ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:38:17Z"
    - latency: 1.609964ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T04:37:17Z"
    - latency: 1.653417ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T04:37:17Z"
kind: List
metadata:
  resourceVersion: ""