-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting no TLS certificate is found on the local machine
error
#211
Comments
@estherkim11111 can you try using a more recent version? The latest release is |
@kerneltime we need to use that version for that version of the api |
@estherkim11111 unfortunately we cannot support v1beta1 anymore please upgrade your k8s versions. |
AFAICS, nothing to be done here from MinIO. Closing |
Signed-off-by: Jason Montleon <jmontleo@redhat.com>
FYI @harshavardhana
Any pointers about what steps I could be missing, something I could be doing wrong, or a better interpretation of the error message below would be appreciated.
Expected Behavior
minio pods should come up healthy with no errors in the logs
Current Behavior
getting in minio pod logs
even though I have specified in the minioinstance yaml
and created a secret called tls-ssl-minio following https://github.com/minio/operator/blob/1.0.9/docs/tls.md#using-kubernetes-tls and https://docs.min.io/docs/how-to-secure-access-to-minio-server-with-tls
This can be seen in the pod yaml:
and
Possible Solution
Steps to Reproduce (for bugs)
kubectl apply -f https://raw.githubusercontent.com/minio/minio-operator/1.0.9/minio-operator.yaml
wget https://raw.githubusercontent.com/minio/minio-operator/1.0.9/examples/minioinstance-with-external-service.yaml
storageClassName
under volumeClaimTemplate (for me I put portworx-db-gp3)kubectl apply -f minioinstance-with-external-service.yaml
Context
Regression
Your Environment
minio-operator
):uname -a
):The text was updated successfully, but these errors were encountered: