Upgrade your kubeconfig in Oracle Cloud Infrastructure to version 2.0.0

On September 16th, Oracle sent out a notification about a change that needs action before November 15th 2019: you need to upgrade your kubeconfig file from version 1.0.0 to version 2.0.0

Unfortunately, the links in the mail don't describe how to upgrade it, just how to download it....

So here is a short blog that describes what I did on my machine to upgrade my kubecofig file.

Update the config file

1. open a command window
2. type oci -v
3. If the version is 2.6.4 or higher, you are fine. Otherwise type: pip install oci-cli --upgrade Take a look at this page if you encounter issues: Upgrading the CLI
4. type oci ce cluster create-kubeconfig --cluster-id [your cluster ocid] --file $HOME/.kube/config --region [your region] --token-version 2.0.0 

The response should be:

Existing Kubeconfig file found at C:\Users\ldikmans/.kube/config and new config merged into it

Test the new config

Please make sure you test your configuration by starting your proxy and open a browser that points to it:

1. Open a command window
2. Type kubectl proxy
3. Open a browsser window
4. Add the URL: http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login
5. Select your updated kubeconfig file

Fix problems

If you get the error "Not enough data to create auth info structure." ,  follow these steps:

1. open a command prompt
2. type kubectl get secrets -n kube-system
3. type kubectl describe secret -n kube-system kubernetes-dashboard-token-jjtzg (or whatever your dashboard service account user has as a token)
4. copy the resulting token
5. open the browser 
6. Add the URL: http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login
7. Select "Token"
8. Paste the token you copied in step 4 in the field for token

When the dashboard opens properly, store the token in a file so you can copy it in the next time.

Now you are all set!

Happy coding 😀



ps: I would have been nice if this instruction was in the mail Oracle sent. Unfortunately it points to a link that contains the regular installation that does not explain it will merge it automatically. The good news is it was easier than it looked!

ps2: I think you should be able to store the token in the config file as well. However, so far I did not manage to make this work in my environment.

Setting up fn on Kubernetes in the Oracle Cloud (OKE)

In this post I will briefly describe how you can install fn on Kubernetes in the Oracle Cloud (OKE).

Prerequisites

1. You need to have access to Oracle Cloud Infrastructure (OCI) with a unique account. If you have a federated account, you should create another one to be able to create a kubernetes cluster. This account must have either Administrator privileges or belong to a group to which a policy grants the appropriate Container Engine for Kubernetes permissions. Since my example is for R&D purposes, I will be using an account with Administrator privileges.
2. Install and configure the OCI CLI, generate an API signing key pair and add that public key to your username. 
3. Create a separate compartment for the cluster and make sure your compartment has the necessary resources and your root compartments needs the policy Allow service OKE to manage all-resources in tenancy 
4. Install and setup kubectl on Windowns (tip: use Chocolatey)
5. Install helm

Create the Kubernetes cluster

1. Navigate to your console
2. Under Developer Services, select "clusters"
3. Pick the compartment that you created or want to use
4. Click on "Create Cluster" and accept all the defaults
5. Click "Create"
6. Inspect the details 
7. Download the kubeconfig file and store it in your .kube directory

If it fails because of service limits, raise an SR with Oracle support to get your limits increased.

Install fn 

1. Make sure your server version of helm is up to date (helm init --upgrade)
2. Create a directory fnhelm
3. Clone the git repo: git clone https://github.com/fnproject/fn-helm.git
4. Install the chart dependencies: helm dep build fn
5. Install it in your cluster: helm install --name my-release fn

Deploy your function to the cluster

1. Make sure you are logged in to your dockerhub account
2. Set the fn context to the right value
3. Deploy the function to the cluster

The fn context

When you use fn deploy, it uses a context to determine where to deploy to, and what registry to use. The URL for the fnserver you deployed to the kubernetes cluster  can be found by issuing the following command

• $(kubectl get svc --namespace default my-release-fn-api -o jsonpath='{.status.loadBalancer.ingress[0].ip}'):80

However, you can also look it up using a kubectl proxy: 

• kubectl proxy 
• Navigate to a browser: https://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#
• Select "Services" in the navigation menu at the left

• Click on the External Endpoint of the my-release-fn-api 
• You should see the following:

Now we can create the context by running the following commands:

• fn list contexts
• fn create context ociLonneke --api-url [your url] --provider default --registry [your_dockerhub_username]
• fn list contexts

Deploy the function to the cluster

Finally! We are ready to deploy our first function to our cluster. In this case I use the Java tutorial example. 

• fn init --runtime java --trigger http javafn
• fn build
• fn deploy --app java-app

This will result in the following output (or something similar)

Successfully created app:  java-app

Successfully created function: javafn with lonneke/javafn:0.0.2

Successfully created trigger: javafn-trigger

Trigger Endpoint: http://xxx.xx.xx.xx:80/t/java-app/javafn-trigger

Test the function

Open a browser and type the url as stated by the trigger endpoint. You should see the following result:

Next steps

Now you have your kubernetes cluster up and running, you can move your functions from your local installation to the cluster and start using them in production!

Happy coding 😊