generated Kubernetes resources : roleBinding.yaml: object name does not conform to Kubernetes naming requirements

[survivant]

I separated kubernetes.yaml into different files in Helm chart format

my app name is : kubernetes-api

The problem is with the name: "kubernetes-api:view"

The naming convention is : https://kubernetes.io/docs/concepts/overview/working-with-objects/names/
contain at most 63 characters
contain only lowercase alphanumeric characters or '-'
start with an alphanumeric character
end with an alphanumeric character

when I try to validate the yaml, I got a error

helm lint (or I used Intellij to validate the yaml file)

Error: 1 chart(s) linted, 1 chart(s) failed
==> Linting chart
[ERROR] templates/roleBinding.yaml: object name does not conform to Kubernetes naming requirements: "kubernetes-api:view"

apiVersion: "rbac.authorization.k8s.io/v1"
kind: "RoleBinding"
metadata:
labels:
{{ include "app.labels" . | indent 4 }}
name: "kubernetes-api:view"
roleRef:
kind: "ClusterRole"
apiGroup: "rbac.authorization.k8s.io"
name: "view"
subjects:

• kind: "ServiceAccount"
  name: {{ include "app.name" . }}

[quarkusbot]

/cc @geoand

[geoand]

@iocanel this seems to come down to how io.dekorate.kubernetes.decorator.AddRoleBindingResourceDecorator generates the name:

String name = Strings.isNotNullOrEmpty(this.name) ? this.name : meta.getName() + ":" + this.role;

Should we change that?

[survivant]

instead of ":" . change it to "-" and it will works

[geoand]

👍

https://kubernetes.io/docs/concepts/overview/working-with-objects/names/ gives all the rules

[iocanel]

Fixing it upstream, will release later today.

[geoand]

Great, thanks!

[geoand]

Fixed by #12278