-
Notifications
You must be signed in to change notification settings - Fork 37
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
Run agents with separate service account and in their own (project specific) namespaces #5
Milestone
Comments
mbarbero
added a commit
that referenced
this issue
Jun 25, 2020
…space Eventually, $.kubernetes.agent.namespace should be set to something different from $.kubernetes.master.namespace to run build jobs in separate namespace (see #5), but for now let's stick to same as parent. Signed-off-by: Mikaël Barbero <mikael.barbero@eclipse-foundation.org>
fredg02
pushed a commit
that referenced
this issue
Jun 25, 2020
…space Eventually, $.kubernetes.agent.namespace should be set to something different from $.kubernetes.master.namespace to run build jobs in separate namespace (see #5), but for now let's stick to same as parent. Signed-off-by: Mikaël Barbero <mikael.barbero@eclipse-foundation.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, agents are started in the same namespace and with the same service account as the master. It means several things that we would like to avoid:
The text was updated successfully, but these errors were encountered: