Change Details

Toolforge kubernetes impose a pattern on Toolforge tool names. There are currently a few that doesn't check the pattern, and are therefore weird tools with either invalid k8s credentials, missing namespaces, or half configured in some other ways. This already caused some problems, see for example: * {T338124} Some examples, underscore is not allowed: * `ru_monuments` https://toolsadmin.wikimedia.org/tools/id/ru_monuments * `wdq_checker` https://toolsadmin.wikimedia.org/tools/id/wdq_checker The latest version of maintain-kubeusers already ignores tools with such invalid names that would otherwise clash with k8s validations.

Toolforge kubernetes impose a pattern on Toolforge tool names. There are currently a few that doesn't check the pattern, and are therefore weird tools with either invalid k8s credentials, missing namespaces, or half configured in some other ways. This already caused some problems, see for example: * {T338124} * {T301720} * {T301015} * {T176027} Some examples, underscore is not allowed: * `ru_monuments` https://toolsadmin.wikimedia.org/tools/id/ru_monuments * `wdq_checker` https://toolsadmin.wikimedia.org/tools/id/wdq_checker The latest version of maintain-kubeusers already ignores tools with such invalid names that would otherwise clash with k8s validations.

Toolforge kubernetes impose a pattern on Toolforge tool names. There are currently a few that doesn't check the pattern, and are therefore weird tools with either invalid k8s credentials, missing namespaces, or half configured in some other ways. This already caused some problems, see for example: * {T338124} * {T301720} * {T301015} * {T176027} Some examples, underscore is not allowed: * `ru_monuments` https://toolsadmin.wikimedia.org/tools/id/ru_monuments * `wdq_checker` https://toolsadmin.wikimedia.org/tools/id/wdq_checker The latest version of maintain-kubeusers already ignores tools with such invalid names that would otherwise clash with k8s validations.