Skip to content

Document networkpolicys to talk to operator #910

@NissesSenap

Description

@NissesSenap

You could argue that this is out of scope for the operator but I want a discussion around it.
If we deploy grafana instances in namespaces that isn't the same as the grafana-operator we will get issues with networkpolicy assuming that the cluster admins have set good default settings.

This will create issues.
From a user point of view it would be nice to setup a networkpolicy that enables the operator to talk to the instance that it creates.
On the other hand this operator already got sooo much rbac access, giving it access to networkpolicy might be a step to long.

I'm leaning a bit that we shouldn't add this feature, instead provide example networkpolicies that you could use but nothing more then that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationIssues relating to documentation, missing, non-clear etc.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions