apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:20:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-65-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-65.ec2.internal
      uid: d0d27d36-0035-43dd-9213-e1e6eacded4f
    resourceVersion: "64713"
    uid: 7acdc149-1975-41e4-acf2-eb8075886605
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h4j7n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:27:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.05671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:02:30Z"
    - latency: 1.349037ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:01:30Z"
    - latency: 1.066463ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:00:30Z"
    - latency: 1.293661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:59:30Z"
    - latency: 984.216µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:58:30Z"
    - latency: 823.405µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:57:30Z"
    - latency: 1.387454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:56:30Z"
    - latency: 2.045283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:55:30Z"
    - latency: 1.351456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:54:30Z"
    - latency: 1.277966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:53:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:20:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-65-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-65.ec2.internal
      uid: d0d27d36-0035-43dd-9213-e1e6eacded4f
    resourceVersion: "64714"
    uid: d2f100bc-0e6f-44dc-b29c-d0a09e790759
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h4j7n
    targetEndpoint: a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:26:30Z"
      message: 'load-balancer-api-external: tcp connection to a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.603895ms
      message: 'load-balancer-api-external: tcp connection to a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:02:30Z"
    - latency: 7.512423ms
      message: 'load-balancer-api-external: resolved host name a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:02:30Z"
    - latency: 5.086711ms
      message: 'load-balancer-api-external: tcp connection to a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:01:30Z"
    - latency: 7.291491ms
      message: 'load-balancer-api-external: resolved host name a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:01:30Z"
    - latency: 4.352072ms
      message: 'load-balancer-api-external: tcp connection to a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:00:30Z"
    - latency: 7.857338ms
      message: 'load-balancer-api-external: resolved host name a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:00:30Z"
    - latency: 4.170548ms
      message: 'load-balancer-api-external: tcp connection to a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:59:30Z"
    - latency: 6.866123ms
      message: 'load-balancer-api-external: resolved host name a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T18:59:30Z"
    - latency: 4.396868ms
      message: 'load-balancer-api-external: tcp connection to a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:58:30Z"
    - latency: 7.109986ms
      message: 'load-balancer-api-external: resolved host name a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T18:58:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:20:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-65-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-65.ec2.internal
      uid: d0d27d36-0035-43dd-9213-e1e6eacded4f
    resourceVersion: "64715"
    uid: a17ce301-298e-4388-9412-09daa95c1207
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h4j7n
    targetEndpoint: a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:26:30Z"
      message: 'load-balancer-api-internal: tcp connection to a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.584035ms
      message: 'load-balancer-api-internal: tcp connection to a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:02:30Z"
    - latency: 7.425135ms
      message: 'load-balancer-api-internal: resolved host name a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:02:30Z"
    - latency: 5.094107ms
      message: 'load-balancer-api-internal: tcp connection to a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:01:30Z"
    - latency: 7.262671ms
      message: 'load-balancer-api-internal: resolved host name a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:01:30Z"
    - latency: 4.346237ms
      message: 'load-balancer-api-internal: tcp connection to a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:00:30Z"
    - latency: 7.794883ms
      message: 'load-balancer-api-internal: resolved host name a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:00:30Z"
    - latency: 4.172644ms
      message: 'load-balancer-api-internal: tcp connection to a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:59:30Z"
    - latency: 6.800543ms
      message: 'load-balancer-api-internal: resolved host name a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T18:59:30Z"
    - latency: 4.087358ms
      message: 'load-balancer-api-internal: tcp connection to a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:58:30Z"
    - latency: 7.084034ms
      message: 'load-balancer-api-internal: resolved host name a8aca785ffa4242639b00379264c3dd5-bd0a015ea114296c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T18:58:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:20:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-65-to-network-check-target-ip-10-0-128-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-65.ec2.internal
      uid: d0d27d36-0035-43dd-9213-e1e6eacded4f
    resourceVersion: "64710"
    uid: 90dff72c-3b06-4061-a062-bcaf4d72f6d1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h4j7n
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:27:30Z"
      message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.382445ms
      message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:02:30Z"
    - latency: 2.197151ms
      message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:01:30Z"
    - latency: 2.656015ms
      message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:00:30Z"
    - latency: 2.54383ms
      message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:59:30Z"
    - latency: 2.117337ms
      message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:58:30Z"
    - latency: 1.86678ms
      message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:57:30Z"
    - latency: 2.651748ms
      message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:56:30Z"
    - latency: 2.821179ms
      message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:55:30Z"
    - latency: 2.294958ms
      message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:54:30Z"
    - latency: 2.394062ms
      message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:53:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:20:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-65-to-network-check-target-ip-10-0-132-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-65.ec2.internal
      uid: d0d27d36-0035-43dd-9213-e1e6eacded4f
    resourceVersion: "64709"
    uid: 8244fd46-d2ec-4efa-b805-75a686878918
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h4j7n
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:27:30Z"
      message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.395278ms
      message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:02:30Z"
    - latency: 1.309469ms
      message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:01:30Z"
    - latency: 970.171µs
      message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:00:30Z"
    - latency: 1.006249ms
      message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:59:30Z"
    - latency: 1.169171ms
      message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:58:30Z"
    - latency: 1.027272ms
      message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:57:30Z"
    - latency: 1.742402ms
      message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:56:30Z"
    - latency: 2.251343ms
      message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:55:30Z"
    - latency: 1.746058ms
      message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:54:30Z"
    - latency: 2.139205ms
      message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:53:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:20:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-65-to-network-check-target-ip-10-0-141-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-65.ec2.internal
      uid: d0d27d36-0035-43dd-9213-e1e6eacded4f
    resourceVersion: "64712"
    uid: aa4c898d-6034-4901-a4d0-5db6717d1cd4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h4j7n
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:27:30Z"
      message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.412702ms
      message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:02:30Z"
    - latency: 2.034672ms
      message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:01:30Z"
    - latency: 2.673734ms
      message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:00:30Z"
    - latency: 2.455033ms
      message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:59:30Z"
    - latency: 2.919491ms
      message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:58:30Z"
    - latency: 1.81167ms
      message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:57:30Z"
    - latency: 2.728055ms
      message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:56:30Z"
    - latency: 2.872239ms
      message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:55:30Z"
    - latency: 2.475402ms
      message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:54:30Z"
    - latency: 2.288558ms
      message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:53:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:20:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-65-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-65.ec2.internal
      uid: d0d27d36-0035-43dd-9213-e1e6eacded4f
    resourceVersion: "64711"
    uid: dfad751f-19bc-41bf-8aab-02886ea732e7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h4j7n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:26:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 815.915µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:02:30Z"
    - latency: 2.363471ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:02:30Z"
    - latency: 972.4µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:01:30Z"
    - latency: 1.946677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:01:30Z"
    - latency: 918.689µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:00:30Z"
    - latency: 1.992504ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:00:30Z"
    - latency: 917.507µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:59:30Z"
    - latency: 1.935345ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T18:59:30Z"
    - latency: 1.073663ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T18:58:30Z"
    - latency: 2.555523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T18:58:30Z"
kind: List
metadata:
  resourceVersion: ""