Block a user
monitoringalerting
No need for this monitoring_stack: Stack field for now. This is a case of YAGNI. We support only one type and I don't see in the very short term a use case that would force us.
feat: add ingress score
What about path, path_type and namespace? These certainly don't support any String?
861f266c4e
Merge pull request 'feat: LAMP stack and Monitoring stack now work on OKD, we just have to manually set a few serviceaccounts to privileged scc until we find a better solution' (#36) from feat/lampOKD into master
51724d0e55
feat: LAMP stack and Monitoring stack now work on OKD, we just have to manually set a few serviceaccounts to privileged scc until we find a better solution
feat: LAMP stack and Monitoring stack now work on OKD, we just have to manually set a few serviceaccounts to privileged scc until we find a better solution
51724d0e55
feat: LAMP stack and Monitoring stack now work on OKD, we just have to manually set a few serviceaccounts to privileged scc until we find a better solution
ad72409287
feat: LAMP stack and Monitoring stack now work on OKD, we just have to manually set a few serviceaccounts to privileged scc until we find a better solution
c2d1cb9b76
Merge pull request 'upgrade stack size from default 1MB on windows (k3d stack overflow otherwise)' (#34) from windows-stack-size-increase into master
feat: LAMP stack and Monitoring stack now work on OKD, we just have to manually set a few serviceaccounts to privileged scc until we find a better solution
johnride
deleted branch upload_folder_improvements from NationTech/harmony
2025-05-14 15:35:04 +00:00
feat: add ingress score
There should maybe be an option in LampConfig to enable/disable ingress creation
feat: add ingress score
Only thing that must be improved at the moment is to use correct type safe types in the Score definition.
feat: add ingress score
I think it's now worth the time to use correct types for each k8s field types.