Joel Speed
Joel Speed
Oh sorry yes, I got confused and inverted the problem in my head! Ok, this is a much harder problem to solve. If we want the schema to be correct,...
We could potentially add a namespace limitation to the controller or have it check for the presence of a label on the namespace before reconciling it like Kubernetes does for...
> can regenerate it if it will help you This would be helpful if you have a moment
Ok, so we will need to add `--namespace` flag that handles restricting Wave to a namespace, this should be reasonably easy to do as we only need to pass the...
> We should have a clear way on how to structure webhooks in our API packages across Cluster API and its ecosystem of providers Agreed, I don't have context on...
I did a bit of work on the code for this today and came across a small issue. Currently the package `internal/test/builder` imports the defaulting functions from `clusterv1`, if we...
> Remove the defaulting bit from the builder (it's for MHC and MD) and handle the defaulting in the tests where those are needed (there are 9 instances for MHC,...
I've just posted two PRs to show the progress I've made so far on the main Cluster v1beta1 APIs, the first of which for scheme builder should be ready for...
Both PRs are now ready for review and, combined, clear the deps for the main APIs (Machine, MS, MD, Cluster etc). Will start to look at the exp APIs next
Have added a TODO list with my initial thoughts on scope here, any additional points we need for this issue?