Create a secret for the license, rather than using (only) a flag (for the operator) about inlets-operator HOT 10 OPEN

Spent the weekend fighting my RPis and net booting.

Ill start working on this this evening if thats ok.

from inlets-operator.

/add label: help wanted

from inlets-operator.

/assign: me

Ill raise an issue on arkade to switch to this too

from inlets-operator.

Thanks Alistair

from inlets-operator.

Hi @Waterdrips did you have a chance to start this yet?

from inlets-operator.

Sounds good. Hope you won 😁

from inlets-operator.

@viveksyngh do you want to take a look?

from inlets-operator.

/derek assign me

from inlets-operator.

@alexellis I was thinking if we can create a secret with the licence and then using secret name as input to the the controller. Which will be read by the controller to the read the secret and also set a watch for that, so in case if this get's updated controller will reconcile all objects.

from inlets-operator.

Part 1a is just changing the helm chart to use a secret name/reference instead of a literal value, but keeping backwards compatibility. Part 1b is changing the arkade app to create the new secret and instruct the helm chart to use it.

See how we do that for arkade and openfaas - https://github.com/alexellis/arkade/blob/master/cmd/apps/openfaas_app.go#L126

Part 2 is more along the lines of what you're saying. We may need one master secret per namespace with the license in it, or one new license secret per client.

from inlets-operator.