-
Notifications
You must be signed in to change notification settings - Fork 401
fix #1188 #1189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
fix #1188 #1189
Conversation
kagent-dev#1188 Signed-off-by: yuanke wei <weiyuanke123@gmail.com>
|
Hey folks! Any updates on this fix? I’m trying to install the latest release (0.7.13) and I’m still running into the same issue. 😕 |
oci artifacts seems ok, |
|
Hi @weiyuanke, Im having the same issue you are having but with the newest release: e.g., ServiceAccount "kagent-kagent-controller" is invalid: metadata.labels: Invalid value: "0.7.13+6030c268d3c0": a valid label must be an empty string or consist of alpha │ Im trying to see if the code owners have any news or schedule to merge your fix or something similar. ps: Im using Flux, and Flux CRD OCIRepository appends build metadata (short SHA256 digest) to Helm chart versions, so a tag like 0.7.13 becomes 0.7.13+6030c268d3c0 and ends up as .Chart.Version. |
|
I am able to install as well, so this must specifically be related to |
|
Yes, this is Flux-specific. The agentgateway chart sets: app.kubernetes.io/version: {{ .Chart.AppVersion | quote }} but this chart sets: app.kubernetes.io/version: {{ .Chart.Version | quote }} The pattern used in the agentgateway chart is to:
Example from agentgateway (_helpers.tpl): {{- define "agentgateway.chart" -}} {{- define "agentgateway.labels" -}} So a simpler fix might be to just follow the pattern of using AppVersion instead of Version. I have kgateway on my cluster, which uses the same fix/pattern as agentgateway so this is what the labels look like: Labels: app.kubernetes.io/instance=kgateway-system-kgateway |
|
That makes sense to me |
#1188