apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:27:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-187-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-187.ec2.internal
      uid: a8865e9b-71d1-4550-87ca-2138c53138c3
    resourceVersion: "50240"
    uid: c38eb70d-aa5b-408c-b7bf-fd0b4f35ced2
  spec:
    sourcePod: network-check-source-989f8b8dc-vwhkg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:34:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.130724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:02:08Z"
    - latency: 1.268962ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:01:08Z"
    - latency: 1.010156ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:00:08Z"
    - latency: 1.206027ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:59:08Z"
    - latency: 1.341086ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:58:08Z"
    - latency: 973.445µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:57:08Z"
    - latency: 847.904µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:56:08Z"
    - latency: 1.271897ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:55:08Z"
    - latency: 1.290007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:54:08Z"
    - latency: 1.000108ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:53:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:27:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-187-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-187.ec2.internal
      uid: a8865e9b-71d1-4550-87ca-2138c53138c3
    resourceVersion: "51090"
    uid: 3db60813-69f7-434e-9ec9-1ca8221cfa17
  spec:
    sourcePod: network-check-source-989f8b8dc-vwhkg
    targetEndpoint: aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:33:08Z"
      message: 'load-balancer-api-external: tcp connection to aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.178451ms
      message: 'load-balancer-api-external: tcp connection to aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:03:08Z"
    - latency: 7.066185ms
      message: 'load-balancer-api-external: resolved host name aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:03:08Z"
    - latency: 5.339445ms
      message: 'load-balancer-api-external: tcp connection to aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:02:08Z"
    - latency: 7.043767ms
      message: 'load-balancer-api-external: resolved host name aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:02:08Z"
    - latency: 4.690018ms
      message: 'load-balancer-api-external: tcp connection to aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:01:08Z"
    - latency: 6.865791ms
      message: 'load-balancer-api-external: resolved host name aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:01:08Z"
    - latency: 5.011386ms
      message: 'load-balancer-api-external: tcp connection to aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:00:08Z"
    - latency: 7.330779ms
      message: 'load-balancer-api-external: resolved host name aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:00:08Z"
    - latency: 4.166039ms
      message: 'load-balancer-api-external: tcp connection to aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:59:08Z"
    - latency: 6.382261ms
      message: 'load-balancer-api-external: resolved host name aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:59:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:27:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-187-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-187.ec2.internal
      uid: a8865e9b-71d1-4550-87ca-2138c53138c3
    resourceVersion: "51091"
    uid: 51fd900a-a70f-4edc-9bbf-5fdab34818cb
  spec:
    sourcePod: network-check-source-989f8b8dc-vwhkg
    targetEndpoint: aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:33:08Z"
      message: 'load-balancer-api-internal: tcp connection to aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.330953ms
      message: 'load-balancer-api-internal: tcp connection to aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:03:08Z"
    - latency: 7.137918ms
      message: 'load-balancer-api-internal: resolved host name aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:03:08Z"
    - latency: 5.362207ms
      message: 'load-balancer-api-internal: tcp connection to aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:02:08Z"
    - latency: 7.012296ms
      message: 'load-balancer-api-internal: resolved host name aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:02:08Z"
    - latency: 5.132248ms
      message: 'load-balancer-api-internal: tcp connection to aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:01:08Z"
    - latency: 6.909561ms
      message: 'load-balancer-api-internal: resolved host name aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:01:08Z"
    - latency: 5.061348ms
      message: 'load-balancer-api-internal: tcp connection to aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:00:08Z"
    - latency: 7.311805ms
      message: 'load-balancer-api-internal: resolved host name aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:00:08Z"
    - latency: 6.630791ms
      message: 'load-balancer-api-internal: tcp connection to aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:59:08Z"
    - latency: 6.415718ms
      message: 'load-balancer-api-internal: resolved host name aaeb12975e03d4bf48c0dfe118957bfe-6adc744d42e9c060.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:59:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:27:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-187-to-network-check-target-ip-10-0-130-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-187.ec2.internal
      uid: a8865e9b-71d1-4550-87ca-2138c53138c3
    resourceVersion: "50239"
    uid: 8adb6e82-4568-44b5-81a8-9c8997ecabda
  spec:
    sourcePod: network-check-source-989f8b8dc-vwhkg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:34:08Z"
      message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.40693ms
      message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:02:08Z"
    - latency: 1.719183ms
      message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:01:08Z"
    - latency: 2.284258ms
      message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:00:08Z"
    - latency: 1.783907ms
      message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:59:08Z"
    - latency: 2.191596ms
      message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:58:08Z"
    - latency: 1.555149ms
      message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:57:08Z"
    - latency: 1.872539ms
      message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:56:08Z"
    - latency: 1.948869ms
      message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:55:08Z"
    - latency: 1.946591ms
      message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:54:08Z"
    - latency: 1.615557ms
      message: 'network-check-target-ip-10-0-130-31: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:53:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:27:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-187-to-network-check-target-ip-10-0-141-108
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-187.ec2.internal
      uid: a8865e9b-71d1-4550-87ca-2138c53138c3
    resourceVersion: "50237"
    uid: d3390d67-2385-4e15-a72c-816ce1338a07
  spec:
    sourcePod: network-check-source-989f8b8dc-vwhkg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:34:08Z"
      message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.122454ms
      message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:02:08Z"
    - latency: 2.290441ms
      message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:01:08Z"
    - latency: 2.069829ms
      message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:00:08Z"
    - latency: 2.016063ms
      message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:59:08Z"
    - latency: 2.103758ms
      message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:58:08Z"
    - latency: 1.778869ms
      message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:57:08Z"
    - latency: 2.306853ms
      message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:56:08Z"
    - latency: 2.077951ms
      message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:55:08Z"
    - latency: 1.937414ms
      message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:54:08Z"
    - latency: 2.108111ms
      message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:53:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:27:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-187-to-network-check-target-ip-10-0-141-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-187.ec2.internal
      uid: a8865e9b-71d1-4550-87ca-2138c53138c3
    resourceVersion: "50238"
    uid: 3319fb93-aa27-4169-b7bf-3b069cb0377a
  spec:
    sourcePod: network-check-source-989f8b8dc-vwhkg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:34:08Z"
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.489741ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:02:08Z"
    - latency: 1.222777ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:01:08Z"
    - latency: 1.123372ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:00:08Z"
    - latency: 1.192576ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:59:08Z"
    - latency: 1.451422ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:58:08Z"
    - latency: 947.93µs
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:57:08Z"
    - latency: 1.500414ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:56:08Z"
    - latency: 845.359µs
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:55:08Z"
    - latency: 1.438882ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:54:08Z"
    - latency: 830.839µs
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:53:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:27:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-187-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-187.ec2.internal
      uid: a8865e9b-71d1-4550-87ca-2138c53138c3
    resourceVersion: "51089"
    uid: 933dae8c-eda4-4651-a455-63f59e44722c
  spec:
    sourcePod: network-check-source-989f8b8dc-vwhkg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:33:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 926.04µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:03:08Z"
    - latency: 1.897722ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:03:08Z"
    - latency: 890.334µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:02:08Z"
    - latency: 1.806119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:02:08Z"
    - latency: 873.129µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:01:08Z"
    - latency: 1.887291ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:01:08Z"
    - latency: 881.355µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:00:08Z"
    - latency: 1.77992ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:00:08Z"
    - latency: 886.977µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T18:59:08Z"
    - latency: 1.967219ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T18:59:08Z"
kind: List
metadata:
  resourceVersion: ""