apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:24:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-50-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-50.ec2.internal
      uid: 9830ac70-8dcf-41ec-8386-72f50dd5fbdf
    resourceVersion: "53262"
    uid: ce6e7c0b-a6e2-4801-81d9-10807054d66e
  spec:
    sourcePod: network-check-source-6f8b768455-jtrvr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:31:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.225652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:52:50Z"
    - latency: 966.611µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:51:50Z"
    - latency: 1.223143ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:50:50Z"
    - latency: 1.017205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:49:50Z"
    - latency: 1.097495ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:48:50Z"
    - latency: 1.693205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:47:50Z"
    - latency: 1.011775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:46:50Z"
    - latency: 1.186887ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:45:50Z"
    - latency: 977.324µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:44:50Z"
    - latency: 965.98µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:43:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:24:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-50-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-50.ec2.internal
      uid: 9830ac70-8dcf-41ec-8386-72f50dd5fbdf
    resourceVersion: "54382"
    uid: fe58ad61-f170-4c3c-b6f7-378ef46af07c
  spec:
    sourcePod: network-check-source-6f8b768455-jtrvr
    targetEndpoint: af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:30:50Z"
      message: 'load-balancer-api-external: tcp connection to af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.24716ms
      message: 'load-balancer-api-external: tcp connection to af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:54:50Z"
    - latency: 14.518602ms
      message: 'load-balancer-api-external: resolved host name af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:54:50Z"
    - latency: 5.142883ms
      message: 'load-balancer-api-external: tcp connection to af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:53:50Z"
    - latency: 8.685915ms
      message: 'load-balancer-api-external: resolved host name af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:53:50Z"
    - latency: 6.2208ms
      message: 'load-balancer-api-external: tcp connection to af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:52:50Z"
    - latency: 8.739238ms
      message: 'load-balancer-api-external: resolved host name af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:52:50Z"
    - latency: 4.725652ms
      message: 'load-balancer-api-external: tcp connection to af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:51:50Z"
    - latency: 8.773954ms
      message: 'load-balancer-api-external: resolved host name af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:51:50Z"
    - latency: 4.419593ms
      message: 'load-balancer-api-external: tcp connection to af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:50:50Z"
    - latency: 12.786675ms
      message: 'load-balancer-api-external: resolved host name af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:50:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:24:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-50-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-50.ec2.internal
      uid: 9830ac70-8dcf-41ec-8386-72f50dd5fbdf
    resourceVersion: "54381"
    uid: ee09e5fb-5378-403a-a81b-8f3a50d8805a
  spec:
    sourcePod: network-check-source-6f8b768455-jtrvr
    targetEndpoint: af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:30:50Z"
      message: 'load-balancer-api-internal: tcp connection to af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.256799ms
      message: 'load-balancer-api-internal: tcp connection to af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:54:50Z"
    - latency: 14.472303ms
      message: 'load-balancer-api-internal: resolved host name af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:54:50Z"
    - latency: 12.877802ms
      message: 'load-balancer-api-internal: tcp connection to af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:53:50Z"
    - latency: 8.580561ms
      message: 'load-balancer-api-internal: resolved host name af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:53:50Z"
    - latency: 6.226095ms
      message: 'load-balancer-api-internal: tcp connection to af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:52:50Z"
    - latency: 8.685125ms
      message: 'load-balancer-api-internal: resolved host name af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:52:50Z"
    - latency: 5.769356ms
      message: 'load-balancer-api-internal: tcp connection to af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:51:50Z"
    - latency: 8.654151ms
      message: 'load-balancer-api-internal: resolved host name af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:51:50Z"
    - latency: 4.396938ms
      message: 'load-balancer-api-internal: tcp connection to af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:50:50Z"
    - latency: 12.650205ms
      message: 'load-balancer-api-internal: resolved host name af1c78e67edfe4276a915815e6ff0a46-96b710c2f80060af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:50:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:24:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-50-to-network-check-target-ip-10-0-132-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-50.ec2.internal
      uid: 9830ac70-8dcf-41ec-8386-72f50dd5fbdf
    resourceVersion: "53260"
    uid: a7da9ffb-efed-46f1-b73c-5b730c6b95e3
  spec:
    sourcePod: network-check-source-6f8b768455-jtrvr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:31:50Z"
      message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.484575ms
      message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:52:50Z"
    - latency: 2.726328ms
      message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:51:50Z"
    - latency: 2.34983ms
      message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:50:50Z"
    - latency: 2.678671ms
      message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:49:50Z"
    - latency: 2.445434ms
      message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:48:50Z"
    - latency: 2.719782ms
      message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:47:50Z"
    - latency: 2.297753ms
      message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:46:50Z"
    - latency: 2.768143ms
      message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:45:50Z"
    - latency: 2.500912ms
      message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:44:50Z"
    - latency: 2.14385ms
      message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:43:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:24:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-50-to-network-check-target-ip-10-0-140-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-50.ec2.internal
      uid: 9830ac70-8dcf-41ec-8386-72f50dd5fbdf
    resourceVersion: "53263"
    uid: 3433b0ad-8675-4958-b48b-da979dd6b756
  spec:
    sourcePod: network-check-source-6f8b768455-jtrvr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:31:50Z"
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.345728ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:52:50Z"
    - latency: 2.192449ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:51:50Z"
    - latency: 2.467948ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:50:50Z"
    - latency: 2.543613ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:49:50Z"
    - latency: 2.445358ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:48:50Z"
    - latency: 2.399243ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:47:50Z"
    - latency: 2.654575ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:46:50Z"
    - latency: 2.259696ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:45:50Z"
    - latency: 2.536676ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:44:50Z"
    - latency: 2.399015ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:43:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:24:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-50-to-network-check-target-ip-10-0-141-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-50.ec2.internal
      uid: 9830ac70-8dcf-41ec-8386-72f50dd5fbdf
    resourceVersion: "53261"
    uid: 6aa5012a-8140-4575-a60f-6bc1facd710d
  spec:
    sourcePod: network-check-source-6f8b768455-jtrvr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:31:50Z"
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.457454ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:52:50Z"
    - latency: 970.432µs
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:51:50Z"
    - latency: 1.050451ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:50:50Z"
    - latency: 1.185774ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:49:50Z"
    - latency: 1.80788ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:48:50Z"
    - latency: 886.543µs
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:47:50Z"
    - latency: 1.006493ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:46:50Z"
    - latency: 1.441081ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:45:50Z"
    - latency: 1.177363ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:44:50Z"
    - latency: 1.105786ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:43:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:24:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-50-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-50.ec2.internal
      uid: 9830ac70-8dcf-41ec-8386-72f50dd5fbdf
    resourceVersion: "54380"
    uid: 779fc9b2-a226-4cda-bf77-487ce94ce860
  spec:
    sourcePod: network-check-source-6f8b768455-jtrvr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:30:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 888.27µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:54:50Z"
    - latency: 1.84565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:54:50Z"
    - latency: 958.347µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:53:50Z"
    - latency: 1.85648ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:53:50Z"
    - latency: 1.628415ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:52:50Z"
    - latency: 1.856734ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:52:50Z"
    - latency: 969.972µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:51:50Z"
    - latency: 1.854352ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:51:50Z"
    - latency: 1.078344ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:50:50Z"
    - latency: 2.43438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:50:50Z"
kind: List
metadata:
  resourceVersion: ""