Eric Stroczynski
Eric Stroczynski
FWIW running the following seems to create two bundles, assuming you have two different operator configurations in `config/manifests-{foo,bar}`: ```sh export PACKAGE_NAME=$(cat PROJECT | grep projectName | sed 's/projectName: //') for...
/lifecycle frozen
Blocked on https://github.com/operator-framework/operator-lib/issues/48.
@vaibhavjainwiz that step you linked is an intermediate step in converting your packagemanifests to a bundle format. At the end of the conversion process, you should have a bundle.Dockerfile at...
>My other scenerio with this requirement is that I have to make two different bundle for community/product version of my operator. Ah interesting. This is a totally reasonable use case....
Bumping this. Perhaps tarring all 3 binaries by platform so the release artifact count doesn't blow up, ex. ```console $ tar --list -f controller-tools_linux_amd64.tar.gz controller-gen helpgen type-scaffold ```
I'd like to suggest deprecating this package in favor of [`controller-runtime/pkg/leaderelection`](https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/leaderelection), or at least make a note that it has this bug until it is fixed to deter users. client-go's...
This is a somewhat complex feature to implement because `errors.Error` contains a predefined set of error types, to which we would have to add types for each field being validated,...
The SDK's test framework uses some client-go APIs directly and requires the kubeconfig's namespace, so it needs the kubeconfig path. While the framework could/should be refactored to use pure controller-runtime,...
@akoserwal try out SDK's master.