apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:56:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-23-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-23.ec2.internal
      uid: a4639416-db78-485b-873f-186dee162ca5
    resourceVersion: "60228"
    uid: 399c83f1-ed49-4098-af63-eef28f0f7da5
  spec:
    sourcePod: network-check-source-869dcfcdcd-6qq5j
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:03:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.336437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:38:48Z"
    - latency: 804.504µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:37:48Z"
    - latency: 826.787µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:36:48Z"
    - latency: 1.228553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:35:48Z"
    - latency: 1.082991ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:34:48Z"
    - latency: 1.443761ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:33:48Z"
    - latency: 1.035198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:32:48Z"
    - latency: 1.687713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:31:48Z"
    - latency: 1.149813ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:30:48Z"
    - latency: 1.15867ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:29:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:56:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-23-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-23.ec2.internal
      uid: a4639416-db78-485b-873f-186dee162ca5
    resourceVersion: "60230"
    uid: 1a19bb79-5228-4da0-9d1f-028a7e74e015
  spec:
    sourcePod: network-check-source-869dcfcdcd-6qq5j
    targetEndpoint: aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:02:48Z"
      message: 'load-balancer-api-external: tcp connection to aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.724924ms
      message: 'load-balancer-api-external: tcp connection to aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:38:48Z"
    - latency: 8.717221ms
      message: 'load-balancer-api-external: resolved host name aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:38:48Z"
    - latency: 5.272915ms
      message: 'load-balancer-api-external: tcp connection to aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:37:48Z"
    - latency: 7.981058ms
      message: 'load-balancer-api-external: resolved host name aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:37:48Z"
    - latency: 3.859861ms
      message: 'load-balancer-api-external: tcp connection to aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:36:48Z"
    - latency: 8.38368ms
      message: 'load-balancer-api-external: resolved host name aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:36:48Z"
    - latency: 3.566085ms
      message: 'load-balancer-api-external: tcp connection to aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:35:48Z"
    - latency: 8.331117ms
      message: 'load-balancer-api-external: resolved host name aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:35:48Z"
    - latency: 5.523173ms
      message: 'load-balancer-api-external: tcp connection to aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:34:48Z"
    - latency: 8.558777ms
      message: 'load-balancer-api-external: resolved host name aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:34:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:56:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-23-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-23.ec2.internal
      uid: a4639416-db78-485b-873f-186dee162ca5
    resourceVersion: "60229"
    uid: d85334e6-74c4-4ba8-a541-60b31d74c998
  spec:
    sourcePod: network-check-source-869dcfcdcd-6qq5j
    targetEndpoint: aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:02:48Z"
      message: 'load-balancer-api-internal: tcp connection to aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.056016ms
      message: 'load-balancer-api-internal: tcp connection to aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:38:48Z"
    - latency: 8.63178ms
      message: 'load-balancer-api-internal: resolved host name aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:38:48Z"
    - latency: 5.602344ms
      message: 'load-balancer-api-internal: tcp connection to aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:37:48Z"
    - latency: 8.185295ms
      message: 'load-balancer-api-internal: resolved host name aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:37:48Z"
    - latency: 6.200195ms
      message: 'load-balancer-api-internal: tcp connection to aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:36:48Z"
    - latency: 8.303502ms
      message: 'load-balancer-api-internal: resolved host name aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:36:48Z"
    - latency: 3.507155ms
      message: 'load-balancer-api-internal: tcp connection to aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:35:48Z"
    - latency: 8.150735ms
      message: 'load-balancer-api-internal: resolved host name aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:35:48Z"
    - latency: 5.569285ms
      message: 'load-balancer-api-internal: tcp connection to aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:34:48Z"
    - latency: 8.592399ms
      message: 'load-balancer-api-internal: resolved host name aee268ab3b1484599b0e6ca004fd29c6-ee81e7188f3a28f5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:34:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:56:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-23-to-network-check-target-ip-10-0-132-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-23.ec2.internal
      uid: a4639416-db78-485b-873f-186dee162ca5
    resourceVersion: "60226"
    uid: 0b3c6ebd-693e-4d2c-9e05-ad650970b64f
  spec:
    sourcePod: network-check-source-869dcfcdcd-6qq5j
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:03:48Z"
      message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.271283ms
      message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:38:48Z"
    - latency: 2.17604ms
      message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:37:48Z"
    - latency: 1.775766ms
      message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:36:48Z"
    - latency: 2.623ms
      message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:35:48Z"
    - latency: 2.2962ms
      message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:34:48Z"
    - latency: 2.376535ms
      message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:33:48Z"
    - latency: 2.384963ms
      message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:32:48Z"
    - latency: 2.922172ms
      message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:31:48Z"
    - latency: 2.48211ms
      message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:30:48Z"
    - latency: 2.089906ms
      message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:29:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:56:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-23-to-network-check-target-ip-10-0-141-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-23.ec2.internal
      uid: a4639416-db78-485b-873f-186dee162ca5
    resourceVersion: "60225"
    uid: 87ede0b6-04eb-4ea6-aa9b-74f15359f0a2
  spec:
    sourcePod: network-check-source-869dcfcdcd-6qq5j
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:03:48Z"
      message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.618473ms
      message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:38:48Z"
    - latency: 1.273504ms
      message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:37:48Z"
    - latency: 754.722µs
      message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:36:48Z"
    - latency: 879.972µs
      message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:35:48Z"
    - latency: 876.848µs
      message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:34:48Z"
    - latency: 903.123µs
      message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:33:48Z"
    - latency: 861.388µs
      message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:32:48Z"
    - latency: 1.005654ms
      message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:31:48Z"
    - latency: 962.191µs
      message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:30:48Z"
    - latency: 978.094µs
      message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:29:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:56:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-23-to-network-check-target-ip-10-0-143-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-23.ec2.internal
      uid: a4639416-db78-485b-873f-186dee162ca5
    resourceVersion: "60224"
    uid: 8a23809a-8f22-4773-932d-376a958f832c
  spec:
    sourcePod: network-check-source-869dcfcdcd-6qq5j
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:03:48Z"
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.965628ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:38:48Z"
    - latency: 1.872086ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:37:48Z"
    - latency: 1.604331ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:36:48Z"
    - latency: 2.414189ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:35:48Z"
    - latency: 2.06846ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:34:48Z"
    - latency: 1.839031ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:33:48Z"
    - latency: 1.866253ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:32:48Z"
    - latency: 1.809011ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:31:48Z"
    - latency: 2.377419ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:30:48Z"
    - latency: 1.999904ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:29:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:56:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-23-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-23.ec2.internal
      uid: a4639416-db78-485b-873f-186dee162ca5
    resourceVersion: "60227"
    uid: 0dd9f303-c734-4e5f-bb3e-26f845211063
  spec:
    sourcePod: network-check-source-869dcfcdcd-6qq5j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T22:02:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.424395ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:38:48Z"
    - latency: 1.605591ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:38:48Z"
    - latency: 1.028144ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:37:48Z"
    - latency: 1.614207ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:37:48Z"
    - latency: 874.716µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:36:48Z"
    - latency: 1.683382ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:36:48Z"
    - latency: 953.707µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:35:48Z"
    - latency: 1.674903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:35:48Z"
    - latency: 1.06676ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T22:34:48Z"
    - latency: 1.847162ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T22:34:48Z"
kind: List
metadata:
  resourceVersion: ""