We utilize the Humio Operator to configure Humio Views for different users across the org.
We have okta groups for the different teams accessing the different views.
Currently we're using the Humio Operator to create the Humio Views and then we still need to integrate with the Humio API to do the graphql mutation to add the Okta group and add the respective roles to the Humio Group.
Our ideal would be that we only need to integrate with the Kubernetes API that has the operator installed and not partially use the Kubernetes API and partially use the Humio API via our provisioner.

We think Humio Groups should be represented as CRD object via the Humio Operator. That way we can just create HumioView and HumioGroup custom resources and only need to integrate with the K8s API.