The JWT signing algorithm ES384 became unsupported after switch from golang-jwt to cap+jose. Likely due to a typo the RS384 algorithm is supported twice while ES384 is no longer supported.
Kubernetes officially supports this algorithm. That means that Kubernetes clusters that use this algorithm aren't able to upgrade to Vault 1.11 successfully. Because Vault 1.11. is using version 1.13. of the vault-plugin-auth-kubernetes.
The JWT signing algorithm ES384 became unsupported after switch from golang-jwt to cap+jose. Likely due to a typo the RS384 algorithm is supported twice while ES384 is no longer supported.![image](https://user-images.githubusercontent.com/5213151/187868813-888b2311-c14c-4936-a04d-71df10f359b0.png)
Kubernetes officially supports this algorithm. That means that Kubernetes clusters that use this algorithm aren't able to upgrade to Vault 1.11 successfully. Because Vault 1.11. is using version 1.13. of the vault-plugin-auth-kubernetes.