I'm not opposed to creating an admin group by default but just want to clarify a little more. Why did we decide to just add an admin group by default rather than making this a lxd init option?

Also, can the permissions of this group be modified? Can the group be deleted? Who relies on the admin group being present?

I'm not opposed to creating an admin group by default but just want to clarify a little more. Why did we decide to just add an admin group by default rather than making this a lxd init option?

I think it is simpler to create the group with permissions, we can avoid adding another question on the lxd init flow.

Also, can the permissions of this group be modified? Can the group be deleted?

Currently, yes, I don't think we need to protect it, see below.

Who relies on the admin group being present?

The UI onboarding will reference the group. Currently, we suggest to 1. create the group 2. add the permission and 3. create the user with the group. We hope to simplify the onboarding to be a single step with creation of the user and referencing the group in a single command. The UI will show a note that if the group is not existing, this is how to create it. The note might be a solution for the question above to let users delete or change the group as they like and still have reliable onboarding instructions.

Comments should be resolved. Please have another pass at this one @markylaing

I misunderstood what you meant previously @markylaing Please have another pass at this one now.