Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOC]: Improve OpenShift operator documentation #3572

Open
alonsocamaro opened this issue Sep 25, 2024 · 1 comment
Open

[DOC]: Improve OpenShift operator documentation #3572

alonsocamaro opened this issue Sep 25, 2024 · 1 comment

Comments

@alonsocamaro
Copy link

alonsocamaro commented Sep 25, 2024

Title

Improve OpenShift operator documentation

Description

At present:

  • There is no information on on what is the difference weather the operator should be installed for all namespaces or in a separate namespace. I find that in both the operand allows to:

    • Specify where the instances are deployed (spec.namespace parameter)
    • Which CIS namespaces will be able to watch

    Some guidelines should be provided to clarify the namespace usage for the operator, and where the CIS is installed.

  • There are no general guidelines on how to setup the operand.

  • The following section applies when deploying an operand, not the operator IMHO

Before you install CIS using Operators on OpenShift, you must create BIG-IP login credentials to use with Operator Helm Charts:

oc create secret generic <SECRET-NAME> -n kube-system
--from-literal=username=<USERNAME> --from-literal=password=<PASSWORD>
@trinaths
Copy link
Contributor

Created [CONTCNTR-4950] for internal tracking.

@trinaths trinaths added bug JIRA and removed feature-request untriaged no JIRA created labels Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants