Right now, some of our operators are loaded from forks of GPTE's GitHub accounts, including an individual contributor and their main project. The Operators are assembled at build time, not maintained as a cohesive unit, and not updated incredibly frequently.
I want to take ownership of the following operators:
[x] Separate the logic required to deploy the operators from the codebase directly
[x] Implement Molecule tests for the newly forked operators in Travis
[x] Implement CD to push updated images to Quay, including cron rebuilds
[x] Determine the best way to make the workshop deliver these new operators without hard-coded Kubernetes resources
(Expect this to be that the operator-sdk is built into the run-container.sh Containerfile and the auto-generated Makefile can be used)
[x] Implement a plan to begin adding more features to those operators, especially in support of #65
[ ] Merge all important changes simultaneously after testing (operator changes move to their respective develop/master branch, new implementation logic moves into this repo's master)
[x] FIPS testing
[x] Disconnected support (including operator-sdk sidecars...)
jharmison-redhat
commented
4 years ago
Right now, some of our operators are loaded from forks of GPTE's GitHub accounts, including an individual contributor and their main project. The Operators are assembled at build time, not maintained as a cohesive unit, and not updated incredibly frequently.
I want to take ownership of the following operators:
This means the following for each of them: