Running vault secrets disable kubernetes fails here if credentials are issued but the k8s cluster is no longer available.
The consequence seems to be that the secret engine cannot be removed.
There should probably be another function that is used when disabling the secret engine that tries to revoke the secret, but fails more gracefully.
Running
vault secrets disable kubernetesfails here if credentials are issued but the k8s cluster is no longer available.The consequence seems to be that the secret engine cannot be removed.
There should probably be another function that is used when disabling the secret engine that tries to revoke the secret, but fails more gracefully.