Hi,

You may use SAML Single Sign On (SSO) plugin with keyclock or your cloud
provider authentication service.

Regardes,

Arnaud

Le mer. 9 nov. 2022, 06:12, Felipe Silveira <felipe.silve...@farfetch.com>
a écrit :

> Hi folks!
>
> I have a big Jenkins setup today at work (over 3k jobs, with a minimum of
> of 1k+ builds a day) -- we use Kubernetes plugins for managed clouds and
> that works quite well. Even though we have zero executors on the
> controller, I'm afraid we'll soon have performance issues on the
> controller. First thing that came to mind was scaling-out, by splitting the
> load among multiple controllers.
>
> I have everything automated with JCasC and ArgoCD, so spinning new
> controllers is not a problem, as they can be dynamically created using Argo
> ApplicationSets, where each new controllers is made available through
> different URL's, by using different ingress paths/prefix, for example:
>
> https://myjenkinsinstnace.io/business-unit-a
> https://myjenkinsinstnace.io/business-unit-b
> https://myjenkinsinstnace.io/business-unit-c
> https://myjenkinsinstnace.io/business-unit-[...]
>
> Even though everything works well, its still be a pain for users having to
> re-login every time they hop around the different instances... is there any
> way I could make their session to persist between the different instances?
>
> I've tried tweaking around Nginx controller settings and using
> reverse-proxy-auth-plugin, but so far without much luck.
>
> Would appreciate any insights!
>
> Thanks in advance,
> Felipe Silveira
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/ea6baa63-e1fe-4857-88c8-93b1f52e9cb7n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/ea6baa63-e1fe-4857-88c8-93b1f52e9cb7n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAESUf_BD-roaVwHh%3D7g%3DPrw7LkcdT8uhR7mBWGx6GkMSTz5odg%40mail.gmail.com.

Reply via email to