Your configuration refers to a file that is local on your system, but does not exist on the jenkins server. The error message is trying to tell you this. /c/Users/D35N/Downloads/GitHubProjeckt/Automation/GitHubProjeckt/newharbortestkey is not on the jenkins server. You need to make this file available on the jenkins server by copying it up there, and it ...
Modern way to achieve seamless roll-out in this scenario is not on the load balancing (i.e. haproxy) side, but instead via proper deployment planning, backward compatibility and/or feature flags.
The issue with load-balancer tinkering is that in the end of day even if you get sticky sessions right it's not going to solve your problem. The reason for that - ...
Just to clarify if I got you right.
Do you want to have a separate service for every pod/replica in your statefulSet?
If so - this is not how K8s sees services being used. The service is used for grouping and load balancing purposes.
In your case, if you want to have 1-on-1 connection between an external client and a pod, I suggest deploying your statefulSet ...
For anyone came here to solve this problem without any workarounds - the solution is simple.
We need to add switch --cache to the kubeconfig for a user used to access a Kubernetes cluster.
- name: <redacted>
Taking the url from cluster-info and creating a config file with jenkins and using at as secret did the trick to pass the connection.
I am still curious how to authenticate with a bearer token though. I have tried to use existing managed Jenkins secret, but it failed with it.
Update: The authentication happens, but after creating pods the job never runs.