You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Making TLS material available would be easy though, the harder part will be to have webhooks actually working and hitting a process external to the cluster, probably that would require something like mirrord or some other networking trick. The easiest thing would be not to setup and configure webhooks in this mode probably.
FWIW I haven't personally used make run in many years. Do folks find it valuable?
Since we added E2E tests I almost never spin up a "dev environment" locally for Crossplane. I just write and/or run the E2E tests, which essentially do the same thing but in a repeatable fashion.
I can see the value in building an e2e scenario for an intended change.
But I can personally find the value, and I can imagine others would as well, to have a very low barrier to entry means of iterating on my local crossplane code. For folks less familiar with the code base, and with the patterns/expectations of the e2e tests, being able to rapidly iterate over just their code changes pointed at a local cluster is an easier experience to get going.
FWIW, I still use ./cluster/local/kind.sh often too, and make run is a faster/easier version of that 😉
Since we added E2E tests I almost never spin up a "dev environment" locally for Crossplane. I just write and/or run the E2E tests, which essentially do the same thing but in a repeatable fashion.
That is a perfect, ideal test-driven workflow, and I admire it. But it also assumes excellent familiarity with the codebase.
The ability to quickly set up the local environment and understand the code behavior is crucial for those of us who don't work with the Crossplane core codebase daily. This enables early testing and lowers the barrier to start with the contribution flow.
What happened?
When new contributors attempt to follow the guidance to set up their developer environment, they will encounter an error when running
make run
:@haarchri has a workaround script he uses. Should we document this, or should the process itself be made more easy?
https://gist.github.com/haarchri/6526d1738611cc79c04e88091dfe074a
How can we reproduce it?
Essentially the steps from https://github.com/crossplane/crossplane/tree/master/contributing#establishing-a-development-environment:
What environment did it happen in?
Crossplane version: v1.15.2
Kubernetes client: v1.26.2
Kubernetes server: v1.29.1
OS: macoS Sonoma v14.4.1
The text was updated successfully, but these errors were encountered: