Replace this template with your information
Describe your question in as much detail as possible:
-
What are you seeing, and how does that differ from what you expect to see?
My usecase is that I want to have one agent only to run pipelines for all my projects. The hierrachy is GROUP > SUBGROUP[1…n] > projects. I have placed myconfig.yamlingroup/subgroup1/config_repo. My.gitlab-ci.yamlis placed ingroup/subgroup1/my_repo
I registered the Gitlab agent successfully in the project group/subgroup1/config_repo and I can see it accepted the configurations.
I followed the official documentation for authorizing the agent to work with another project and met the only condition I could see, i.e.
“The Kubernetes projects must be in the same group hierarchy as the project where the agent’s configuration is.”
When I run the pipeline in group/subgroup1/my_repo, it returns this error.
But when I register an agent in the repo, it works as expected. Not sure what am doing wrong.
Also, am I supposed to register runners when I am using an agent?
-
What version are you on? Are you using self-managed or GitLab.com?
Using Gitlab.com -
Add the CI configuration from
.gitlab-ci.ymland other configuration if relevant (e.g. docker-compose.yml)
.gitlab-ci.yaml
test:
image:
name: bitnami/kubectl:latest
entrypoint: [""]
script:
- kubectl config get-contexts
- kubectl config use-context group/subgroup1/config_repo:my_agent
- kubectl get pods -A
.gitlab/agents/agent/config.yaml
ci_access:
# This agent is accessible from CI jobs in projects in these groups
projects:
- id: oltranz-team/notification-domain/slackbot
observability:
logging:
level: debug
- What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?