Provide real Helm deployer to Landscaper
In-Ko opened this issue · comments
Description
Currently, the Landscapers "Helm Deployer" only uses the Helm Templating mechanism, which is sufficient for the Gardener usecase / Helm-based deployments, but not for other Stakeholders of the Landscaper.
So we have to provide another Deployer for the Landscaper, which encapsulates the complete feature-set of the Helm Client. We might not be able to use the Potter Helm-Deployer, but should be able to benefit from our previous knowledge when we have created that deployer for the Potter.
Done Criteria
- All Features implemented
- Code has been reviewed by other team members
- Unit Tests created for new code
- Integration Test Suite updated (if applicable)
- Internal technical Documentation updated
- Enduser Documentation updated (if applicable)
- Successful demonstration in Review
Approach: Try to integrate helm helm chart repos and helm deployment in current helm deployer. We start with helm chart repo
Todos:
- Implement Helm Chart Repo Access
- Authentication
- synchronise helm chart repo catalog cache access
- Implement real helm deployment
- install
- uninstall
- check namespace creation/deletion
Done:
- Access to unprotected helm chart repo
moved to other backlog project
@In-Ko should we close this?
Yes, as issue is now tracked in the new backlog project.