edgelevel/lastpass-operator

A Kubernetes Operator to manage secrets stored in LastPass password manager

lastpass-operator's Issues

TODOs after #8 is merged

See #8

• release latest version
• update readme/doc e.g. remove dep, etc.
• remove travis
• setup ci + docker publish with gh-actions
• upgrade chart to Helm 3
• update lastpass.Logout(), see comment
• bump to latest operator-sdk version (try at least)
• verify project settings e.g. branch protection

Missing namespace in RBAC ServiceAccount

The RBAC templates to create the ServiceAccount do not take into account the namespace specified in the values.yaml. This causes the ServiceAccount to be created in the namespace where the Helm command is performed and not in the desired namespace.

I think it should be changed from:

---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: {{ .Values.name }}

to:

---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: {{ .Values.name }}
  namespace: {{ .Values.namespace }}

Secret name

Hi,
i want to understand why are you trying to use lastpass id in secret name?
With deployment that will try to use that secret you will need to first create that secret and later assign it to deployment.

Support creation of dockerconfigjson secret type

Current Behaviour:
The lastpass-operator supports the creation of Opaque secrets.

Enhanced behaviour:
Add the flexibility in the LastPass custom resource to choose the type of secret to be created.

type: kubernetes.io/dockerconfigjson
key: .dockerconfigjson

Example secret for docker credentials

apiVersion: v1
kind: Secret
type: kubernetes.io/dockerconfigjson
metadata:
  name: regcred
  namespace: bots
data:
  .dockerconfigjson: ewogICAiYXV0aHMiOnsKICAgICAgImh0dHBzOi8vaW5kZXguZG9ja2VyLmlvL3YxLyI6ewogICAgICAgICAidXNlcm5hbWUiOiJVc2VybmFtZSIsCiAgICAgICAgICJwYXNzd29yZCI6IlBhc3N3MHJkIiwKICAgICAgICAgImVtYWlsIjoic29tZW9uZUBnbWFpbC5jb20iLAogICAgICAgICAiYXV0aCI6IlZYTmxjbTVoYldVNlVHRnpjM2N3Y21RPSIKICAgICAgfQogICB9Cn0=

Example last pass configuration for docker credentials which will be stored as a base64 string under the .dockerconfigjson key

{
   "auths":{
      "https://index.docker.io/v1/":{
         "username":"Username",
         "password":"Passw0rd",
         "email":"[email protected]",
         "auth":"VXNlcm5hbWU6UGFzc3cwcmQ="
      }
   }
}

Add metrics

We'd like to use the operator in production.

However, currently, the metrics expose generic information about the pod itself, rather than useful insight.
Useful metrics could include;

• Is the operator logged in at Lastpass
• Total amount of requests to LastPass
• Amount of errors at the operator + reason
• Generic health of operator

etc..

Is this something one could easily create?

Synchronize folders

Hey there, love the project !

Is it possible to synchronize a full LastPass folder ?
If I understand correctly, you currently need to write one configuration file for each secret you want to keep in sync.