Merge pull request #22 from darkowlzz/apiversion-update

Update apiVersion to operators.coreos.com/v1alpha1

Author: rithujohn191

README.md

@@ -133,7 +133,7 @@ Deploying an Operator is as simple as applying the Operator’s manifest to the
 ```sh
 $ curl -Lo memcachedoperator.0.0.1.csv.yaml https://raw.githubusercontent.com/operator-framework/getting-started/master/memcachedoperator.0.0.1.csv.yaml
 $ kubectl apply -f memcachedoperator.0.0.1.csv.yaml
-$ kubectl get ClusterServiceVersion-v1s memcachedoperator.v0.0.1 -o json | jq '.status'
+$ kubectl get ClusterServiceVersion memcachedoperator.v0.0.1 -o json | jq '.status'
 ```
 
 After applying this manifest, nothing has happened yet, because the cluster does not meet the requirements specified in our manifest. Create the CustomResourceDefinition and RBAC rules for the Memcached type managed by the Operator:

memcachedoperator.0.0.1.csv.yaml

@@ -1,8 +1,8 @@
 # This file defines the ClusterServiceVersion (CSV) to tell the catalog how to display, create and
 # manage the application as a whole. If changes are made to the CRD for this application kind,
 # make sure to replace those references below as well.
-apiVersion: app.coreos.com/v1alpha1
-kind: ClusterServiceVersion-v1
+apiVersion: operators.coreos.com/v1alpha1
+kind: ClusterServiceVersion
 metadata:
   name: memcachedoperator.v0.0.1
   namespace: default

memcachedoperator.0.0.2.csv.yaml

@@ -1,8 +1,8 @@
 # This file defines the ClusterServiceVersion (CSV) to tell the catalog how to display, create and
 # manage the application as a whole. If changes are made to the CRD for this application kind,
 # make sure to replace those references below as well.
-apiVersion: app.coreos.com/v1alpha1
-kind: ClusterServiceVersion-v1
+apiVersion: operators.coreos.com/v1alpha1
+kind: ClusterServiceVersion
 metadata:
   name: memcachedoperator.v0.0.2
   namespace: default