Must be able to modify existing python applications to integrate with new features/standards.
Should have opinions on Kubernetes deployments - they won’t need to set strategy but should be able to self-direct based on first software engineering principles.
25 apps running in AWS running on internal k8s hosted infrastructure. All deployed via CICD pipelines. Would like to take all 25 of those services and migrate them to equivalent infrastructure in GCP. They have their own cluster in GCP environment. They would like the running applications moved from the current CI/CD pipeline to a new pipeline that already exists and have the helm charts get updated..
They have existing helm charts, writing to a previous standard would like to have some enhancements..
No istio service meshing is not changing, their biggest ask is to change how they do secrets management.. custom solution to potentially leveraging vault..
Vault is already running... would be looking to add in the `init` container, might have some other solutions.. config interpolation might be performed as part of the app itself..
For the python implementation, its mostly the vault stuff, as the helm charts are re-written, they may have some better options..
Python would not be elaborate but would like experience running making small changes.. on the configuration side..
Here’s the source and a readme -- They are leveraging an internal framework that is maintained by the Demonware portions..
They have the part, with the CRD that is backed by a controller that fetches the secrets.. and syncs them into the cluster...
Some legacy apps have some older tracing implementation, that has since been extended out, department now offers tracing as a service... It’s even more bare bones than that, used to have a library that would annotate everything with tracing metadata.
Preceded by a broader library, would like someone to help migrate from the old library to the new library. (Python 3 Code)