linkerd
/
linkerd2
mirror of https://github.com/linkerd/linkerd2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: Update instructions for running the tap controller locally (#7788) 

The instructions for running the tap controller are no longer valid.
This change updates BUILD.md with the proper instructions.

Signed-off-by: Alejandro Pedraza <alejandro@buoyant.io>
Co-authored-by: Alejandro Pedraza <alejandro@buoyant.io>
This commit is contained in:
Oliver Gould 2022-02-07 15:08:10 -08:00 committed by GitHub
parent a24aa51639
commit d0497f6bd5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
BUILD.md
View File

@ -311,14 +311,13 @@ You can send test requests to the destination service using the
bin/go-run controller/script/destination-client -path hello.default.svc.cluster.local:80
```
##### Running the Tap APIService for development
##### Debugging the Tap APIService for development
```bash
openssl req -nodes -x509 -newkey rsa:4096 -keyout $HOME/key.pem -out $HOME/crt.pem -subj "/C=US"
bin/go-run controller/cmd tap --disable-common-names --tls-cert=$HOME/crt.pem --tls-key=$HOME/key.pem
curl -k https://localhost:8089/apis/tap.linkerd.io/v1alpha1
```
The Tap APIService is a Kubernetes extension API server, so it can be
challenging to run outside the cluster. The most straightforward workflow is to
simply test changes by building and loading the container image as explained in
the [comprehensive configuration](#comprehensive) section above (in order to
just build this component use `bin/docker-build-tap`).
#### Generating CLI docs