Allow registering an agent without a config file
Release notes
Problem to solve
As an Application Operator/Software engineer, I want to start using the GitLab Kubernetes Agent with minimal effort for my projects, using the CI tunnel, so I can focus on writing business code, instead of ops.
Definition of done
-
The agent should work with a default agent configuration when no agent configuration is available under .gitlab/agents/<agent-name>/config.yaml
-
This default configuration should enable project level CI/CD tunnel for the agent configuration project -
Registering a new agent should check that an agent with that name does not exist and the agent name can be used as a path segment. The registration should still work if a config file is present. -
Document how to get started with CI/CD tunnel without configuration -
KAS does not error when an agent has no config file - gitlab-org/cluster-integration/gitlab-agent!583 (merged)
Optional ideas
The agent details UI should provide a single-click to create an MR with the default configuration pre-filled (it should be easy to take ownership of the agent without changing the existing workflow)
- In the first iteration we could just have a description, show the default configuration as text and have a button to open the Web IDE.
Documentation
- Document the default setting
- Document how to take ownership of the configuration (by creating an agent config file)
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.