Custom ressources

[Fenrur]

First idea

Hello, I will see a feature that will help GitOps a lot.

A user custom resource, where we indicate in this custom resource, the name of the Emqx resource, the name of the user.

The operator would carry out the creation and reconciliation operations if in the db, the user is deleted manually to avoid any problems.

Once the resource is applied, a secret is created in the same namespace as the User resource.

secret name:
same user ressource name

This is composed of:

• user = user + - + random uuid
• password = a random strong password
• emqx = the associated emqx

Example

user-emqx.yml:

apiVersion: apps.emqx.io/.......
kind: User
metadata:
  namespace: hello
  name:  fenrur-user-emqx
spec:
  generateUserName: fenrur
  emqx: my-emqx

secret name created by the operator:

apiVersion: v1
kind: Secret
metadata:
  namespace: hello
  name:  fenrur-user-emqx
  labels:
    apps.emqx.io/managed-by: "emqx-operator"
    apps.emqx.io/instance: "my-emqx"
    ...
data:
   user: fenrur-447483bc-30d1-42a3-bab8-898abfae9afc
   password: STRONG PASSWORD
   emqx: my-emqx
type: Opaque

Second idea

But the best would be to have all the UI behavior as a custom resource.

[Rory-Z]

Hi, @Fenrur thanks for your idea

• About first idea, the EMQX customer resource have .spec.bootstrapAPIKeys, I think this can meet the needs of GitOps, can it meet your requirements?

• About second idea, lots of UI behavior is configure in etc/emqx.conf, so can set it by .spec.config.data, about EMQX configure, you can check https://docs.emqx.com/en/enterprise/v5.5.0/hocon/

[onedr0p]

I would love some way to set predefined users in a GitOps supported way, the current method appears to be pretty janky by looking at this solution

https://github.com/ahinko/home-ops/tree/main/kubernetes/apps/home-automation/emqx/cluster