Explanation
Using kubectl logs deployment api does not display the events table for this object. The kubectl logs command shows the logs of a pod or a container in a pod, but it does not show the events related to the deployment object. To see the events table for this object, you need to use kubectl describe deployment api. References:
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#logs,
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#describe

Explanation
Setting and exporting the IGNORE_TLS environment variable on the command line is not a way to configure the Docker engine to use a registry without a trusted TLS certificate. The IGNORE_TLS environment variable is not recognized by Docker and has no effect on its behavior. To configure the Docker engine to use a registry without a trusted TLS certificate, you need to either set INSECURE_REGISTRY in the /etc/docker/default configuration file or add --insecure-registry flag to the dockerd command. References:
https://docs.docker.com/registry/insecure/,
https://docs.docker.com/engine/reference/commandline/dockerd/#insecure-registries

Explanation
This command does not mount the host's /data directory to the ubuntu container in read-only mode. The -v or
--volume flag mounts a host directory or a named volume to a container. The syntax for mounting a host directory is -v <host-path>:<container-path>[:<options>]. The options can be ro for read-only mode, rw for read-write mode, z or Z for SELinux labels, etc. In this command, -mode readonly is not a valid option and will cause an error. To mount the host's /data directory to the ubuntu container in read-only mode, you need to use -v /data:/mydata:ro instead. References: https://docs.docker.com/storage/bind-mounts/,
https://docs.docker.com/engine/reference/run/#volume-shared-filesystems

The purpose of Docker Content Trust is not to indicate an image on Docker Hub is an official image. Docker Content Trust is a feature that allows users to verify the integrity and publisher of container images they pull or deploy from a registry server, signed on a Notary server1. Docker Content Trust uses digital signatures to ensure that the images are authentic and have not been tampered with2. Official images are a curated set of Docker repositories that are designed to be the best starting point for most users3. They are not necessarily signed by Docker Content Trust, although some of them are. To indicate an image on Docker Hub is an official image, you can look for the blue "official image" badge on the image page. References:
* Content trust in Docker | Docker Docs
* Docker Content Trust: What It Is and How It Secures Container Images
* Official Images on Docker Hub | Docker Docs
* [Docker Hub Quickstart | Docker Docs]