apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:30:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-114-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-114.ec2.internal
      uid: ebec78e9-cca6-4c8b-a4b9-d88318a9eaf7
    resourceVersion: "60737"
    uid: cbeac198-728f-44a4-bfe0-8a1ba565fc18
  spec:
    sourcePod: network-check-source-869dcfcdcd-2fmrd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T13:37:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 997.069µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:12:15Z"
    - latency: 1.089267ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:11:15Z"
    - latency: 1.061525ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:10:15Z"
    - latency: 1.57021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:09:15Z"
    - latency: 730.717µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:08:15Z"
    - latency: 1.169703ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:07:15Z"
    - latency: 868.142µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:06:15Z"
    - latency: 1.105163ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:05:15Z"
    - latency: 1.030746ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:04:15Z"
    - latency: 1.211747ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:03:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:30:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-114-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-114.ec2.internal
      uid: ebec78e9-cca6-4c8b-a4b9-d88318a9eaf7
    resourceVersion: "60739"
    uid: aac63f75-919e-445f-975e-5869d37abf9c
  spec:
    sourcePod: network-check-source-869dcfcdcd-2fmrd
    targetEndpoint: a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T13:36:15Z"
      message: 'load-balancer-api-external: tcp connection to a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.060193ms
      message: 'load-balancer-api-external: tcp connection to a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:12:15Z"
    - latency: 8.23749ms
      message: 'load-balancer-api-external: resolved host name a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:12:15Z"
    - latency: 5.085098ms
      message: 'load-balancer-api-external: tcp connection to a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:11:15Z"
    - latency: 8.205496ms
      message: 'load-balancer-api-external: resolved host name a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:11:15Z"
    - latency: 4.160034ms
      message: 'load-balancer-api-external: tcp connection to a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:10:15Z"
    - latency: 11.537659ms
      message: 'load-balancer-api-external: resolved host name a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:10:15Z"
    - latency: 5.640667ms
      message: 'load-balancer-api-external: tcp connection to a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:09:15Z"
    - latency: 8.077141ms
      message: 'load-balancer-api-external: resolved host name a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:09:15Z"
    - latency: 3.826139ms
      message: 'load-balancer-api-external: tcp connection to a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:08:15Z"
    - latency: 9.88114ms
      message: 'load-balancer-api-external: resolved host name a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:08:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:30:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-114-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-114.ec2.internal
      uid: ebec78e9-cca6-4c8b-a4b9-d88318a9eaf7
    resourceVersion: "60738"
    uid: 77e9b340-45f4-41b9-a061-31afae721385
  spec:
    sourcePod: network-check-source-869dcfcdcd-2fmrd
    targetEndpoint: a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T13:36:15Z"
      message: 'load-balancer-api-internal: tcp connection to a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.198142ms
      message: 'load-balancer-api-internal: tcp connection to a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:12:15Z"
    - latency: 8.323896ms
      message: 'load-balancer-api-internal: resolved host name a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:12:15Z"
    - latency: 5.094814ms
      message: 'load-balancer-api-internal: tcp connection to a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:11:15Z"
    - latency: 8.245455ms
      message: 'load-balancer-api-internal: resolved host name a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:11:15Z"
    - latency: 4.164141ms
      message: 'load-balancer-api-internal: tcp connection to a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:10:15Z"
    - latency: 11.508395ms
      message: 'load-balancer-api-internal: resolved host name a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:10:15Z"
    - latency: 5.596429ms
      message: 'load-balancer-api-internal: tcp connection to a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:09:15Z"
    - latency: 8.111587ms
      message: 'load-balancer-api-internal: resolved host name a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:09:15Z"
    - latency: 3.813102ms
      message: 'load-balancer-api-internal: tcp connection to a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:08:15Z"
    - latency: 9.956406ms
      message: 'load-balancer-api-internal: resolved host name a275ae25797634cfd905b0e4505a376b-0940cc1b300f6c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:08:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:30:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-114-to-network-check-target-ip-10-0-138-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-114.ec2.internal
      uid: ebec78e9-cca6-4c8b-a4b9-d88318a9eaf7
    resourceVersion: "60733"
    uid: 87f586e1-39e2-4b4a-a208-e14c2a2c9d9b
  spec:
    sourcePod: network-check-source-869dcfcdcd-2fmrd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T13:37:15Z"
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.408141ms
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:12:15Z"
    - latency: 1.551608ms
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:11:15Z"
    - latency: 812.81µs
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:10:15Z"
    - latency: 826.481µs
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:09:15Z"
    - latency: 1.032219ms
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:08:15Z"
    - latency: 894.544µs
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:07:15Z"
    - latency: 793.594µs
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:06:15Z"
    - latency: 985.237µs
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:05:15Z"
    - latency: 852.418µs
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:04:15Z"
    - latency: 1.482435ms
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:03:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:30:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-114-to-network-check-target-ip-10-0-140-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-114.ec2.internal
      uid: ebec78e9-cca6-4c8b-a4b9-d88318a9eaf7
    resourceVersion: "60735"
    uid: 299dc256-33b6-406f-bb89-911fe0b10096
  spec:
    sourcePod: network-check-source-869dcfcdcd-2fmrd
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T13:37:15Z"
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.485961ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:12:15Z"
    - latency: 2.122401ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:11:15Z"
    - latency: 2.41939ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:10:15Z"
    - latency: 2.177722ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:09:15Z"
    - latency: 1.870669ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:08:15Z"
    - latency: 2.093372ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:07:15Z"
    - latency: 2.001693ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:06:15Z"
    - latency: 2.20684ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:05:15Z"
    - latency: 2.290237ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:04:15Z"
    - latency: 2.325557ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:03:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:30:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-114-to-network-check-target-ip-10-0-142-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-114.ec2.internal
      uid: ebec78e9-cca6-4c8b-a4b9-d88318a9eaf7
    resourceVersion: "60734"
    uid: f45d3f8a-1bb9-44af-a502-7673f0f70bed
  spec:
    sourcePod: network-check-source-869dcfcdcd-2fmrd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T13:37:15Z"
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.388166ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:12:15Z"
    - latency: 2.102443ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:11:15Z"
    - latency: 2.083753ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:10:15Z"
    - latency: 1.918327ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:09:15Z"
    - latency: 1.729645ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:08:15Z"
    - latency: 1.993555ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:07:15Z"
    - latency: 2.064391ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:06:15Z"
    - latency: 2.208432ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:05:15Z"
    - latency: 1.792442ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:04:15Z"
    - latency: 2.165321ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:03:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T13:30:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-114-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-114.ec2.internal
      uid: ebec78e9-cca6-4c8b-a4b9-d88318a9eaf7
    resourceVersion: "60736"
    uid: e0b2104c-48e3-4115-897c-c83613a40d73
  spec:
    sourcePod: network-check-source-869dcfcdcd-2fmrd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T13:36:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 967.739µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:12:15Z"
    - latency: 1.696977ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:12:15Z"
    - latency: 717.089µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:11:15Z"
    - latency: 1.931606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:11:15Z"
    - latency: 1.140725ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:10:15Z"
    - latency: 1.992081ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:10:15Z"
    - latency: 1.044377ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:09:15Z"
    - latency: 1.798535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:09:15Z"
    - latency: 700.063µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:08:15Z"
    - latency: 1.700903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:08:15Z"
kind: List
metadata:
  resourceVersion: ""