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.

Sign up for GitHub

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

Jump to bottom

[Bug] GrafanaDashboard unknown field #1276

Closed
oczek opened this issue Oct 16, 2023 · 1 comment
Closed

[Bug] GrafanaDashboard unknown field #1276

oczek opened this issue Oct 16, 2023 · 1 comment
Labels
bug Something isn't working needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@oczek
Copy link

oczek commented Oct 16, 2023 •
edited
Loading

Describe the bug
Grafana Dashboard error decoding envs value

GrafanaDashboard in version "v1beta1" cannot be handled as a GrafanaDashboard: strict decoding error: unknown field "spec.envs[1].value"

Version
v5.3.0

To Reproduce
Steps to reproduce the behavior:

  1. create dashboard file with envs configuration:
kind: GrafanaDashboard
metadata:
  name: dashboard
spec:
  instanceSelector:
    matchLabels:
      instance: "grafana"
  envs:
    - name: VAR
      value: "7d"
  1. kubectl apply -f dashboard.yaml

Expected behavior
Creating dashboard with envs variable should be possible

Suspect component/Location where the bug might be occurring
unknown

Runtime (please complete the following information):

  • OS: Linux
  • Grafana Operator Version v5.3.0
  • Environment: Kubernetes
  • Deployment type: deployed
@oczek oczek added bug Something isn't working needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 16, 2023
@oczek oczek changed the title [Bug] [Bug] GrafanaDashboard unknown field Oct 16, 2023
@weisdd weisdd added question Further information is requested bug Something isn't working needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed bug Something isn't working needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. question Further information is requested labels Oct 16, 2023
@weisdd
Copy link
Collaborator

weisdd commented Oct 16, 2023

Hi @oczek,
I believe it was fixed in #1199, which is part of v5.4.0, so you simply need to update the operator and apply new CRDs.

@weisdd weisdd closed this as completed Oct 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@oczek @weisdd