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

feat(deployments): move components to use deployments instead of RC #346

Merged
merged 1 commit into from
Sep 12, 2016

Conversation

kmala
Copy link
Contributor

@kmala kmala commented Sep 6, 2016

fixes #337 #338 #339

@deis-bot
Copy link

deis-bot commented Sep 6, 2016

@jchauncey, @krancour and @arschles are potential reviewers of this pull request based on my analysis of git blame information. Thanks @kmala!

@kmala kmala self-assigned this Sep 6, 2016
@kmala kmala added this to the v2.6 milestone Sep 6, 2016
spec:
replicas: 1
strategy:
type: Recreate
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For others to understand, Recreate is the important difference here compared to Controller / Router which use RollingUpdate

@helgi helgi added the LGTM1 label Sep 6, 2016
@kmala
Copy link
Contributor Author

kmala commented Sep 12, 2016

@krancour can you check the logger components?
@jchauncey can you check the monitor components?
@bacongobbler can you check the database component?

@bacongobbler
Copy link
Member

database component looks good to me. My only concern before was the rolling deployment model, but recreate should work.

@kmala kmala merged commit 301c966 into deis:master Sep 12, 2016
@kmala kmala deleted the controller branch September 12, 2016 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

We're only 1/2 way transitioned to deployments?
6 participants