Describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.
Please include any manual steps for testing end-to-end or functionality not covered by unit/integration tests.
Also include details of the environment this PR was developed in (language/platform/browser version).
[x] This change adds test coverage for new/changed/fixed functionality
Checklist
[x] I have added documentation for new/changed functionality in this PR and in github.com/otterize/docs
Description
After reconsidering Kubernetes custom resources versioning conventions, we have decided to upgrade
v1alpha3tov1beta1instead ofv1References
https://github.com/otterize/intents-operator/pull/454/
Testing
Describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.
Please include any manual steps for testing end-to-end or functionality not covered by unit/integration tests.
Also include details of the environment this PR was developed in (language/platform/browser version).
Checklist