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

add operatorhub bundle files #30

Merged
merged 5 commits into from
Jul 24, 2019
Merged

add operatorhub bundle files #30

merged 5 commits into from
Jul 24, 2019

Conversation

pb82
Copy link
Collaborator

@pb82 pb82 commented Jul 23, 2019

Add operatorhub bundle files for the 1.3.0 release

Verification steps:

  1. An OpenShift 4 cluster is needed
  2. Login to your OpenShift 4 cluster with oc and create the following OperatorSource:
apiVersion: operators.coreos.com/v1
kind: OperatorSource
metadata:
  name: pb82-operators
  namespace: openshift-marketplace
spec:
  type: appregistry
  endpoint: https://quay.io/cnr
  registryNamespace: pb82
  displayName: "Integreatly Operators"
  publisher: "Integreatly"
oc create -f ./operator-source.yaml
  1. Make sure the operator source is valid:
oc get operatorsource -n openshift-marketplace

There should be a value like this:

pb82-operators        appregistry   https://quay.io/cnr   pb82                  Integreatly Operators   Integreatly   Succeeded   The object has been successfully reconciled   22m
  1. In the OpenShift console, create a new project named grafana
  2. In the OpenShift console, navigate to Catalog -> OperatorHub
  3. In the left panel under Provider Type there should be a category Custom
  4. It might take a minute for OpenShift to recognize the new OperatorSource, refresh the page if it's not yet visible.
  5. Under the Custom category, you should find the Grafana Operator.
  6. Click on it, then select Install (make sure that the Grafana project is selected)
  7. Click on the Suscribe button and wait for the installation to finish.
  8. Make sure the operator is running in the grafana namespace and does not have any errors in the log.
  9. Create a Grafana Instance: Grafana.yaml and GrafanaWithRoute.yaml from the examples directory will both work, GrafanaWithIngressHost.yaml will only work on Kubernetes.
  10. Create dashboards and a data source and make sure everything works as expected.
  11. Log into the Grafana instance (credentials can be found in the CR) and make sure that the dashboards and data source have been created.

@pb82 pb82 requested a review from david-martin July 23, 2019 10:52
@pb82 pb82 changed the title add operatorhub bundle files [WIP] add operatorhub bundle files Jul 23, 2019
@pb82 pb82 changed the title [WIP] add operatorhub bundle files add operatorhub bundle files Jul 23, 2019
@pb82 pb82 mentioned this pull request Jul 24, 2019
9 tasks
Copy link

@davidffrench davidffrench left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pb82 Looks really good, great work. I have verified it using the steps provided. I have a few questions

  1. Who should the publisher be, Integreatly or Red Hat?
  2. Should you be allowed to create multiple grafana CRs in the same namespace? (Currently this is not the case). I can't imagine this would be allowed but wanted to check.
  3. If a GrafanaDashboard CR is updated with new json, should this be reflected in Grafana. This doesn't seem to be the case right now.

@davidffrench
Copy link

Questions answered in Hangouts. Approved

@pb82 pb82 merged commit 9adc566 into grafana:master Jul 24, 2019
@pb82 pb82 deleted the olm-files branch July 24, 2019 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants