This message was deleted.

Hi @cuddly-van-73431 If you want it completely obfuscated, using a secret is the best way to go. You can create a CRD to your liking and store information like the secret ID, which you can then use as a “link” to that screen imagine the flow: • no CRD or CRD but no secret ID, that initial extension screen takes you to the

create a secret

interface • if there’s a CRD, with a secret ID that is valid, that initial screen content switches for the ui of your extension It’s an idea, not 100% sure if it’s all going to work, but it’s an avenue I would pursue 🤔 Check the patterns for creating a CRD + storing a service token in this extension: https://github.com/StackVista/rancher-extension-stackstate it may be of use 😉

Has there been any activity/plans to introduce the ability to manage other general settings related to extensions, via the Rancher UI or other common Rancher components?