-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customizable Default Configuration for Storage Class in User Clusters #13258
Comments
This issue needs clarification: Is it end users (people creating clusters) or platform admins (changing the defaults of what is deployed) that should be able to change this? The first section says As a KKP admin, but the solution details say As a user. End users should just deploy their own |
If I may chime in as a platform admin: we simply build a custom addons image with our own storage classes included and we then overwrite the addons that are installed through the KubermaticConfiguration, i.e. we removed the I obviously wouldn't be opposed to having an easier solution that doesn't involve building our own addons image and overwriting the addons list. But imho only being able to configure the parameters Csenger mentioned wouldn't be helpful. We'd need to overwrite the default storage classes, probably through the KubermaticConfiguration, completely. For example we also set |
@embik my 5 cents: I'm with @judge-red. It would be great to have an easier solution than building a custom addon. |
Is this something that could be solved by using the Applications feature in KKP? |
Hi @xrstf, IIRC, the application feature needs to be enabled separately for each user cluster. |
@xrstf I think if it was possible to mandate certain applications, like we can with addons, that could work. But I don't think that's currently possible, is it? That said, we also don't wan't the default StorageClasses defined in the KKP addon, as they're non-functional for us. So we'd still need to overwrite the |
You're right, but overriding the defaultManifests should at least be a bit simpler than maintaining your own set of addons. Apps would make that maintenance a bit easier was my thinking. |
Simpler yes. But just recently we ran into the issue that addons were removed from KKP and we missed that we should remove them from the |
/label sig/cluster-management |
Description of the feature you would like to add / User story
As a KKP admin
I want the ability to update default configurations within user clusters, particularly for storage classes
In order to customize their behavior according to our requirements.
Solution details
allowVolumeExpansion
should be configurable and set totrue
.reclaimPolicy
should be configurable and set toRetain
.Alternative approaches
Use cases
Additional information
allowVolumeExpansion
is deactivated and reclaimPolicy is set todelete
The text was updated successfully, but these errors were encountered: