DiamondLightSource / DiamondLightSource/python-copier-template

Add a helm chart for deploying Python services to Kubernetes

未关闭
#286 1 条评论 0 个 reaction 已指派 1 人 已被 @gilesknap 认领 在 GitHub 查看
主要语言
Jinja
星标
25
派生
10
平均合并
4 小时 4 分钟
30 天内合并 PR
6

描述

The fastcs helm chart should be made generic and included in this repo
https://github.com/DiamondLightSource/FastCS/blob/b46ee3e1607896ba91bfb7180d5c74d31129671d/Charts

Notes:-

- For a project that publishes containers referred to by the helm chart, the `_containers.yml` workflow should be added to the `needs` of _helm in `ci.yml`.
- inspect the values of `editable` and `autostart` in the `values.yaml` file of the specified IOC (TODO: at present it uses the p47-services source code to do so but this should be determined from the cluster in future).
- also see https://github.com/epics-containers/p47-services/blob/f6e6aa6383db204f4e9a3b7b05f9234562f10247/debug.py for how the editable and autostart features are used.
- inspection of the values of `editable` and `autostart` in the `values.yaml` file of the specified IOC currentl uses the p47-services source code to do so but this should be determined from the cluster in future.
- note that symlinks from the /schemas folder to the individual Charts/xxx/values.schema.json should be supplied (document the manual process or automate it) AND we need a solution like this:https://github.com/DiamondLightSource/FastCS/blob/b46ee3e1607896ba91bfb7180d5c74d31129671d/schemas/fastcs-service.schema.json for making a schema for the services repository - but where should that go?

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。