apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-236-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-236.ec2.internal
      uid: ac1be00b-81d4-4c03-b57b-f3c995d31805
    resourceVersion: "67592"
    uid: b8adc9fd-85cb-4a78-9a3e-6b74d1a27666
  spec:
    sourcePod: network-check-source-6f8b768455-bbzkq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:59:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.105064ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:27:30Z"
    - latency: 1.010426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:30Z"
    - latency: 1.363244ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:30Z"
    - latency: 987.251µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:30Z"
    - latency: 1.486186ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:23:30Z"
    - latency: 969.457µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:22:30Z"
    - latency: 1.597633ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:21:30Z"
    - latency: 903.068µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:20:30Z"
    - latency: 971.671µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:19:30Z"
    - latency: 992.291µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-236-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-236.ec2.internal
      uid: ac1be00b-81d4-4c03-b57b-f3c995d31805
    resourceVersion: "68696"
    uid: cb0ba136-516a-480e-a4eb-5a88e5762198
  spec:
    sourcePod: network-check-source-6f8b768455-bbzkq
    targetEndpoint: aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:58:30Z"
      message: 'load-balancer-api-external: tcp connection to aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.618318ms
      message: 'load-balancer-api-external: tcp connection to aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:28:30Z"
    - latency: 9.734405ms
      message: 'load-balancer-api-external: resolved host name aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:28:30Z"
    - latency: 5.946643ms
      message: 'load-balancer-api-external: tcp connection to aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:27:30Z"
    - latency: 9.941871ms
      message: 'load-balancer-api-external: resolved host name aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:27:30Z"
    - latency: 4.32659ms
      message: 'load-balancer-api-external: tcp connection to aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:30Z"
    - latency: 9.187835ms
      message: 'load-balancer-api-external: resolved host name aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:26:30Z"
    - latency: 5.550026ms
      message: 'load-balancer-api-external: tcp connection to aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:30Z"
    - latency: 10.275799ms
      message: 'load-balancer-api-external: resolved host name aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:25:30Z"
    - latency: 5.299024ms
      message: 'load-balancer-api-external: tcp connection to aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:30Z"
    - latency: 10.666626ms
      message: 'load-balancer-api-external: resolved host name aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:24:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-236-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-236.ec2.internal
      uid: ac1be00b-81d4-4c03-b57b-f3c995d31805
    resourceVersion: "68697"
    uid: 774ac559-ab0e-49a2-8309-172a3395d484
  spec:
    sourcePod: network-check-source-6f8b768455-bbzkq
    targetEndpoint: aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:58:30Z"
      message: 'load-balancer-api-internal: tcp connection to aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.636041ms
      message: 'load-balancer-api-internal: tcp connection to aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:28:30Z"
    - latency: 10.015695ms
      message: 'load-balancer-api-internal: resolved host name aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:28:30Z"
    - latency: 5.163523ms
      message: 'load-balancer-api-internal: tcp connection to aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:27:30Z"
    - latency: 9.866219ms
      message: 'load-balancer-api-internal: resolved host name aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:27:30Z"
    - latency: 4.346439ms
      message: 'load-balancer-api-internal: tcp connection to aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:30Z"
    - latency: 9.301811ms
      message: 'load-balancer-api-internal: resolved host name aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:26:30Z"
    - latency: 5.524319ms
      message: 'load-balancer-api-internal: tcp connection to aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:30Z"
    - latency: 10.319897ms
      message: 'load-balancer-api-internal: resolved host name aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:25:30Z"
    - latency: 5.283959ms
      message: 'load-balancer-api-internal: tcp connection to aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:30Z"
    - latency: 10.84281ms
      message: 'load-balancer-api-internal: resolved host name aaba992a061ab467f81fa9a55ea00ab6-ea743a2067fab2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:24:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-236-to-network-check-target-ip-10-0-131-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-236.ec2.internal
      uid: ac1be00b-81d4-4c03-b57b-f3c995d31805
    resourceVersion: "67589"
    uid: b6efda1d-4ade-4b7d-9a9c-1b94561f83ec
  spec:
    sourcePod: network-check-source-6f8b768455-bbzkq
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:59:30Z"
      message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.022µs
      message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:27:30Z"
    - latency: 954.245µs
      message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:30Z"
    - latency: 992.522µs
      message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:30Z"
    - latency: 869.195µs
      message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:30Z"
    - latency: 942.932µs
      message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:23:30Z"
    - latency: 1.17832ms
      message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:22:30Z"
    - latency: 1.483049ms
      message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:21:30Z"
    - latency: 936.268µs
      message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:20:30Z"
    - latency: 992.991µs
      message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:19:30Z"
    - latency: 1.383746ms
      message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-236-to-network-check-target-ip-10-0-133-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-236.ec2.internal
      uid: ac1be00b-81d4-4c03-b57b-f3c995d31805
    resourceVersion: "67591"
    uid: 85ae76a9-5555-4634-9e6a-896fab4ecf3c
  spec:
    sourcePod: network-check-source-6f8b768455-bbzkq
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:59:30Z"
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.687423ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:27:30Z"
    - latency: 2.429228ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:30Z"
    - latency: 2.483707ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:30Z"
    - latency: 2.269539ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:30Z"
    - latency: 2.878193ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:23:30Z"
    - latency: 2.26286ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:22:30Z"
    - latency: 2.290102ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:21:30Z"
    - latency: 2.353011ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:20:30Z"
    - latency: 2.585902ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:19:30Z"
    - latency: 2.368887ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-236-to-network-check-target-ip-10-0-135-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-236.ec2.internal
      uid: ac1be00b-81d4-4c03-b57b-f3c995d31805
    resourceVersion: "67590"
    uid: 3c00f0f4-b07f-4ddf-b19f-2e2010e1eac4
  spec:
    sourcePod: network-check-source-6f8b768455-bbzkq
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:59:30Z"
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.347285ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:27:30Z"
    - latency: 2.919487ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:30Z"
    - latency: 2.577786ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:30Z"
    - latency: 2.751302ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:30Z"
    - latency: 2.280076ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:23:30Z"
    - latency: 2.411558ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:22:30Z"
    - latency: 2.219959ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:21:30Z"
    - latency: 2.88576ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:20:30Z"
    - latency: 2.449651ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:19:30Z"
    - latency: 2.478388ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-236-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-236.ec2.internal
      uid: ac1be00b-81d4-4c03-b57b-f3c995d31805
    resourceVersion: "68695"
    uid: 58821a92-2583-4414-97c5-7e0fdf4b4cf3
  spec:
    sourcePod: network-check-source-6f8b768455-bbzkq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:58:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 969.632µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:28:30Z"
    - latency: 2.523156ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:28:30Z"
    - latency: 959.934µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:27:30Z"
    - latency: 1.90878ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:27:30Z"
    - latency: 1.270201ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:30Z"
    - latency: 1.973656ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:26:30Z"
    - latency: 946.936µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:30Z"
    - latency: 1.824238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:25:30Z"
    - latency: 866.439µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:30Z"
    - latency: 2.613557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:24:30Z"
kind: List
metadata:
  resourceVersion: ""