-@gerrit:opendev.org- Felix Edel proposed: [zuul/zuul] 933710: Clean up old status page resources https://review.opendev.org/c/zuul/zuul/+/933710 | 09:52 | |
-@gerrit:opendev.org- Felix Edel proposed: [zuul/zuul] 933710: Clean up old status page resources https://review.opendev.org/c/zuul/zuul/+/933710 | 09:56 | |
-@gerrit:opendev.org- Ian Wienand proposed: [zuul/nodepool] 933717: func-test: make glean check more robust https://review.opendev.org/c/zuul/nodepool/+/933717 | 10:45 | |
@dfajfer:fsfe.org | > <@karlatec:matrix.org> Back again with a question that might be pretty basic for everyone, but... :) | 11:32 |
---|---|---|
> Can anyone advise how to configure Zuul when it's deployed in k8s cluster and using ingress controller for UI access? | ||
> | ||
> I have ClusterIP services for exposing both Gerrit and Zuul Web ports. That works fine. | ||
> I have an ingress controller with `/` path for Gerrit - works fine. I want to access Zuul UI using `/zuul` path but when accessing `host.name.com/zuul` in the browser I get a blank screen. Browser's `network` tab in developer tools section shows me 404 when trying to GET .js scripts, so I assume it has something to do with static\_path. | ||
> I've tried setting zuul.conf (and restarting the pod) like this: | ||
> | ||
> ``` | ||
> [web] | ||
> listen_address=0.0.0.0 | ||
> port=9000 | ||
> root=http://host.name.com/zuul | ||
> static_path=/usr/local/lib/python3.11/site-packages/zuul/web/static/ (this is where I found static elements using `find` in the zuul-web container itself) | ||
> ``` | ||
Karol: I have that setup (although using zuul-operator) but I'm returning to work starting on monday. If you're willing to wait I could guide you a bit I guess | ||
@dfajfer:fsfe.org | overall I never had any problems with it and I have several instances of zuul+gerrit | 11:32 |
@karlatec:matrix.org | Thanks Damian Fajfer ! I would definitely would like to take a look. | 11:44 |
I am kind of novice then it comes to deploying things using k8s + ingress. I was experimenting some more yesterday, and turns out I was doing it all wrong - trying to use Nginx Ingress while I was working with k3s which comes with Traefik Ingress Controllers. After changing to Traefik IngressRoutes things work more or less as I would expect them too. Ingress rules could probably be better, but at least it works :) | ||
Clark turns our `static_path` was not needed after all and it was a matter of creating additional ingress rules for `/static` and `/api` paths :) | ||
@karlatec:matrix.org | * Thanks Damian Fajfer ! I definitely would like to take a look. | 11:48 |
I am kind of novice then it comes to deploying things using k8s + ingress. I was experimenting some more yesterday, and turns out I was doing it all wrong - trying to use Nginx Ingress while I was working with k3s which comes with Traefik Ingress Controllers. After changing to Traefik IngressRoutes things work more or less as I would expect them too. Ingress rules could probably be better, but at least it works :) | ||
Clark turns our `static_path` was not needed after all and it was a matter of creating additional ingress rules for `/static` and `/api` paths :) | ||
-@gerrit:opendev.org- Slawek Kaplonski proposed: [zuul/zuul-jobs] 933395: Drop support for user/password authentication to the readthedocs.org https://review.opendev.org/c/zuul/zuul-jobs/+/933395 | 13:23 | |
-@gerrit:opendev.org- Clark Boylan proposed: [zuul/zuul-registry] 933759: Rebuild the zuul-registry container image https://review.opendev.org/c/zuul/zuul-registry/+/933759 | 16:26 | |
-@gerrit:opendev.org- Clark Boylan proposed: | 17:16 | |
- [zuul/zuul-registry] 933759: Rebuild the zuul-registry container image https://review.opendev.org/c/zuul/zuul-registry/+/933759 | ||
- [zuul/zuul-registry] 933764: Run image builds on noble https://review.opendev.org/c/zuul/zuul-registry/+/933764 | ||
-@gerrit:opendev.org- Clark Boylan proposed: | 17:37 | |
- [zuul/zuul-registry] 933764: Run image builds on noble https://review.opendev.org/c/zuul/zuul-registry/+/933764 | ||
- [zuul/zuul-registry] 933759: Rebuild the zuul-registry container image https://review.opendev.org/c/zuul/zuul-registry/+/933759 | ||
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: | 20:43 | |
- [zuul/nodepool] 933688: Summarize nodescan state machine log messages https://review.opendev.org/c/zuul/nodepool/+/933688 | ||
- [zuul/nodepool] 933689: Retry nodescan connections during the key phase https://review.opendev.org/c/zuul/nodepool/+/933689 | ||
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul-registry] 933787: Remove nodeset specifier from image jobs https://review.opendev.org/c/zuul/zuul-registry/+/933787 | 21:12 | |
@jim:acmegating.com | Clark: i approved your first change; i think the second is unecessary; and i made a followup ^ | 21:12 |
@clarkb:matrix.org | ya I realized after everything tested successfully that the second change is a noop since the first rebuilds the image too | 21:13 |
@clarkb:matrix.org | I abandoned it | 21:13 |
-@gerrit:opendev.org- Zuul merged on behalf of Clark Boylan: [zuul/zuul-registry] 933764: Run image builds on noble https://review.opendev.org/c/zuul/zuul-registry/+/933764 | 21:25 | |
-@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/zuul-registry] 933787: Remove nodeset specifier from image jobs https://review.opendev.org/c/zuul/zuul-registry/+/933787 | 22:01 | |
@clarkb:matrix.org | https://discuss.python.org/t/getting-rid-of-daemon-threads/68836/38 is maybe one day relevant to zuul though it seems like they are less motivated to make the chagne to remove daemon threads from python now | 23:46 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!