1.7 KiB
1.7 KiB
lang, kind, section
| lang | kind | section |
|---|---|---|
| en | explain | specification |
Module structure
graph TD
base --> kubectl
kubectl --> helm
product --> helm
helm --> sale_helm
sale_helm --> website_sale_helm
website_sale --> website_sale_helm
Object model
!Specification Sale Helm.excalidraw
Odoo models
The most important models and fields.
Kubectl Context
Name: kubectl.context
cluster_idKubeconfig connects to this cluster.configContent of the kubeconfig.
Kubectl Cluster
Name: kubectl.cluster
server: Hostname of Kubernetes cluster.povider_id: Link the Hosting provider.context_ids: Connected kubeconfigs.
Kubectl Namespace
Name: kubectl.namespace
cluster_idThe namespace belongs to a cluster.
Helm Chart
Name: helm.chart
name: Name of the chart.values: Content of thevalues.yaml.value_ids: Links Helm chart values.
Helm Release
Name: chart.release
namespace_id: Namespace the release is connected to.chart_id: Links the chart.values: Content of customer specificvalues.yaml
Once a release is installed, the admin can edit the values and upgrade the release. For the customer portal there will be explicit fields and validations to change the content of vaules.
The admin can download the manifest.yaml and values.yaml.
Helm Chart Value
Name: helm.chart.value
chart_id: References the helm chart .path: Path expression of the value key.value: Python expression that defines the value. Has access tosale_idandchart_id.field_id: Instead of applied to avalues.yamlthe value is applied to a release field.
The chart values are evaluated once.