The direct license upload feature in Redpanda Console can cause issues (manual restarts, license overrides) when deployed in Kubernetes via Helm or an operator. The user suggests adding a warning banner or disabling the upload functionality in such environments to prevent "foot-guns".
Thanks to @JakeSCahill for bringing this to my attention. Console's new (?) ability to directly upload a license to redpanda is great but could lead to some accidental foot-guns if deployed in Kubernetes via the helm chart or operator. 1. Console will require a manual restart. This would require a user to manually delete the console Pods after uploading the console. 2. The uploaded license may get overridden if the redpanda license is also managed via helm or the operator. Neither of these are particularly nasty but 2. could certainly lead to some head scratching or perhaps some unexpected downtime if redpanda doesn't reject expired licenses. I'd be ideal if console could either disable the ability to upload licenses or perhaps display a warning with a link to our docs with an explanation of the warning. As for the restart... console could just crash itself and rely on Kubernetes to restart it but that's likely not the most pleasant experience. Console could either garn