apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-142.ec2.internal
      uid: 11f1157e-1330-40f6-82eb-c6335afffc78
    resourceVersion: "53831"
    uid: 0e0b1d3c-8b23-4028-a2a2-9f7a9612538e
  spec:
    sourcePod: network-check-source-6f8b768455-p9rh5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:09:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 853.443µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:32Z"
    - latency: 954.583µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:32Z"
    - latency: 1.162944ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:32Z"
    - latency: 1.201084ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:32Z"
    - latency: 1.179653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:32Z"
    - latency: 1.127533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:32Z"
    - latency: 991.616µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:32Z"
    - latency: 1.491416ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:32Z"
    - latency: 1.166154ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:32Z"
    - latency: 922.877µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-142.ec2.internal
      uid: 11f1157e-1330-40f6-82eb-c6335afffc78
    resourceVersion: "55550"
    uid: 0e1be665-d14b-4d78-9171-e087b42dbeac
  spec:
    sourcePod: network-check-source-6f8b768455-p9rh5
    targetEndpoint: ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:32Z"
      message: 'load-balancer-api-external: tcp connection to ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.9977ms
      message: 'load-balancer-api-external: tcp connection to ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:32:32Z"
    - latency: 8.484498ms
      message: 'load-balancer-api-external: resolved host name ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:32:32Z"
    - latency: 5.292957ms
      message: 'load-balancer-api-external: tcp connection to ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:31:32Z"
    - latency: 10.359637ms
      message: 'load-balancer-api-external: resolved host name ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:31:32Z"
    - latency: 4.36186ms
      message: 'load-balancer-api-external: tcp connection to ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:32Z"
    - latency: 8.230438ms
      message: 'load-balancer-api-external: resolved host name ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:32Z"
    - latency: 19.117738ms
      message: 'load-balancer-api-external: tcp connection to ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:32Z"
    - latency: 8.39435ms
      message: 'load-balancer-api-external: resolved host name ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:32Z"
    - latency: 4.745931ms
      message: 'load-balancer-api-external: tcp connection to ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:32Z"
    - latency: 8.715014ms
      message: 'load-balancer-api-external: resolved host name ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-142.ec2.internal
      uid: 11f1157e-1330-40f6-82eb-c6335afffc78
    resourceVersion: "55551"
    uid: 33b3c2d0-1c16-4d00-b922-950e109e85e1
  spec:
    sourcePod: network-check-source-6f8b768455-p9rh5
    targetEndpoint: ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:32Z"
      message: 'load-balancer-api-internal: tcp connection to ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.679936ms
      message: 'load-balancer-api-internal: tcp connection to ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:32:32Z"
    - latency: 8.429279ms
      message: 'load-balancer-api-internal: resolved host name ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:32:32Z"
    - latency: 3.862805ms
      message: 'load-balancer-api-internal: tcp connection to ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:31:32Z"
    - latency: 10.292743ms
      message: 'load-balancer-api-internal: resolved host name ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:31:32Z"
    - latency: 3.238454ms
      message: 'load-balancer-api-internal: tcp connection to ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:32Z"
    - latency: 8.133039ms
      message: 'load-balancer-api-internal: resolved host name ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:32Z"
    - latency: 3.851912ms
      message: 'load-balancer-api-internal: tcp connection to ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:32Z"
    - latency: 8.430338ms
      message: 'load-balancer-api-internal: resolved host name ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:32Z"
    - latency: 3.215579ms
      message: 'load-balancer-api-internal: tcp connection to ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:32Z"
    - latency: 8.784747ms
      message: 'load-balancer-api-internal: resolved host name ac4ec50f088124032b75e900c8b79202-fd2f6c203ff32c9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-142-to-network-check-target-ip-10-0-128-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-142.ec2.internal
      uid: 11f1157e-1330-40f6-82eb-c6335afffc78
    resourceVersion: "53829"
    uid: c021ec13-1cad-4bd3-84d2-ae40f90daab4
  spec:
    sourcePod: network-check-source-6f8b768455-p9rh5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:09:32Z"
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.465836ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:32Z"
    - latency: 2.347122ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:32Z"
    - latency: 2.425625ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:32Z"
    - latency: 2.525239ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:32Z"
    - latency: 2.257205ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:32Z"
    - latency: 2.399993ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:32Z"
    - latency: 2.447037ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:32Z"
    - latency: 2.636423ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:32Z"
    - latency: 2.362976ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:32Z"
    - latency: 2.796105ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-142-to-network-check-target-ip-10-0-135-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-142.ec2.internal
      uid: 11f1157e-1330-40f6-82eb-c6335afffc78
    resourceVersion: "53828"
    uid: 10e4e293-06ad-4c47-8c05-cf604248f494
  spec:
    sourcePod: network-check-source-6f8b768455-p9rh5
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:09:32Z"
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.020315ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:32Z"
    - latency: 918.399µs
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:32Z"
    - latency: 1.12911ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:32Z"
    - latency: 1.02235ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:32Z"
    - latency: 934.103µs
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:32Z"
    - latency: 886.176µs
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:32Z"
    - latency: 1.176847ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:32Z"
    - latency: 1.109072ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:32Z"
    - latency: 1.135366ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:32Z"
    - latency: 1.000194ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-142-to-network-check-target-ip-10-0-135-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-142.ec2.internal
      uid: 11f1157e-1330-40f6-82eb-c6335afffc78
    resourceVersion: "53830"
    uid: 95090fff-3710-458a-9249-5fa65c54649d
  spec:
    sourcePod: network-check-source-6f8b768455-p9rh5
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:09:32Z"
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.562813ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:32Z"
    - latency: 2.477769ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:32Z"
    - latency: 2.733343ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:32Z"
    - latency: 2.664831ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:32Z"
    - latency: 2.270835ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:32Z"
    - latency: 2.103662ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:32Z"
    - latency: 2.50332ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:32Z"
    - latency: 2.56372ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:32Z"
    - latency: 2.374879ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:32Z"
    - latency: 2.195519ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-142.ec2.internal
      uid: 11f1157e-1330-40f6-82eb-c6335afffc78
    resourceVersion: "55549"
    uid: bb8058d5-e975-4df6-8f38-52baf36c6082
  spec:
    sourcePod: network-check-source-6f8b768455-p9rh5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 980.742µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:32:32Z"
    - latency: 1.817534ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:32:32Z"
    - latency: 1.102721ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:31:32Z"
    - latency: 1.874092ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:31:32Z"
    - latency: 940.847µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:32Z"
    - latency: 1.936628ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:32Z"
    - latency: 1.138281ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:32Z"
    - latency: 1.901199ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:32Z"
    - latency: 936.433µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:32Z"
    - latency: 1.940007ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:32Z"
kind: List
metadata:
  resourceVersion: ""