mbalassi commented on code in PR #313:
URL: 
https://github.com/apache/flink-kubernetes-operator/pull/313#discussion_r918952631


##########
docs/content/docs/operations/olm.md:
##########
@@ -0,0 +1,247 @@
+---
+title: "OLM"
+weight: 1
+type: docs
+aliases:
+- /operations/olm.html
+---
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+  http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# Managing Flink Operator Using OLM
+The Operator Lifecycle Management(OLM) helps install, update, and manage the 
lifecycle of all Operators in a Kubernetes Clusters. The 
[Operatorhub](https://operatorhub.io/) contains a catalog of community shared 
Kubernetes operators which are ready to be deployed using OLM.
+## Prerequisite
+1. Kubernetes Cluster. Use 
[kind](https://kind.sigs.k8s.io/docs/user/quick-start/) to create cluster 
locally if needed.

Review Comment:
   Did you test with minikube also? Our user examples use that, would be nice 
to keep consistent:
   
https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/try-flink-kubernetes-operator/quick-start/



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to