chore: Deprecate size limits in the KafkaRequest schema #1183
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
The KafkaRequest schema contains the following fields providing information on the instance size limits:
- egress_throughput_per_sec
- ingress_throughput_per_sec
- instance_type_name
- max_connection_attempts_per_sec
- max_data_retention_period
- max_partitions
- total_max_connections
In this PR these fields have been marked for deprecation
Jira: https://issues.redhat.com/browse/MGDSTRM-8967
Checklist (Definition of Done)
Unit and integration tests added that prove the fix is effective or the feature works (tested against emulated and non-emulated OCM environment)Documentation added for the featureRequired metrics/dashboards/alerts have been added (or PR created).Required Standard Operating Procedure (SOP) is added.JIRA has been created for changes required on the client side