Troubleshooting Guide

Cluster with proxy

To allow the Nirmata Kubernetes Controller to connect successfully in a cluster with a proxy environment, edit the nirmata-kube-controller deployment by running the following command on any node that has kubectl installed:

kubectl edit deployment nirmata-kube-controller -n nirmata

Add the environment variables NO_PROXY, HTTP_PROXY, and HTTPS_PROXY with their respective values under the env of the container in nirmata-kube-controller deployment and then save to apply the changes.

env:
- name: TOKEN
  ...
- name: NO_PROXY
  value: <IP_ADDR>
- name: HTTP_PROXY
  value: http://<PROXY_SERVER>:<PROXY_PORT>
- name: HTTPS_PROXY
  value: https://<PROXY_SERVER>:<PROXY_PORT>
  ...

Verify nirmata-kube-controller installation

To check if the Nirmata Kubernetes Controller was installed correctly, run this command to verify the controller pod is running:

kubectl get pod -n nirmata

Reinstalling Nirmata Kubernetes Controller

If the Nirmata Kubernetes Controller is not installed or has failed, you can remove existing resources by running the commands given below:

kubectl delete namespaces nirmata

kubectl delete clusterrolebindings nirmata-cluster-admin-binding

kubectl delete clusterrolebindings nirmata-controller-binding

kubectl delete clusterroles nirmata:nirmata-readonly

And then install the Nirmata Kubernetes Controller by downloading the YAML from the Nirmata Control Hub and running this command:

kubectl create -f nirmata-kube-controller.yaml

NOTE: The name of the downloaded manifest YAML file may be different, so use the appropriate filename in the commands.