docs/static/v0.9/installation/kubernetes/index.html
Manage your Kubernetes clusters with Meshery. Deploy Meshery in Kubernetes in-cluster or outside of Kubernetes out-of-cluster. Note: It is advisable to install Meshery in your Kubernetes clusters
Follow the steps below to install Meshery in your Kubernetes cluster.
Read through the following considerations prior to deploying Meshery on Kubernetes.
Verify your kubeconfig’s current context is set to the Kubernetes cluster you want to deploy Meshery to.
`kubectl config current-context`
mesheryctlOnce configured, execute the following command to start Meshery.
Before executing the below command, go to ~/.meshery/config.yaml and ensure that the current platform is set to Kubernetes.
`mesheryctl system start`
For detailed instructions on installing Meshery using Helm V3, please refer to the Helm Installation guide.
Optionally, you can verify the health of your Meshery deployment using mesheryctl system check.
You’re ready to use Meshery! Open your browser and navigate to the Meshery UI.
After successfully deploying Meshery, you can access Meshery's web-based user interface. Your default browser will automatically open and navigate to Meshery UI (default location is http://localhost:9081).
You can use the following command to open Meshery UI in your default browser:
`mesheryctl system dashboard`
If you have installed Meshery on Kubernetes or a remote host, you can access Meshery UI by exposing it as a Kubernetes service or by port forwarding to Meshery UI.
`mesheryctl system dashboard --port-forward`
Depending on how you have networking configured in Kubernetes, you can use kubectl to port forward to the Meshery UI.
`kubectl port-forward svc/meshery 9081:9081 --namespace meshery`
After installing Meshery, regardless of the installation type, it is important to verify that your kubeconfig file has been uploaded correctly via the UI.
Connected.#Customizing Your Meshery Provider Callback URL
Meshery Server supports customizing your Meshery Provider authentication flow callback URL. This is helpful when deploying Meshery behind multiple layers of networking infrastructure.
For production deployments, it is recommended to access the Meshery UI by setting up a reverse proxy or using a LoadBalancer. By specifying a custom redirect endpoint, you can ensure that authentication flows complete successfully, even when multiple routing layers are involved.
Note : For production deployments, it is important to select the Remote Provider in order to control which identity providers are authorized. Learn more about this in the Extensibility: Providers guide.
Define a custom callback URL by setting up the MESHERY_SERVER_CALLBACK_URL environment variable before installing Meshery.
To customize the authentication flow callback URL, use the following command:
`MESHERY_SERVER_CALLBACK_URL=https://custom-host mesheryctl system start`
Meshery should now be running in your Kubernetes cluster and the Meshery UI should be accessible at the EXTERNAL IP of the meshery service.
Install Meshery on Docker (out-of-cluster) and connect it to your Kubernetes cluster.
`minikube addons enable ingress`
`kubectl get pods -n ingress-nginx`
`kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.15.3/cert-manager.yaml`
View all discussions tagged with meshery
[ Previous
GitHub Codespaces ](/v0.9/installation/codespaces)[ Next
AKS ](/v0.9/installation/kubernetes/aks)