![Dmitrii Kabanov](/assets/img/avatar_default.png)
This patch set adds "startingDeadlineSeconds" field to cronJobs. When the field is not set, the controller counts how many missed jobs occured from the last scheduled time till now. And if it happends more than 100 time the job will not be scheduled. To avoid this the "startingDeadlineSeconds" field should be set to sufficient period of time. In this case the controller counts how many missed jobs occured during this period of time. The value of the field should be less than time (in seconds) needed for running >100 jobs (according to schedule). Change-Id: I3bf7c7077b55ca5a3421052bd0b59b70c9bbcf24
OpenStack-Helm
Mission
The goal of OpenStack-Helm is to provide a collection of Helm charts that simply, resiliently, and flexibly deploy OpenStack and related services on Kubernetes.
Communication
- Join us on Slack - #openstack-helm
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-5 on freenode
- Meeting Agenda Items: Agenda
Storyboard
Bugs and enhancements are tracked via OpenStack-Helm's Storyboard.
Installation and Development
Please review our documentation. For quick installation, evaluation, and convenience, we have a kubeadm based all-in-one solution that runs in a Docker container. The Kubeadm-AIO set up can be found here.
This project is under active development. We encourage anyone interested in OpenStack-Helm to review our Installation documentation. Feel free to ask questions or check out our current Storyboard backlog.
To evaluate a multinode installation, follow the Bare Metal install guide.
Repository
Developers wishing to work on the OpenStack-Helm project should always base their work on the latest code, available from the OpenStack-Helm git repository.