Add knative crds + move knative CRs to plugin-infra #1219
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently, the Knative CRs (managed by Serverless Operator) are created as part of the plugin-deps. However, this should be part of the plugin-infra because there will be risks of failure when changes are made to the these CRs (by the admin) and the RHDH operator attempts reapplication/reconciliation/reversion since the plugin-deps are handled by the operator.
Which issue(s) does this PR fix or relate to
PR acceptance criteria
Knative CRs should be applied during the plugin infrastructure set up instead of afterwards.
Tests
Documentation
How to test changes / Special notes to the reviewer
Pull the changes, run
make plugin-infra deploy IMG={IMG}
This should apply the knative CRs and create the resources after the serverless operator is ready.