Hi there I m trying to start up a new prefect server in kube

Question

Hi there I m trying to start up a new prefect server in kubernetes 1 2 1 and after getting everything wired up it seems to be missing a decent number of the graphql query definitions but it does seem to have the mutations defined For example when running this against the graphql interfact I get an error ``` query tenant id With error GRAPHQL VALIDATION FAILED Cannot query field tenant on type Query ``` However I can run the mutation to create a tenant Did I miss a step or a service somewhere Thanks

Anna Geller · Answer

Did you use the helm chart setup GRAPHQL VALIDATION FAILED is generic so hard to say immediately what s the root cause

Anna Geller · Answer

often this error occurs when you try to access some API route that is not available in your Server version e g I saw <https discourse prefect io t i cant use secrets using graphql on prefect server it throws an error graphql validation failed why 701 1|one> when a user was trying to use API requests for Prefect Cloud Secrets on Server

Anna Geller · Answer

other things to check your Hasura version should be I think gt = 2 0 9 based on whether you have a tenant you could try to create a default tenant using this command if you already have a default tenant then this should fail ```prefect server create tenant name default slug default``` the last thing I saw is that you may try adding this environment variable to make it work with Hasura 2 0 ```You may also need this environment variable export HASURA GRAPHQL V1 BOOLEAN NULL COLLAPSE=true```

Greg Wyne · Answer

Thank you very much Will go through all of these and see if this works

Greg Wyne · Answer

For that issue it was indeed the HASURA GRAPHQL environment variable would never have found that one on my own so thanks I think I have one more thing to go before this is all working as some context we are upgrading from 0 13 to 1 2 1 we use kubernetes job spec yaml files in order to define some annotations and secrets we need to have the job run The same kubernetes job spec we used to use is no longer working since it appears some values are being lost in translation in our case the annotations and secrets We used to use `KubernetesJobEnvironment` for this but in the newer version it want s us to use `KubernetesRun` instead I ll keep poking around but if you have any insights there that would be amazing

Greg Wyne · Answer

Ah I got it nevermind Super appreciate the help thanks again

Anna Geller · Answer

Gotcha I understand Have you seen this migration tutorial <https docs prefect io orchestration faq upgrading 1 0 html> it shows how to switch from environments to run configs