Only core-services/secrets folder is applied to the cluster api.ci.
Except user secret management, no services are running on api.ci.
OWNERS and README.md files. This is
enforced by make check locally and by the ci/prow/core-valid check on
pull requests.applyconfig
tool. The tool applies all YAML files under your service subdirectory. Subdirectories are searched recursively and directories with names starting with _ are skipped. All
YAML filenames should follow the following convention:
admin_*.yaml files_.applyconfig applies files in lexicographical order. In the case when some
resources need to be created before others, this needs to be reflected by the
naming of the files (e.g. by including a numerical component).config-updater service account in the ci namespace must have
permissions to apply all standard resources.config-updater Prow plugin.There are two types of configuration: resources and ConfigMaps.
config-updater Prow plugin,
configured in its config.yaml file.
Additionally, they are periodically
synced by a Prow job.make core, provided the user has rights
to perform all necessary actionsAdditionally, the applyconfig can be used directly.
See its README.md for more details.