Expose connect.host to be able to override Connect host

[volodymyrZotov]

Resolves #148

This PR provides an ability to use Connect deployed in the other namespace than the operator. Therefore, it also gives the ability to use a single Connect instance with multiple operators.

Instructions below demonstrate how to set up a single Connect instance in the default namespace and 2 operator instances, one in test1 namespace and the second in test2 namespace. Each of the operators watches for its own namespace (aka operator1 watches for namespace test1 and operator2 watches for namespace test2). Also, each operator uses a different Connect token saved in the Secret (onepassword-token1 and onepassword-token2).

Deploy Connect to the default namespace

helm install connect 1password/connect --set-file connect.credentials=1password-credentials.json -n default

Prepare namespace test1 and deploy Operator

• Create test1 namesapce kubectl create namespace test1
• Create Secret containing Connect token kubectl create secret generic onepassword-token1 --from-literal=token="<YOUR_CONNECT_TOKEN>" -n test1
• Deploy Operator

  helm install opearator1 1password/connect --set connect.create=false --set connect.host=onepassword-connect.default.svc.cluster.local --set operator.create=true --set operator.watchNamespace={test1} --set operator.token.name=onepassword-token1 --set operator.serviceAccount.name=onepassword-connect-operator1 --set operator.clusterRole.name=onepassword-connect-operator1 --set operator.applicationName=onepassword-connect-operator1 -n test1

  Note: you need to override clusterRole, applicationName, serviceAccount to be unique in order to be able to deploy other Operator instances. Also, pay attention to using the propper operator.token.name=onepassword-token1 and properly specify the namespace you want the Operator to watch for operator.watchNamespace={test1}. If no operator.watchNamespace is specified it watches for ALL namespaces. In order for the Operator to use Connect deployed in the default namespace override Connect host by setting connect.host=onepassword-connect.default.svc.cluster.local.

Prepare namespace test2 and deploy Operator

• Create test1 namesapce kubectl create namespace test2
• Create Secret containing Connect token kubectl create secret generic onepassword-token2 --from-literal=token="<YOUR_CONNECT_TOKEN>" -n test2
• Deploy Operator

  helm install opearator2 1password/connect --set connect.create=false --set connect.host=onepassword-connect.default.svc.cluster.local --set operator.create=true --set operator.watchNamespace={test2} --set operator.token.name=onepassword-token2 --set operator.serviceAccount.name=onepassword-connect-operator2 --set operator.clusterRole.name=onepassword-connect-operator2 --set operator.applicationName=onepassword-connect-operator2 -n test2

  Note: you need to override clusterRole, applicationName, serviceAccount to be unique in order to be able to deploy other Operator instances. Also, pay attention to using the propper operator.token.name=onepassword-token2 and properly specify the namespace you want the Operator to watch for operator.watchNamespace={test2}. If no operator.watchNamespace is specified it watches for ALL namespaces. In order for the Operator to use Connect deployed in the default namespace override Connect host by setting connect.host=onepassword-connect.default.svc.cluster.local.

Create OnepasswordItems

• Use the snippet below to create OnepasswordItems (replace itemPath with valid one)

  # test-cred.yaml
  apiVersion: onepassword.com/v1
  kind: OnePasswordItem
  metadata:
  name: test-creds
  spec:
  itemPath: "vaults/vauld_id/items/item_id"

• Create OnepasswordItem in test1 namespace kubectl apply -f test-cred.yaml -n test1
• Check that test-cred Secret is created kubectl get secret test-creds -n test1
• Create OnepasswordItem in test2 namespace kubectl apply -f test-cred.yaml -n test2
• Check that test-cred Secret is created kubectl get secret test-creds -n test2

Note: the same scenario will work if deploy all the Operators in the single namespace aka operators

[volodymyrZotov]

@jillianwilson FYI, autoformatting was applied to the README.md that's why it has a lot of changes. The only entry I added there is connect.host.