Skip to content
`kf` provides `cf` users a familiar workflow experience on top of Knative.
Branch: master
Clone or download
josephlewis42 and mattysweeps added service account to source (#328)
This adds the ability to specify a service account on a Source. We use the field name ServiceAccount to match Tekton rather than ServiceAccountName which matches Knative Build.

This will ensure we don't break the instructions Evan is putting together that rely on setting a service account.

Longer term, we should put a default service account on the space to be used for all builds to prevent privilege escalation by devs.
Latest commit 58aef85 Jul 17, 2019

README.md

Kf

knative.slack.com

kf provides a cf-like experience on top of Knative.

kf aims to be fully compatible with CF applications and lifecycle. It supports logs, buildpacks, app manifests, routing, service brokers, and injected services.

At the same time, it aims to improve the operational experience by supporting git-ops, self-healing infrastructure, containers, a service mesh, autoscaling, scale-to-zero, improved quota management and does it all on Kubernetes using industry-standard OSS tools including Knative, Istio, and Tekton.

Getting started

Follow the install instructions to create a GKE cluster, install Kf into it, and deploy an app with the kf CLI.

How to build

Requirements:

  • Golang 1.12 (go mod is used and required for dependencies)

Building:

$ ./hack/build.sh

Notes:

  • The kf CLI must be built outside of the $GOPATH folder unless you explicitly use export GO111MODULE=on.

Development and releasing

We use ko for rapid development and during the release process to build a full set of kf images and installation YAML.

To update your cluster while developing run ko apply:

KO_DOCKER_REPO=gcr.io/my-repo ko apply -f config

This will build any images required by config/, upload them to the provided registry, and apply the resulting configuration to the current cluster.

You can’t perform that action at this time.