How to install from the command line

[software-engr-full-stack]

Sorry if this is a basic question but I haven't found the solution after searching online.

How do I install this operator from the command line?

I can install a service mesh operator using kubectl apply -f using this file:

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: servicemeshoperator
  namespace: openshift-operators
spec:
  channel: stable
  name: servicemeshoperator
  source: redhat-operators
  sourceNamespace: openshift-marketplace

But it doesn't work with this operator (after replacing the relevant fields like "name" and "source". By "it doesn't work" I mean when I look up the "Installed Operators" page under "Operators" in the OpenShift web UI (Admin mode), the status is not "Succeeded" like the other operators that were installed successfully.

Thanks in advance.

[jcantrill]

Without additional details, it sounds as if you are missing an operator group. Following is the script used to do deployment for running the e2e tests.

[anpingli]

You should deploy elasticsearch-operator under openshift-operators-redhat namespace.

1. Create namespace openshift-operators-redhat
2. Create operatorgroup

cat <<EOF |oc create -f -
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: openshift-operators-redhat
  namespace: openshift-operators-redhat
  spec: {}
EOF

3. subscribe to catalogsource

cat <<EOF |oc create -f -
{
  "apiVersion": "operators.coreos.com/v1alpha1",
  "kind": "Subscription",
  "metadata": {
    "name": "elasticsearch-operator"
  },
  "spec": {
    "channel": "stable",
    "installPlanApproval": "Automatic",
    "name": "elasticsearch-operator",
    "source": "redhat-operators",
    "sourceNamespace": "openshift-marketplace"
  }
}
EOF

[anpingli]

For more detail, you can refer to https://docs.openshift.com/container-platform/4.13/logging/cluster-logging-deploying.html#cluster-logging-deploy-cli_cluster-logging-deploying

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.