Add python-persistent helm chart. #2989
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
Explain the details for making this change. What existing problem does the pull request solve?
Some python applications are currently deployed with the
node-persistent
service type to allow binding a persistent volume to the deployment. This introduces apython-persistent
service type for semantic separation of deployments.The main driver behind this is CKAN deployments as they currently rely on a PV. The
node-persistent
service type uses a TCP liveness probe rather than HTTP. This means that we cannot include Layer7 validations for CKAN to get Kubernetes to restart the pods.The python liveness probe is configured for HTTP, so we can add additional listeners and application lookups to determine if a scaling event has moved the PG pod and have kubernetes restart the CKAN pod.
Closing issues
Closes #2988