apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 49d80ecd-26c3-4ece-8816-8caf94a49c54
    resourceVersion: "21957"
    uid: 9074577f-3e5f-42e7-9a49-bd2521b436b3
  spec:
    sourcePod: network-check-source-56499946bc-m6t9g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:49:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.296489ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:03:05Z"
    - latency: 1.335016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:02:05Z"
    - latency: 1.139483ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:01:05Z"
    - latency: 1.040463ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:05Z"
    - latency: 939.162µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:05Z"
    - latency: 1.152529ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:05Z"
    - latency: 1.125599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:05Z"
    - latency: 1.096393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:56:05Z"
    - latency: 1.185213ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:55:05Z"
    - latency: 1.383431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:54:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 49d80ecd-26c3-4ece-8816-8caf94a49c54
    resourceVersion: "20531"
    uid: a49b0ea3-6c3e-4cb4-a973-eab420993768
  spec:
    sourcePod: network-check-source-56499946bc-m6t9g
    targetEndpoint: ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:48:05Z"
      message: 'load-balancer-api-external: tcp connection to ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.256197ms
      message: 'load-balancer-api-external: tcp connection to ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:05Z"
    - latency: 8.2028ms
      message: 'load-balancer-api-external: resolved host name ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T15:00:05Z"
    - latency: 4.456891ms
      message: 'load-balancer-api-external: tcp connection to ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:05Z"
    - latency: 9.530242ms
      message: 'load-balancer-api-external: resolved host name ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:59:05Z"
    - latency: 5.004061ms
      message: 'load-balancer-api-external: tcp connection to ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:05Z"
    - latency: 8.289896ms
      message: 'load-balancer-api-external: resolved host name ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:58:05Z"
    - latency: 4.937249ms
      message: 'load-balancer-api-external: tcp connection to ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:05Z"
    - latency: 9.437578ms
      message: 'load-balancer-api-external: resolved host name ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:57:05Z"
    - latency: 4.986033ms
      message: 'load-balancer-api-external: tcp connection to ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:56:05Z"
    - latency: 8.715503ms
      message: 'load-balancer-api-external: resolved host name ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:56:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 49d80ecd-26c3-4ece-8816-8caf94a49c54
    resourceVersion: "20532"
    uid: f339f84c-9e4e-4cb7-9f4e-0a07e117307a
  spec:
    sourcePod: network-check-source-56499946bc-m6t9g
    targetEndpoint: ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:48:05Z"
      message: 'load-balancer-api-internal: tcp connection to ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.286708ms
      message: 'load-balancer-api-internal: tcp connection to ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:05Z"
    - latency: 8.319853ms
      message: 'load-balancer-api-internal: resolved host name ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T15:00:05Z"
    - latency: 4.469035ms
      message: 'load-balancer-api-internal: tcp connection to ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:05Z"
    - latency: 9.476184ms
      message: 'load-balancer-api-internal: resolved host name ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:59:05Z"
    - latency: 5.013745ms
      message: 'load-balancer-api-internal: tcp connection to ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:05Z"
    - latency: 8.308949ms
      message: 'load-balancer-api-internal: resolved host name ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:58:05Z"
    - latency: 4.444267ms
      message: 'load-balancer-api-internal: tcp connection to ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:05Z"
    - latency: 9.599362ms
      message: 'load-balancer-api-internal: resolved host name ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:57:05Z"
    - latency: 4.987089ms
      message: 'load-balancer-api-internal: tcp connection to ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:56:05Z"
    - latency: 8.677806ms
      message: 'load-balancer-api-internal: resolved host name ab477f15f52c848099c0b8a61c5be683-aacf61b4b7aa2f37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:56:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-network-check-target-ip-10-0-129-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 49d80ecd-26c3-4ece-8816-8caf94a49c54
    resourceVersion: "21955"
    uid: edad2318-2f8c-4b17-b678-a8719d642b41
  spec:
    sourcePod: network-check-source-56499946bc-m6t9g
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:49:05Z"
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.110343ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:03:05Z"
    - latency: 2.232383ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:02:05Z"
    - latency: 2.168232ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:01:05Z"
    - latency: 2.059619ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:05Z"
    - latency: 2.199826ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:05Z"
    - latency: 1.947832ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:05Z"
    - latency: 1.991408ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:05Z"
    - latency: 1.938101ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:56:05Z"
    - latency: 2.172504ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:55:05Z"
    - latency: 2.037013ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:54:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-network-check-target-ip-10-0-134-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 49d80ecd-26c3-4ece-8816-8caf94a49c54
    resourceVersion: "21954"
    uid: 799a5418-8d01-4a2f-a16d-126de60d5997
  spec:
    sourcePod: network-check-source-56499946bc-m6t9g
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:49:05Z"
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.357143ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:03:05Z"
    - latency: 2.196787ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:02:05Z"
    - latency: 2.322169ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:01:05Z"
    - latency: 2.264011ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:05Z"
    - latency: 1.900367ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:05Z"
    - latency: 2.19171ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:05Z"
    - latency: 2.180065ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:05Z"
    - latency: 2.231948ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:56:05Z"
    - latency: 2.05263ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:55:05Z"
    - latency: 1.994672ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:54:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-network-check-target-ip-10-0-134-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 49d80ecd-26c3-4ece-8816-8caf94a49c54
    resourceVersion: "21956"
    uid: 143ce00a-d2d9-4f36-b919-5fdf9473145c
  spec:
    sourcePod: network-check-source-56499946bc-m6t9g
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:49:05Z"
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.549986ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:03:05Z"
    - latency: 1.387479ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:02:05Z"
    - latency: 1.002295ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:01:05Z"
    - latency: 1.001004ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:05Z"
    - latency: 1.441363ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:05Z"
    - latency: 929.507µs
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:05Z"
    - latency: 1.063138ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:05Z"
    - latency: 937.15µs
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:56:05Z"
    - latency: 1.469798ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:55:05Z"
    - latency: 820.508µs
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:54:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 49d80ecd-26c3-4ece-8816-8caf94a49c54
    resourceVersion: "20530"
    uid: 2cdcbae4-baae-48d5-a8b4-47be4e24c880
  spec:
    sourcePod: network-check-source-56499946bc-m6t9g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:48:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 874.048µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:05Z"
    - latency: 1.985217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T15:00:05Z"
    - latency: 1.104019ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:05Z"
    - latency: 1.687937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:59:05Z"
    - latency: 1.013768ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:05Z"
    - latency: 1.949947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:58:05Z"
    - latency: 946.468µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:05Z"
    - latency: 1.988548ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:57:05Z"
    - latency: 1.215195ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:56:05Z"
    - latency: 1.958832ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:56:05Z"
kind: List
metadata:
  resourceVersion: ""