Skip to content

Latest commit

 

History

History
230 lines (168 loc) · 8.01 KB

DEVELOPMENT.md

File metadata and controls

230 lines (168 loc) · 8.01 KB
Raw

Development

This doc explains how to setup a development environment so you can get started contributing to Knative Serving. Also take a look at:

Getting started

  1. Create a GitHub account
  2. Setup GitHub access via SSH
  3. Install requirements
  4. Set up a kubernetes cluster
  5. Set up a docker repository you can push to
  6. Set up your shell environment
  7. Create and checkout a repo fork

Once you meet these requirements, you can start Knative Serving!

Before submitting a PR, see also CONTRIBUTING.md.

Requirements

You must install these tools:

  1. go: The language Knative Serving is built in
  2. git: For source control
  3. dep: For managing external Go dependencies.
  4. ko: For development.
  5. kubectl: For managing development environments.

Environment setup

To start your environment you'll need to set these environment variables (we recommend adding them to your .bashrc):

  1. GOPATH: If you don't have one, simply pick a directory and add export GOPATH=...
  2. $GOPATH/bin on PATH: This is so that tooling installed via go get will work properly.
  3. KO_DOCKER_REPO and DOCKER_REPO_OVERRIDE: The docker repository to which developer images should be pushed (e.g. gcr.io/[gcloud-project]).
  4. K8S_CLUSTER_OVERRIDE: The Kubernetes cluster on which development environments should be managed.
  5. K8S_USER_OVERRIDE: The Kubernetes user that you use to manage your cluster. This depends on your cluster setup, please take a look at cluster setup instruction.

.bashrc example:

export GOPATH="$HOME/go"
export PATH="${PATH}:${GOPATH}/bin"
export KO_DOCKER_REPO='gcr.io/my-gcloud-project-name'
export DOCKER_REPO_OVERRIDE="${KO_DOCKER_REPO}"
export K8S_CLUSTER_OVERRIDE='my-k8s-cluster-name'
export K8S_USER_OVERRIDE='my-k8s-user'

Make sure to configure authentication for your KO_DOCKER_REPO if required. To be able to push images to gcr.io/<project>, you need to run this once:

gcloud auth configure-docker

For K8S_CLUSTER_OVERRIDE, we expect that this name matches a cluster with authentication configured with kubectl. You can list the clusters you currently have configured via: kubectl config get-contexts. For the cluster you want to target, the value in the CLUSTER column should be put in this variable.

Checkout your fork

The Go tools require that you clone the repository to the src/github.com/knative/serving directory in your GOPATH.

To check out this repository:

  1. Create your own fork of this repo
  2. Clone it to your machine:
mkdir -p ${GOPATH}/src/github.com/knative
cd ${GOPATH}/src/github.com/knative
git clone [email protected]:${YOUR_GITHUB_USERNAME}/serving.git
cd serving
git remote add upstream [email protected]:knative/serving.git
git remote set-url --push upstream no_push

Adding the upstream remote sets you up nicely for regularly syncing your fork.

Once you reach this point you are ready to do a full build and deploy as described below.

Starting Knative Serving

Once you've setup your development environment, stand up Knative Serving:

  1. Setup cluster admin
  2. Deploy istio
  3. Deploy build
  4. Deploy Knative Serving
  5. Enable log and metric collection

Setup cluster admin

Your $K8S_USER_OVERRIDE must be a cluster admin to perform the setup needed for Knative:

kubectl create clusterrolebinding cluster-admin-binding \
  --clusterrole=cluster-admin \
  --user="${K8S_USER_OVERRIDE}"

Deploy Istio

kubectl apply -f ./third_party/istio-1.0.2/istio.yaml

Follow the instructions if you need to set up static IP for Ingresses in the cluster.

Deploy Build

kubectl apply -f ./third_party/config/build/release.yaml

Deploy Knative Serving

This step includes building Knative Serving, creating and pushing developer images and deploying them to your Kubernetes cluster.

First, edit config-network.yaml as instructed within the file. If this file is edited and deployed after Knative Serving installation, the changes in it will be effective only for newly created revisions.

Next, run:

ko apply -f config/

You can see things running with:

kubectl -n knative-serving get pods
NAME                                READY     STATUS    RESTARTS   AGE
controller-77897cc687-vp27q   1/1       Running   0          16s
webhook-5cb5cfc667-k7mcg      1/1       Running   0          16s

You can access the Knative Serving Controller's logs with:

kubectl -n knative-serving logs $(kubectl -n knative-serving get pods -l app=controller -o name)

If you're using a GCP project to host your Kubernetes cluster, it's good to check the Discovery & load balancing page to ensure that all services are up and running (and not blocked by a quota issue, for example).

Install logging and monitoring backends

Run:

kubectl apply -R -f config/monitoring/100-common \
    -f config/monitoring/150-elasticsearch \
    -f third_party/config/monitoring/common \
    -f third_party/config/monitoring/elasticsearch \
    -f config/monitoring/200-common \
    -f config/monitoring/200-common/100-istio.yaml

Iterating

As you make changes to the code-base, there are two special cases to be aware of:

These are both idempotent, and we expect that running these at HEAD to have no diffs. Code generation is automatically checked to produce no diffs for each pull request. Dependencies are not yet automatically checked (see issue 1711).

update-deps.sh runs "dep ensure" command. In some cases, if newer dependencies are required, you need to run "dep ensure -update package-name" manually.

Once the codegen and dependency information is correct, redeploying the controller is simply:

ko apply -f config/controller.yaml

Or you can clean it up completely and completely redeploy Knative Serving.

Clean up

You can delete all of the service components with:

ko delete --ignore-not-found=true \
  -f config/monitoring/100-common \
  -f config/ \
  -f ./third_party/config/build/release.yaml \
  -f ./third_party/istio-1.0.2/istio.yaml

Telemetry

See telemetry documentation.