consistent implementation of liveness and readiness probes accross all openstack helm charts
Registered by
Matthias Omisore
Although openstack helm supports the implementation of liveness and readiness probes. There is currently no coherent way of implementing them. This proposes a blueprint for determining the kind of probe (tcpSocket, httpGet or command) to implement based on the service/container being probed, whether its a local Service, API or Port. . The probes fields (periodSeconds, InitialDelaySec
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Matthias Omisore
- Direction:
- Needs approval
- Assignee:
- Matthias Omisore
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
patches:
https:/
https:/
(?)