Recently, I have been playing a lot with Functions and Project Fn. Eventually, I got to the point where I had to go beyond a playground on my laptop and go to the real wild world. An idea of running Fn on a K8s cluster seemed very attractive to me and I decided to do that somewhere on prem or in the cloud. After doing some research on how to install and configure K8s cluster on your own on a bare metal I came to a conclusion that I was too lazy for that. So, I went (flew) to the cloud.
In this post I am going to show how to run Fn on Kubernetes cluster hosted on the Google Cloud Platform. Why Google? There are plenty of other cloud providers with the K8s services.
The thing is that Google really has Kubernetes cluster in the cloud which is available for everyone. They give you the service right away without asking to apply for a preview mode access (aka we’ll reach out to you once we find you good enough for that), explaining why you need it, checking your background, credit history, etc. So, Google.
Once you got through all formalities and finally have access to the Google Kubernetes Engine, go to the Quickstarts page and follow the instructions to install Google Cloud SDK.
If you don’t have kubectl installed on your machine you can install it with gcloud:
gcloud components install kubectl
Follow the instructions on Kubernetes Engine Quickstart to configure gcloud and create a K8s cluster by invoking the following commands:
gcloud container clusters create fncluster gcloud container clusters get-credentials fncluster
Check the result with kubectl:
kubectl cluster-info
This will give you a list of K8s services in your cluster and their URLs.
Ok, so this is our starting point. We have a new K8s cluster in the cloud on one hand and Fn project on another hand. Let’s get them married.
We need to install a tool managing Kubernetes packages (charts). Something similar to apt/yum/dnf/pkg on Linux. The tool is Helm. Since I am a happy Mac user I just did that:
brew install kubernetes-helm
The rest of Helm installation options are available here.
The next step is to install Tiller in the K8s cluster. This is a server part of Helm:
kubectl create serviceaccount --namespace kube-system tiller kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller helm init --service-account tiller --upgrade
helm repo update
If you don’t have Fn installed locally, you will want to install it so you have Fn CLI on your machine (on Mac or Linux):
curl -LSs https: //raw .githubusercontent.com /fnproject/cli/master/install > setup.sh chmod u+x setup.sh sudo ./setup.sh
Install Fn on K8s cluster with Helm (assuming you do have git client):
git clone git@github.com:fnproject/fn-helm.git && cd fn-helm helm dep build fn
helm install --name fn-release fn
Wait (a couple of minutes) until Google Kubernetes Engine assigns an external IP to the Fn API in the cluster. Check it with:
kubectl get svc --namespace default -w fn-release-fn-api
Configure your local Fn client with access to Fn running on K8s cluster
export FN_API_URL=http://$(kubectl get svc --namespace default fn-release-fn-api -o jsonpath='{.status.loadBalancer.ingress[0].ip}'):80Basically, it’s done. Let’s check it:
fn apps create adfbuilderapp fn apps list
Now we can build ADF applications with an Fn function as it is described in my previous post. Only this time the function will run and therefore building job will be performed somewhere high in the cloud.
That’s it!
| Published on Java Code Geeks with permission by Eugene Fedorenko , partner at our JCG program. See the original article here: Run Fn Functions on K8s on Google Cloud Platform Opinions expressed by Java Code Geeks contributors are their own. |
