Skip to content
This repository has been archived by the owner on Jan 19, 2018. It is now read-only.

kubernetes: remove running components if one component fails #429

Open
dustymabe opened this issue Nov 30, 2015 · 4 comments
Open

kubernetes: remove running components if one component fails #429

dustymabe opened this issue Nov 30, 2015 · 4 comments
Assignees
@rtnpro
Labels
provider:kubernetes
Milestone
CDK 2.1

Comments

@dustymabe
Copy link
Contributor

Child issue of #319 for the kubernetes provider.
@dustymabe dustymabe mentioned this issue Nov 30, 2015
Open
@dustymabe dustymabe added this to the CDK 2 GA milestone Nov 30, 2015
@dustymabe dustymabe assigned rtnpro and unassigned kadel Jan 12, 2016
@kadel kadel added blocker and removed blocker labels Feb 4, 2016
@rtnpro
Copy link
Contributor

rtnpro commented Feb 9, 2016

Fixed in #456 . Are we considering it for GA?

@rtnpro
Copy link
Contributor

rtnpro commented Feb 9, 2016

@cdrage ^^

@cdrage cdrage modified the milestones: CDK 2.1, CDK 2 GA Feb 11, 2016
@cdrage
Copy link
Member

cdrage commented Feb 11, 2016

Hey @kadel are you still being blocked by this?

@dustymabe dustymabe removed the blocker label Feb 11, 2016
@rtnpro
Copy link
Contributor

rtnpro commented Feb 17, 2016

We've decided not to merge the atomic deployment feature into atomicapp for GA because:

  • it's a risky change
  • it's an enhancement
  • this scenario was not at all considered in the product design for Nulecule/atomicapp.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@rtnpro rtnpro

Labels
provider:kubernetes
Projects
None yet
Milestone
CDK 2.1
Development

No branches or pull requests
4 participants
@kadel @rtnpro @dustymabe @cdrage