-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix app template #3
Conversation
30ac6ca
to
5c1beb2
Compare
110960c
to
54b745b
Compare
54b745b
to
87d18eb
Compare
I thought the idea was to integrate this app in another repo until we could put it back in collections under the Otherwise I'm also fine with this method |
Well yes this is the other repo :D |
I meant "integrate it in another existing repo" 😅 |
ah yes but if we did that then we would need to migrate the config :D |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine with me
application.giantswarm.io/branch: {{ .Chart.Annotations.branch | replace "#" "-" | replace "/" "-" | replace "." "-" | trunc 63 | trimSuffix "-" | quote }} | ||
application.giantswarm.io/commit: {{ .Chart.Annotations.commit | quote }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're removing a lot of stuff from the default template. Isn't it good practice to have them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commit and branch? We remove it from everywhere actually 😅
It looks like a bit more than a template fix 😅 It's quite hard to spot the differences between generated files and actual code/config. I haven't seen any config that would make this app act as a Otel / Prometheus / Loki gateway. Did I miss something? What happens when this is released? As it's pushed to collections it will be deployed to all CAPI MCs. Will it run or will it fail? Are there some related PRs for config? Also, could you link the source issue? |
So I forgot to link the main issue giantswarm/roadmap#3568 (comment) ... sorry about this. This application is deployed via collections so the config (to be) will be defined here https://github.com/giantswarm/shared-configs/blob/main/default/apps/alloy-gateway/configmap-values.yaml.template. When this app is released it will then be deployed to all CAPI MCs and it will work because I've tested it on grizzly. Once this is setup, we will be able to configure this properly. The real changes are in the helm directory, https://github.com/giantswarm/alloy-gateway-app/pull/3/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5 the rest is merely templating like github workflow |
@hervenicol let me know if you need more info or we can pair on it |
This PR removes the push to app collections to avoid a conflict with giantswarm/alloy-gateway-app#3
This PR removes the push to app collections to avoid a conflict with giantswarm/alloy-gateway-app#3
All right, by default it's not enabled and won't deploy any configmap or pod. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks, sorry about the confusion :( |
This PR:
Checklist
values.yaml
andvalues.schema.json
are valid.