Adding Additional Roles and Removing Namespaces

**Why:**

* Allows deployment using the manifest file

Signed-off-by: Christopher Hein <[email protected]>

Author: christopherhein

configs/aws-operator.yaml

@@ -10,7 +10,6 @@ items:
   apiVersion: rbac.authorization.k8s.io/v1beta1
   metadata:
     name: aws-operator
-    namespace: aws-operator
   rules:
   - apiGroups:
     - v1
@@ -26,6 +25,17 @@ items:
     - create
     - delete
     - update
+  - apiGroups:
+    - extensions
+    resources:
+    - thirdpartyresources
+    verbs:
+    - get
+    - list
+    - watch
+    - create
+    - delete
+    - update
   - apiGroups:
     - apiextensions.k8s.io
     resources:
@@ -53,15 +63,14 @@ items:
   apiVersion: rbac.authorization.k8s.io/v1beta1
   metadata:
     name: aws-operator
-    namespace: aws-operator
   roleRef:
     apiGroup: rbac.authorization.k8s.io
     kind: ClusterRole
     name: aws-operator
   subjects:
   - kind: ServiceAccount
     name: aws-operator
-    namespace: default
+    namespace: aws-operator
 
 - kind: Deployment
   apiVersion: apps/v1beta1
@@ -86,6 +95,7 @@ items:
             - name: AWS_SECRET_ACCESS_KEY
               value:
           args:
+            - server
             - --cluster-name=<cluster-name>
             - --region=<region>
             - --bucket=<bucket-name>