Ken Sipe
Ken Sipe
Kudo details on contributing a patch modeled after Example: https://github.com/helm/helm/blob/master/CONTRIBUTING.md#how-to-contribute-a-patch
**What would you like to be added**: Spark operator is adding crds... which in the logs is impossible to discern. **Why is this needed**:
**What would you like to be added**: Between framework -> operator and bundle -> packages refactoring we have structures which are challenging for anyone new to the project to reasonable...
**What would you like to be added**: Based on review of https://github.com/kudobuilder/kudo/pull/506 it was suggested that we: 1. Create a Validator interface with a Validate function 2. Add Validate functions...
This provides the ability for 1 repo index to include another (or multiple). This changes in code is backward compatible... if the new field "include:" is missing, it works fine....
It would be great if we could restrict params being set at install / update / upgrade to a set of predefined values... lets say a param defines a protocol...
### Expected Behavior the cmd line docs for `tilt up --hud` seem to indicate it is default true... which should be the default `tilt up`. however it looks identical to...
Signed-off-by: Ken Sipe
Signed-off-by: Ken Sipe
This should be simple. trigger off version tag and release. MVP is release of kuttl.. but would love to automate: 1. kuttl release 2. docker release 3. krew update (this...