The sample below uses the NGINX ingress controller to establish a deployment and expose it. Because SSL will be utilized by default and produce an error for a nonexistent certificate, it’s critical to pay attention to the annotation nginx.ingress.kubernetes.io/ssl-redirect: “false”.
The domain name that is used is another crucial factor. I’m going to use the domain name test.localhost, but you should obviously change it to your own and direct it to your k3s instance node.
Create a file called my-example.yaml and use the following syntax to implement this example for Ingress testing:
kubectl cluster-info
kubectl get nodes
kubectl get pods -A
kubectl config get-contexts
kubectl get all --all-namespaces
Copy k3s config file
1
sudo cp /etc/rancher/k3s/k3s.yaml ~/.kube/config
Change owner to user for k3s config file
1
sudo chown -R $USER:$USER /home/$USER
Install k9s
In order to communicate with your Kubernetes clusters, K9s offers a terminal UI. This project’s goal is to make it simpler to use, monitor, and administer your apps in the field. K9s continuously scans Kubernetes for modifications and provides follow-up commands to interact with the resources you have selected.