You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a small set of changes @matthewnolf and I had to make to get things working on our end with k3d. After updating the dependencies and regenerating the lock we were still seeing type errors,
Error: evaluating jsonnet: RUNTIME ERROR: Field does not exist: specType
tns/tanka/environments/default/main.jsonnet:132:14-36
During manifestation
...
Error: evaluating jsonnet: RUNTIME ERROR: Field does not exist: withPort
tns/tanka/vendor/tempo/tempo.libsonnet:68:7-44
During manifestation
The jsonnet changes to default/tempo resolved those errors for everything to come online properly.
The only remaining thing I found but haven't fixed is a 'Panel plugin not found: timeseries' error in the grafana dashboard. Not sure how to go about fixing that one quite yet, perhaps upgrading the version of grafana?
The only remaining thing I found but haven't fixed is a 'Panel plugin not found: timeseries' error in the grafana dashboard. Not sure how to go about fixing that one quite yet, perhaps upgrading the version of grafana?
This could be due to newer versions of Grafana. Does it work if you load it into Grafana 7?
The only remaining thing I found but haven't fixed is a 'Panel plugin not found: timeseries' error in the grafana dashboard. Not sure how to go about fixing that one quite yet, perhaps upgrading the version of grafana?
This could be due to newer versions of Grafana. Does it work if you load it into Grafana 7?
The Grafana version running is grafana/grafana:7.3.x-exemplars . I think we can update that in a followup to Grafana 8 but not sure it's the cause
The only remaining thing I found but haven't fixed is a 'Panel plugin not found: timeseries' error in the grafana dashboard. Not sure how to go about fixing that one quite yet, perhaps upgrading the version of grafana?
This could be due to newer versions of Grafana. Does it work if you load it into Grafana 7?
The Grafana version running is grafana/grafana:7.3.x-exemplars . I think we can update that in a followup to Grafana 8 but not sure it's the cause
Yeah now that it's up and running I'll merge this and maybe make another pass to get some of the apps updated to see what that does.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a small set of changes @matthewnolf and I had to make to get things working on our end with k3d. After updating the dependencies and regenerating the lock we were still seeing type errors,
The jsonnet changes to default/tempo resolved those errors for everything to come online properly.
The only remaining thing I found but haven't fixed is a 'Panel plugin not found: timeseries' error in the grafana dashboard. Not sure how to go about fixing that one quite yet, perhaps upgrading the version of grafana?