We'll create the same Jenkins objects we defined earlier:
kubectl create \
-f secret/jenkins-unprotected.yml \
--record --save-config
kubectl rollout status deploy jenkins
We created an Ingress, a Deployment, and a Service object. We also executed the kubectl rollout status command that will tell us when the deployment is finished.
The secret/jenkins-unprotected.yml definition does not use any new feature so we won't waste time going through the YAML file. Instead, we'll open Jenkins UI in a browser.
open "http://$(minikube ip)/jenkins"
Upon closer inspection, you'll notice that there is no login button. Jenkins is currently unprotected. The image does allow the option to define an initial administrative username and password. If the files /etc/secrets/jenkins-user and /etc/secrets/jenkins-pass are present...
