Contributors wanted! #3906

We're always happy to see new contributors to kcp!

Learn about kcp

While smaller issues do not require a deep knowledge of kcp knowing the rough terminology, concepts and architecture is a good starting point:

• Terminology
• Architecture
• Tenancy

Local environment

We have few ways to run a local environment. For kcp in most cases it is enough to go run the kcp binary to run a single root shard with no proxy. In other cases you need a sharded setup to test cross-shard feature.

• single shard
• tilt multi-shard with front proxy
• sharded-test-server

The components do not necessarily require a running kcp instance to develop - some have enough options for unit and e2e tests that usually include running kcp in some form.

Also install the krew plugins to easily create and switch workspaces: kcp kubectl plugins

Find something to work on

We label issues that should be a good entrypoint for new contributors as "good first issue", for which you can find search links to the various components below. Of course if you feel brave you can also tackle other issues!

• kcp
• api-syncagent
• multicluster-provider
• kcp-operator
• helm-charts

Getting help

Development topics are discussed mostly in our channel #kcp-dev on the Kubernetes Slack.
If you don't have a Kubernetes Slack account yet get your invite here: https://slack.kubernetes.io/