kubectl get all –all-namespaces | grep name
From here.
helm with tls cert
After following steps in guide to create certs:
$ cp ca.cert.pem ~/.helm/ca.pem
$ cp helm.cert.pem ~/.helm/cert.pem
$ cp helm.key.pem ~/.helm/key.pem
Then use the –tls options:
$ helm ls --tls
Kubernetes: can’t schedule a pod on master node
Attempting to run a pod on the master and get this error:
Warning FailedScheduling 14m (x2 over 14m) default-scheduler 0/1 nodes are available: 1 node(s) had taints that the pod didn't tolerate.
From issue here: you can configure the master node to run pods with:
kubectl taint nodes --all node-role.kubernetes.io/master-
Running GitLab in a Docker container on a different port
Gitlab by default runs on port 80. GitLab in a Docker container runs the same as a when natively installed, but to change the port you need to change the config, and change the exposed ports on the container.
First, per steps here, start the container with:
docker run --detach \
--hostname gitlab.example.com \
--publish host-https-port:container-https-port
--publish host-http-port:container-http-port
--publish 22:22 \
--name gitlab \
--restart always \
--volume /srv/gitlab/config:/etc/gitlab \
--volume /srv/gitlab/logs:/var/log/gitlab \
--volume /srv/gitlab/data:/var/opt/gitlab \
gitlab/gitlab-ce:latest
By default host-http-port and container-http-port are 80, and host-https-port container-https-port are 443. Change these to be whatever port you want to run on, but keep each pair the same (e.g. host-http-port and container-http-port = 8090)
When the container is up, start a shell into the running container:
docker exec -it containerid sh
and then edit the config file:
vi /etc/gitlab/gitlab.rb
and add line (at the top is ok):
external_url 'http://localhost:your-new-port-here
setting your-new-port-here to the new port.
Reconfigure the server:
gitlab-ctl reconfigure
gitlab-ctl restart
Done!