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

Allow APBs to mount in volumes from the host #812

Closed
rthallisey opened this issue Mar 2, 2018 · 4 comments
Closed

Allow APBs to mount in volumes from the host #812

rthallisey opened this issue Mar 2, 2018 · 4 comments
Labels
feature lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. unplanned Issue is recognized but not planned for any release

Comments

@rthallisey
Copy link
Contributor

Feature:

APBs currently only interact with cluster resources. As we expand our library of APBs, some workflows will need to change things on the hosts they run on. Provide a mechanism for APB authors to configure the volumes mounted into an APB pod.

This features needs a proposal to:

  • Address security concerns
  • Provide a plan for a solution
@rthallisey rthallisey added feature 3.10 | release-1.2 Kubernetes 1.10 | Openshift 3.10 | Broker release-1.2 labels Mar 2, 2018
@rthallisey rthallisey added 3.11 | release-1.3 Kubernetes 1.11 | Openshift 3.11 | Broker release-1.3 3.10 | release-1.2 Kubernetes 1.10 | Openshift 3.10 | Broker release-1.2 and removed 3.10 | release-1.2 Kubernetes 1.10 | Openshift 3.10 | Broker release-1.2 3.11 | release-1.3 Kubernetes 1.11 | Openshift 3.11 | Broker release-1.3 labels Mar 6, 2018
@jmrodri jmrodri added 3.12 | release-1.4 Kubernetes 1.12 | Openshift 3.12 | Broker release-1.4 and removed 3.11 | release-1.3 Kubernetes 1.11 | Openshift 3.11 | Broker release-1.3 labels Jul 23, 2018
@jmrodri
Copy link
Contributor

jmrodri commented Jul 23, 2018

@rthallisey do we still need this feature? If not, please close.

@jmrodri jmrodri added unplanned Issue is recognized but not planned for any release and removed 3.12 | release-1.4 Kubernetes 1.12 | Openshift 3.12 | Broker release-1.4 labels Nov 12, 2018
@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 29, 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
feature lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. unplanned Issue is recognized but not planned for any release
Projects
None yet
Development

No branches or pull requests

4 participants