There are cases where the Helm chart may not require credentials to access the Deepgram container image repositories hosted on Quay. This PR removes the firm requirement to include these credentials as a pull secret for pulling container images.
For example, a client may pull the images from Quay manually and push them into a private company repository that meets certain security or scanning requirements. Credentials to that private repo may be pre-configured in the cluster, so the pull secret shouldn't be mandatory.
Another case is if a Docker proxy is being used and credentials are supplied in the proxy. Then the credentials don't need to be exposed directly in the cluster with this Helm chart.
There are cases where the Helm chart may not require credentials to access the Deepgram container image repositories hosted on Quay. This PR removes the firm requirement to include these credentials as a pull secret for pulling container images.
For example, a client may pull the images from Quay manually and push them into a private company repository that meets certain security or scanning requirements. Credentials to that private repo may be pre-configured in the cluster, so the pull secret shouldn't be mandatory.
Another case is if a Docker proxy is being used and credentials are supplied in the proxy. Then the credentials don't need to be exposed directly in the cluster with this Helm chart.
Resolves #14.