-
Notifications
You must be signed in to change notification settings - Fork 170
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
helm "podAnnotations" cannot applied #477
Comments
I am also experiencing this issue. It seems that even the sample yaml file (customAnnotationsAndLabels.yaml) cannot be used with the values schema. % helm template -f test.yaml grafana/k6-operator
coalesce.go:220: warning: cannot overwrite table with non table for k6-operator.manager.env (map[])
Error: values don't meet the specifications of the schema(s) in the following chart(s):
k6-operator:
- (root): Additional property certManager is not allowed
- customLabels: Additional property customized-labels is not allowed
- manager.readinessProbe: Additional property successThreshold is not allowed
- manager.readinessProbe: Additional property timeoutSeconds is not allowed
- manager.readinessProbe: Additional property failureThreshold is not allowed
- manager.readinessProbe: Additional property httpGet is not allowed
- manager.readinessProbe: Additional property initialDelaySeconds is not allowed
- manager.readinessProbe: Additional property periodSeconds is not allowed
- manager.env: Invalid type. Expected: object, given: array
- manager.image: Additional property name is not allowed
- manager.livenessProbe: Additional property failureThreshold is not allowed
- manager.livenessProbe: Additional property httpGet is not allowed
- manager.livenessProbe: Additional property initialDelaySeconds is not allowed
- manager.livenessProbe: Additional property periodSeconds is not allowed
- manager.livenessProbe: Additional property successThreshold is not allowed
- manager.livenessProbe: Additional property timeoutSeconds is not allowed
- podLabels: Additional property environment is not allowed
- podLabels: Additional property owner is not allowed
- podAnnotations: Additional property customized-annotation is not allowed
- affinity: Additional property nodeAffinity is not allowed
- authProxy.resources: Additional property limits is not allowed
- authProxy.resources: Additional property requests is not allowed
- customAnnotations: Additional property customized-annotation is not allowed
- nodeSelector: Additional property disktype is not allowed
- tolerations: Invalid type. Expected: object, given: array Why is |
Got same issue. Rolled back to helm chart version 3.8.0 - works fine |
👋 @githubeto, sorry for the delay; but I believe this is a duplicate of #471 ? |
This part was fixed in #480 The rest of errors is expected to be fixed the same as in #471 (comment) So closing this in favor of #471. Please watch that one: I'll update there once a new release is up. |
Brief summary
helm chart values
install commands:
error log:
k6-operator version or image
0.0.17
Helm chart version (if applicable)
k6-operator-3.9.0
TestRun / PrivateLoadZone YAML
not.
Other environment details (if applicable)
No response
Steps to reproduce the problem
Expected behaviour
helm install.
Actual behaviour
I also tried these.
The text was updated successfully, but these errors were encountered: