Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to mount 1password-credentials.json via PVC #199

Open
yalattas opened this issue Jul 12, 2024 · 0 comments
Open

Ability to mount 1password-credentials.json via PVC #199

yalattas opened this issue Jul 12, 2024 · 0 comments

Comments

@yalattas
Copy link

Summary

All examples refers to credentials: variable to provide content of 1password-credentials.json file. Yet, some are using GitOps to render the template and the then apply without using helm release.

Another people, will use helm CICD, will be a bit difficult to pass extra argument other than what's expected (values.yaml and secrets.yaml )

Another case where people are using helmfile instead,

Therefore, its better to allow volume mounting into operator container so I can put the content of the file in secrets then mount the secret into a specific path in operator container and point the application to use this JSON file

dataVolume:
    # The name of the shared volume used between 1Password Connect Containers
    name: shared-data
    # The type of the shared volume used between
    # 1Password Connect Containers
    type: emptyDir
    # Desribes the fields and values for configuration of
    # shared volume for 1Password Connect
    values: {}

Above snippet isn't clear and haven't found sufficient example of its usage. Values expects dictionary, key=value how can I provide JSON content to be shared across pods

Use cases

1- fetch JSON from external secret within k8s cluster
2- fetch JSON from external ConfigMap within k8s cluster

Proposed solution

Allow mounting to operator pod via helm chart

Is there a workaround to accomplish this today?

Currently base64, yet initially failed for some reason, when I followed the example, encoding values was different.
I am using GitOps so CD solution will do the apply and will be responsible to generate the secret in advance for 1password operator to use it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant