You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we have the capability to define labels at the environment level, which are automatically propagated. However, this functionality is not mandatory for environment creation. Unlike application creation, where label specification is enforced, there is no policy enforcement to ensure labels are consistently applied at the environment level during its creation.
🎤 Pitch / Usecases
We propose the introduction of a policy mechanism, similar to Pod Security Levels, at the namespace level. This policy would ensure that no new pods are created with elevated access or security privileges beyond the defined thresholds. While Devtron currently supports the use of labels at the namespace level, there is no provision to make these labels mandatory during environment creation. Enforcing such a policy would enhance security and standardization across environments.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🔖 Feature description
Currently, we have the capability to define labels at the environment level, which are automatically propagated. However, this functionality is not mandatory for environment creation. Unlike application creation, where label specification is enforced, there is no policy enforcement to ensure labels are consistently applied at the environment level during its creation.🎤 Pitch / Usecases
We propose the introduction of a policy mechanism, similar to Pod Security Levels, at the namespace level. This policy would ensure that no new pods are created with elevated access or security privileges beyond the defined thresholds. While Devtron currently supports the use of labels at the namespace level, there is no provision to make these labels mandatory during environment creation. Enforcing such a policy would enhance security and standardization across environments.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: