Skip to content
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

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

Closed
snowdrop-bot opened this issue Sep 23, 2020 · 0 comments
Assignees
Labels
7 - Community development upstream/closed The issue has been closed in the upstream repository

Comments

@snowdrop-bot
Copy link
Collaborator

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" . }}

quarkusio#12269


$upstream:12269$

@iocanel iocanel closed this as completed Sep 24, 2020
@snowdrop-bot snowdrop-bot reopened this Sep 28, 2020
@snowdrop-bot snowdrop-bot added the upstream/closed The issue has been closed in the upstream repository label Sep 28, 2020
@iocanel iocanel closed this as completed Sep 29, 2020
@snowdrop-bot snowdrop-bot reopened this Sep 29, 2020
@iocanel iocanel closed this as completed Sep 29, 2020
@snowdrop-bot snowdrop-bot reopened this Sep 29, 2020
@iocanel iocanel closed this as completed Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
7 - Community development upstream/closed The issue has been closed in the upstream repository
Projects
None yet
Development

No branches or pull requests

2 participants