WHAT

Capacity limits are reported back in our public API endpoints but they are currently not returned in any of the private admin API endpoints.

Report capacity limits in the getKafkas, getKafkaById and updateKafkaById endpoints in the private admin API.

WHY

The private admin API endpoints allow admin users to list, view, update and delete Kafka instances regardless who created them. They are mainly used by RTS/CS-SRE for debugging purposes.

We should report the capacity limits in the private admin API endpoints as they can be useful information.

HOW

1. Update the Kafka schema in the kas-fleet-manager-private-admin.yaml to include the following fields:

• ingress_throughput_per_sec
• egress_throughput_per_sec
• total_max_connections
• max_partitions
• max_data_retention_period
• max_connection_attempts_per_sec
• quota_consumed
• quota_type
• capacity_consumed

2. Run make openapi/generate
3. Update the PresentKafkaRequestAdminEndpoint presenter to include the fields mentioned above. This may need to be refactored so that the function accepts config.KafkaConfig, which contains the values for the new fields.

DONE

• Capacity limits are reported in the getKafkas, getKafkaById and updateKafkaById endpoints of the private admin API.
• Unit/Integration tests updated if required.

Guidelines

The following steps should be adhered to:

• Required tests should be put in place - unit, integration, manual test cases (if necessary)
• CI and all relevant tests passing
• Changes have been verified by one additional reviewer against:
• each required environment
• each supported upgrade path
• If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged