https://prefect.io
Join Slack
hey everyone! i'm trying to add the Prefect Server Helm chart as a dependency to an existing helm ch...
# prefect-server
c
hey everyone! i'm trying to add the Prefect Server Helm chart as a dependency to an existing helm chart. If I want to prefix/rename EVERYTHING that is in the Prefect Server helm chart, is there an easy way to do that?
discourse 1
z
c
i saw that, but it was a tid bit headscratching, with respect to 
namePrefix
nameSuffix
too... in my top-level chart, should i set 
nameOverride
or 
namePrefix
or 
nameSuffix
for each component?
z
Yeah šŸ˜„
Soā€¦ the name for each object is created with
Copy code
{{- $name := print (.namePrefix | default "") ( .component ) (.nameSuffix | default "") -}}
{{ printf "%s-%s" .Release.Name $name | trunc 63 | trimSuffix "-" }}
Where the first chunk is the name of the helm release
And the second chunk is the ā€œnameā€ which has a prefix, component, and suffix
The prefix and suffix there are internal to the chart, although we could expose their default value in the values file if itā€™d be helpful.
It sounds like you want to change the first chunk though, which is just the release name
A Release is an instance of a chart running in a Kubernetes cluster. One chart can often be installed many times into the same cluster. And each time it is installed, a new release is created. Consider a MySQL chart. If you want two databases running in your cluster, you can install that chart twice. Each one will have its own release, which will in turn have its own release name.
c
exactly, so my Chart.yml looks something like this:
Copy code
apiVersion: v2
name: my-app
type: application
version: 0.0.0
appVersion: "1.16.0"
...
dependencies:
  - name: postgresql
    version: "~9.3.2"
    repository: <https://charts.bitnami.com/bitnami>
    condition: postgresql.useSubChart
  - name: prefect-server
    version: "2022.01.25"
    repository: <https://prefecthq.github.io/server/>
so currently its colliding on the service account name and postgres (and we already have a component called ui as well) i think prefect's helm is trying to make 
my-app-postgresql
which is already taken by 
my-app
z
Hmmm
I think we might need to add something to the chart to make this possible
c
i think this is the possible issue: https://github.com/PrefectHQ/server/blob/master/helm/prefect-server/templates/_helpers.tpl#L27 i believe the helper is taking 
.Chart.Name
or which is in this case, 
my-app
, and only allowing 
.Values.nameOverride
as an alternative?
z
What happens if you provide a nameOverride to the server chart?
The name of the component uses the release name, not the chart name, so I donā€™t think nameOverride takes effect
c
in my top level values.yaml, i've been playing with something like this...
Copy code
prefect-server:
  nameOverride: prefect-server
  useSubChart: false
  postgresql:
    nameOverride: prefect-server-postgresql
  serviceAccount:
    name: prefect-server
but that nested nameOverride seems to have no effect? (PSA I'm new to the way values.yaml are munged for subcharts)
z
Yeah only the top-level name override will do anything
And itā€™ll just override the chart name, not the component names
c
ahh dang šŸ˜•
z
c
that looks pretty good, wouldn't we want an option of somekind to conditionally do the new naming, for backwards compatibility?
z
Perhaps, Iā€™m not actually sure how helm will behave on upgrade when names change
In theory, itā€™ll just replace the components with the newly named ones.
c
i believe the service yamls use 
nameField
as well, so in theory the generated DNS name would likely change, that might break anyone that's hardcoded the DNS name of apollo, for example
i'm wondering if just allowing 
.namePrefix
or 
.nameSuffix
to be provided in values would do the trick?
z
Ah yes, hm. Iā€™m not really enthused about including a boolean. Iā€™ll see what the rest of the team thinks.
Wellā€¦ those are supposed to be internal for different uses of 
nameField
like if somewhere in the chart we had two names for the same component and wanted to add a suffix to one
Itā€™d have to be change to be global prefix/suffix values and Iā€™d rather just fix the default names.
c
gotcha, i understand! let me know what the rest of the team thinks!
FYI, i've worked around this by simply doing another chart install outside of my standard app install
z
Iā€™ve added a toggle to the PR for backwards compatibility
c
wonderful thanks!! does this land in the Helm Repo once its pushed to master?
z
No, Iā€™ll cut a new server release today though
c
šŸš€ you rock thanks!
43 Views
Open in Slack
PreviousNext
Powered by

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by