ifurs / dexus-vault Goto Github PK

There is a kinda interesting behavior with using Dex storage "kubernetes"
As you know, Dex creates CRDs with interesting hashed names, and you may get errors like this:

"invalid kubernetes resource name: must match the pattern ^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$ and be no longer than 63 characters"

It's because Dex trying to validate the resource name of CRD and then the client(that responds to gRPC calls too) will return the error above if it does not match reqs, e.g check this https://github.com/dexidp/dex/blob/9451d87ca0c940463d043e9def0c967711e55ddf/storage/kubernetes/client.go#L87

Two questions:

• which secret engines must be enabled
• how to manage multiple engines, using modular/plugin structure or just add more handlers?