Skip to content

Conversation

@pigmej
Copy link
Contributor

@pigmej pigmej commented May 8, 2017

This change is Reviewable

dshulyak and others added 26 commits March 10, 2017 15:52
Instead of running ac-run inside of the appcontroller pod user will
have to create documented config map with several fields (concurrency, labels selector).

appcontroller process will listen to changes for that config map and run deployment graph
processing, on deletion of configmap we will terminate deployment workflow.

It will allow us to provide guarantees that workflow will be finished even if appcontroller
pod will crash.
Refactor appcontroller to work as long running controller
This is mainly required for tests and not supposed to be used on
production
Use kubeadm on CI and make it work on kube 1.6
- Add copyright notices

- Currently, CI pushing images only with latest tag:
  https://travis-ci.org/Mirantis/k8s-AppController/jobs/203410745#L1998-L2001
  No one paid attention to this, because the "after_success" step failure
  doesn't fail build:
  travis-ci/travis-ci#758
  And at the moment a good fix is to use this as the last entry of
  "script" step instead of "after_success" step.
- Fixed syntax
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.

5 participants