Access Fluid Kube Clusters¶
Once your Kube cluster has deployed, accessing your cluster is as simple as downloading a kubeconfig file from the BlueXP interface and using your Kubernetes management tools of choice.
If you’re managing multiple Kubernetes environments from the CLI, we recommend and endorse the following open-source projects for accessing and switching between clusters:
Fluid isn’t associated with these projects, we just think they’re awesome!
Installing kubectl
If you’re looking to manage Fluid’s Kube environments from your CLI, like you would any other Kube cluster, you may need to install kubectl on your machine. Refer to the following official Kubernetes documentation for your system.
Accessing your Fluid!
Select your new cluster from the Kubernetes table in the Fluid Console. Here you’ll see what services are running in your cluster, and what LoadBalancers have been created. Given this is a new clusters, these are most likely to be blank right now.
Download your Kubeconfig file from the interface by selecting the Download Kubeconfig button. Place this file alongside your Kubernetes config files, on POSIX systems, it’s likely to live at ~/.kube/. If you already have existing Kube files, you can combine them by running the following.
cp ~/.kube/config ~/.kube/config.bak && KUBECONFIG=~/.kube/config:~/.kube/fluid-kube-ctl.yml kubectl config view --flatten > /tmp/config && mv /tmp/config ~/.kube/config
Alternatively you can access the environment using kubectl with the –kubeconfig argument and point it the config file.
kubectl --kubeconfig fluid-kube-ctl.yml get nodes
This should now give you access to your cluster. All access is proxied via the Fluid Cloud service which handles authentication and access to your clusters.
See Deploy Kube Workloads for a basic example on deploying workloads to your cluster.