r-cube/k8s-custom-configmap

A custom config map which adds a safety net to your ad-hoc changes

k8s-custom-configmap's Issues

Cleanup unused custom-config map resource

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Switch to josdk's managed dependent resources

Description

josdk offers a way to wire in managed dependencies. This would make the code look more concise and declarative.

Due to the limitation we have as mentioned in this ticket, It is required to construct our ownDependentResourceFactory that is aware of Spring context.

Support base64 opaque secret key reference in the custom resource

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Introduce capability to externalize JSON data validation

Is your feature request related to a problem? Please describe.

Currently, the custom resource expects the JSON schema to be present along with the data, and this JSON schema is used by the operator to validate the data. While this approach functions as intended, there are a few limitations:

• If the data is too large, the corresponding JSON schema will likely increase in size, consequently expanding the size of the custom resource.
• There are scenarios where more robust validations on the data might be necessary, which may not be adequately covered by the JSON schema.

Describe the solution you'd like

The proposl is to allow users to externalize data validations to a service (or lambda) and exposing it via a REST API, which can then be utilized by the config-operator for data validation before creating the config-map. This approach has several advantages over embedding the JSON schema directly in the custom resource:

• Reduced Custom Resource Size
• Dynamic and Extensible Validations