volumeEncrypted Broken in API

When creating a new pod using the GraphQL API, requests that specify volumeEncrypted, whether true or false, fail with the response “Internal server error” instead of a pod ID. Setting “volumeKey” alongside volumeEncrypted doesn’t fix this either. I am able to create pods without this parameter, so I believe my query is well formed I assume this is a known issue but is there any way around this, other than keeping an encrypted pod in an exited state? Thanks in advance.
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?