Chapter 9. Building and deploying functions on the cluster

Procedure

1. Create a function by running the following command:

   $ kn func create <function_name> -l <runtime>

2. Implement the business logic of your function. Then, use Git to commit and push the changes.

3. Deploy your function by running the following command:

   $ kn func deploy --remote

   If you are not logged into the container registry referenced in your function configuration, you are prompted to give credentials for the remote container registry that hosts the function image:

   You get an output similar to the following example:

   🕕 Creating Pipeline resources
   Please provide credentials for image registry used by Pipeline.
   ? Server: https://index.docker.io/v1/
   ? Username: my-repo
   ? Password: ********
      Function deployed at URL: http://test-function.default.svc.cluster.local

4. To update your function, commit and push new changes by using Git, then run the kn func deploy --remote command again.

5. Optional. You can configure your function to be built on the cluster after every Git push by using pipelines-as-code:

   1. Generate the Tekton Pipelines and PipelineRuns configuration for your function by running the following command:

      $ kn func config git set

      Apart from generating configuration files, this command connects to the cluster and verifies the pipeline installation. By using the token, it also creates a webhook on the function repository on behalf of the user. That webhook triggers the pipeline on the cluster every time you push changes to the repository.

      You need to have a valid GitHub personal access token with the repository access to use this command.

   2. Commit and push the generated .tekton/pipeline.yaml and .tekton/pipeline-run.yaml files by running the following commands:

      $ git add .tekton/pipeline.yaml .tekton/pipeline-run.yaml
      $ git commit -m 'Add the Pipelines and PipelineRuns configuration'
      $ git push

   3. After you make a change to your function, commit and push it. The function is rebuilt automatically by using the created pipeline.

Procedure

1. Navigate to Topology.
2. Click a function, then click Test Serverless Function from the Actions drop-down list in the Details panel. This opens the Test Serverless Function dialog box.

3. In the Test Serverless Function dialog box, change the settings for your test as required:

   1. Choose the Format for your test. This can be either CloudEvent or HTTP.
   2. The Content-Type defaults to the Content-Type HTTP header value.
   3. You can use the Advanced Settings to change the Type or Source for CloudEvent tests, or to add optional headers.
   4. You can change the input data for the test.
4. Click Test to run your test.
5. After the test is complete, the Test Serverless Function dialog box displays a status code and a message that informs you whether your test was succesful.
6. Click Back to perform another test, or Close to close the testing dialog box.