This was super helpful - Thank you !!!
Since my original post, I’ve moved from my Windows laptop over to an EC2 instance on AWS. It is Amazon Linux and I’m using minikube on docker. Without the extra VirtualBox layer, I was able to run your command using eth0 as the interface name. I can browse to port 8443 and get a response (403 forbidden, but I know it is serving).
I’ve got connectivity now, but the error message in gitlab.com changed to “There was a problem authenticating with your cluster. Please ensure your CA Certificate and Token are valid.”
I’ve checked my CA Certificate and Service Token at least 10 times. I’ve pasted them into notepad, then recopied them out of notepad into the browser. No extra spaces or line feeds. I still get this error.
When I use postman, I’m able to set up a client certificate using these two files (pulled from .kube/config):
- name: minikube
In postman, I can add the crt and key and hit the endpoint. It responds back with a list of valid API endpoints.
I created a gitlab authentication token using the instructions here:
I created the yaml file and ran it. The output was:
I deleted the certificate in postman and instead specified bearer token for my request and pasted the token text into the token field (I assume you don’t need any other usernames or keys to use a token in postman), but I get the 403 forbidden response in postman with the token. Is there something else I need to do to get the token based authentication to work correctly in minikube?