[tenant-namespace-operator] Switched to helm module in k8s ansible collection

[plnordquist]

• Updated to latest community.kubernetes collection
• Switched to relative paths for watches.yaml for easier development
• Added symlink for build/Dockerfile for operator-sdk run --local
• Added collection references to role meta
• Removed helm-diff plugin since helm module checks values and version for changes
• Removed temp file in role as helm module accepts python dict
• Switched to snake case reference to flavor
• Added label for namespace type

As listed above I've symlinked the Dockerfile so the operator sdk can run locally for fast development of the Ansible roles. I think that symlink can go away when the build scripts for the container can point to a Dockerfile not in the current working directory. The build script might need a configurable location to look for the /.extrafingerprints file as well since a non-root user can't write to / without pre-creating the file as root.

I've updated the Dockerfile to drop root when running non-root required commands and skipped adding the miscscripts repository by passing the repository when calling helm pull. The unpacked chart now ends up in the home directory of the operator user which is easier to replicate in a local dev environment.

It looks like the version of the container is being put in the /.extrafingerprints file, should this PR update that version?

[kfox1111]

Looks good. Can you make a couple more tweaks please:
update containers/tenant-namespace-operator/buildenv to be export PREFIX=0.1.6
update charts/charts/tenant-namespace-operator/Chart.yaml and set version: 0.1.8 and appVersion: 0.1.6-1

Those are not automated yet unfortunately. Otherwise, looks great. Thanks for reworking this. :)

[plnordquist]

I've updated the versions now. These changes might be worth a minor version bump but I've bumped the versions as per your comment.

I should have said in the first post but there is an issue with Ansible failures where it will immediately attempt another reconciliation so the operator kind of gets stuck attempting to create a tenant when a referenced flavor does not exist, see https://github.com/operator-framework/operator-sdk/issues/2502.

[kfox1111]

Yeah. It could be a minor version bump, as it does add a little bit of functionality with the namespace labels. Its < 1 though, so probably close enough.

I think the operator misbehaved when flavor was nonexistent before too. So probably not a regression. Since normal users cant do TenantNamespaces, its good enough for now.