Skip to content
This repository has been archived by the owner on Mar 16, 2019. It is now read-only.

Allow deploying different components to separate namespaces #3

Closed
alexvicegrab opened this issue Dec 17, 2018 · 1 comment
Closed

Allow deploying different components to separate namespaces #3

alexvicegrab opened this issue Dec 17, 2018 · 1 comment
Assignees
@alexvicegrab
Labels
enhancement New feature or request fabric
Projects
Planned improvements

Comments

@alexvicegrab
Copy link
Contributor

Currently, all is deployed to a single Kubernetes namespace. However, we should be able to deploy components to different namespaces (e.g. peers in one namespace, and orderers in another; or split a K8S space by organisational namespaces)
@alexvicegrab alexvicegrab added this to To do in Planned improvements via automation Dec 17, 2018
@alexvicegrab alexvicegrab added enhancement New feature or request fabric labels Dec 17, 2018
@alexvicegrab alexvicegrab moved this from To do to In progress in Planned improvements Jan 15, 2019
@alexvicegrab alexvicegrab mentioned this issue Jan 16, 2019
Merged
@alexvicegrab
Copy link
Contributor Author

Addressed by #21

Planned improvements automation moved this from In progress to Done Jan 16, 2019
@alexvicegrab alexvicegrab self-assigned this Jan 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@alexvicegrab alexvicegrab

Labels
enhancement New feature or request fabric
Projects
Planned improvements
  
Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexvicegrab