-
Cuts user’s wait-time down since namespaces will already be ready-to-go.
-
Ensures that namespaces are not forgotten therefore reducing resource utilization.
-
Long-running environments require work to maintain, therefore, having a time limit on them will reduce this issue from happening.
A user will request a namespace which creates a reservation request. From there a namespace is selected from the pool and checked out by that user. The user will have that pool for the specified duration (Or for 1 hour if duration was not specified).
A user can use any of the following optional flags to specify their needs:
-
--name
: Specify a reservation name. Ex.--name my-namespace-reservation
-
-d, --duration
: Specify the length of time a user wants to reserve the namespace for. Ex.-d 3h
-
--pool
: Specify the pool a user wants a namespace from. Ex.--pool minimal
Given the various needs of our users, we incorporated different pools of ready namespaces that contain specific resources.
This is to help ensure that when users request a namespace they aren’t getting any unnecessary resources within their namespace.
The current list of pools are default
, minimal
, and managed-kafka
.
An optional configuration can be added to the pool spec for limiting the number of namespaces that a pool can have at once. This would
include ready
, creating
, and reserved
namespaces. Add the following to utilize this feature: sizeLimit: <int>
-
ClowdEnvironment
: This will create deployments for Kafka, Kafka Connect, Minio, Prometheus, and feature flags. -
FrontendEnvironment
: This sets up environment configurations for the github.com/RedHatInsights/frontend-operator[frontend operator] -
RoleBindings
: Access is granted to devs to edit resources in the namespace -
Secrets are copied from the base namespace.
Made with ❤️ @ Red Hat