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

Sharing credentials between provisions of service instances #999

Closed
maleck13 opened this issue Jul 3, 2018 · 3 comments
Closed

Sharing credentials between provisions of service instances #999

maleck13 opened this issue Jul 3, 2018 · 3 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@maleck13
Copy link
Contributor

maleck13 commented Jul 3, 2018

Feature:

UseCase

I have an Operator that will deploy a number of service instances from a namespace broker into a privileged namespace based on a custom resource. These services are intended to be shared and consumed by users of the cluster. Once provisioned, I want to tell the broker to use a secret that contains the credentials and coordinates of a shared service with each subsequent provisions of that APB so that subsequent provisions can interact with the shared service without the need for the requesting user to know the credentials or coordinates of that service.

Currently, if you have perms, you can create a secret in the brokers namespace and have them mounted into a specific APB container using the broker-config https://github.com/openshift/ansible-service-broker/blob/master/docs/config.md#secrets-configuration

It would be useful to be able to define these secrets dynamically.

  • It would stop the need to redeploy the broker to pick up new secrets
  • It would mean you would not need to know all the details ahead of time.

Initial concerns

  • As the secret could change / be updated (for instance as one shared service became full and a new one was provisioned) , the broker will need to copy this credential for each provision or keep track of which service instances received which secret so that during a deprovision the APB would receive the correct values to interact with the same service again.

@eriknelson @jmrodri any thoughts on the concern of tracking which credential were given to which service instance.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 23, 2020
@jmrodri
Copy link
Contributor

jmrodri commented Sep 20, 2020

/close

@openshift-ci-robot
Copy link

@jmrodri: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants