upbound / provider-vault

A Crossplane provider for HashiCorp Vault
Apache License 2.0
15 stars 9 forks source link

k8s auth backend -- no authbackend type #32

Open reedjosh opened 6 months ago

reedjosh commented 6 months ago

What happened?

Tried to create a kubernetes auth backend.

Used authBackendConfig

But there is then no path for that backend.

Errors:\n\n* no handler for route 'auth/k8s-test-cluster/config': "

Most other backends have an authbackend type.

In terraform I'd do something like:

resource "vault_auth_backend" "kubernetes" {
  type = "kubernetes"
  path = "k8s-${local.cluster_name}"
}

Which would create the backend.

I'm going to try using the token backend, but not sure if that will work, and it seems a bit odd that this doesn't exist for the k8s backend.

Thanks!

reedjosh commented 6 months ago

Well, that was quick.

I see the following in the generated examples.

apiVersion: auth.vault.upbound.io/v1alpha1
kind: Backend
metadata:
  annotations:
    meta.upbound.io/example-id: kubernetes/v1alpha1/authbackendconfig
  labels:
    testing.upbound.io/example-name: kubernetes
  name: kubernetes
spec:
  forProvider:
    type: kubernetes

Suppose I'll go give that a try. : )

reedjosh commented 6 months ago

Yup, this totally works.

I'll leave this for ya'll to close so you can at least witness the silly shenanigans your newb users are getting up to. 🙃