Skip to content

Latest commit

 

History

History
114 lines (77 loc) · 3.31 KB

DEVELOPMENT.md

File metadata and controls

114 lines (77 loc) · 3.31 KB
Raw

Development

Commits

PRs

Because github doesn't have great support for merging PRs from the webui, PRs must be merged from the command line:

git rebase -ff branch-name && git push origin branch-name

CI

On PR, CI produces a darwin-arm64 binary and helm chart. Click on any step from the PR and then Summary on the left sidebar to see the uploaded artifacts. Docker images are built to verify that the linux-amd64 binary can be built but they are not pushed or uploaded anywhere.

Environment

Copy .envrc.example to .envrc. The GHCR_TOKEN is a personal access token with permissions to write:packages. This is only required if you want to upload directly to github.

Cluster

We recommend using k3d to run a local cluster. To setup:

k3d cluster create kty --registry-create kty:5432

Next, you'll want to add the registry to your /etc/hosts:

echo "127.0.0.1 kty" | sudo tee -a /etc/hosts

When you run just dev-push, an image at kty:5432/kty:latest will be available to run inside the cluster.

Logging

The global debug level can be overly noisy. Instead of doing -vvvv, try:

RUST_LOG=none,kty=debug

If you'd like to see backtraces on panic, set RUST_BACKTRACE.

Tracing Tree

It can be a little difficult to reason about how events filter through the application. Towards that end, dispatch has tracing::instrument on it in most places. This can be used to render a tree based on the spans that lets you see what functions are being called and what their return values are. To see this data, you can use the same format as RUST_LOG and export:

TRACING_TREE=none,kty=trace

Ingress Tunnel

If testing port forwarding and running the service locally (aka not on the cluster), you won't have access to any of the DNS or IP addresses that might be forwarded. To work around this, modify /etc/hosts:

127.0.0.1 localhost.default.svc

Then you'll be able to test forwarding to localhost via:

ssh -L 9090:svc/default/localhost:9091 me@localhost -p 2222

Testing pods and nodes requires running on the cluster as the response from addr for those is IP addresses.

Egress Tunnel

If you're not running on the cluster, you'll want to:

  • Make sure you're running from the same network (doable with some games with VPNs and local clusters).
  • Set HOSTNAME to a pod in the cluster that is in your default namespace.
  • Set POD_UID to the metadata.uid of the pod from HOSTNAME.
  • Set POD_IP to the IP address of your host. You can get this by going into a pod and doing a nslookup host.docker.internal.

Kubernetes Resources

When updating resources, make sure to update them in both places: