Can't start a pod anymore with graphql mutation without a networkVolumeId
When I run this mutation
I get the following error
This is very new it wasn't happening before, are we forced to use networkVolumeIds now?
11 Replies
+1
+1 Use REST API
@Madiator2011 is it better than the graphQL api?
ye less chance you can mees things up
perfect thank you
much easier to work with as on graphql one thing wrong and it will error out
where can I find it?
thank you
can the REST api terminate a POD vs stop it?
Delete a Pod - terminate
Stop a Pod - stop
thank you