How to resolve "Error: repository not found" error while deploying konvoy
Konvoy delivers a Day 2 ready cluster by installing various addons in the kubernetes cluster. These addons are distributed using addon repos. Addon repos are git repositories that contain the definition for various addons in the repo. Various addon repos are configured for a Konvoy cluster under the
addons section of
ClusterConfiguration. Path to these addon repos is specified by the
configRepository field. This article covers various scenarios that can lead to the "Error: repository not found".
There are a few possible scenarios that can result in "Error: repository not found". All of these scenarios are related to airgapped install method where addon repos are accessed locally from disk as the nodes cannot reach out to the internet to access addon repos hosted on Github. We will go over how to check for there scenarios and how to resolve the issue.
Addon repo directory does not exist
The path containing the
konvoy binary is mounted into the docker container launched by Konvoy, at the location
/opt/konvoy/artifcats. To use local directory based addon repos make sure that the directory for the addon repo exists in the same directory as
konvoy binary and
configRepository field is set to
/opt/konvoy/artifacts/ For example if your
konvoy binary lives in and is launched from
/home/alice/my-clusterthen make sure your addon directory
my-addon-repo exists under
configRepository is set to
If the addon directory is not present on the machine you running Konvoy from, then use a machine that has access to the addon git repo to clone the repo and copy it over. For the default Konvoy addon repos you can find the addon repos in the airgapped release bundle.
Addon repo exists but not a git repo
The addon repo directory used by Konvoy is supposed to be a git repo. If directory exists and is a git repo and you are still getting the "Error: repository not found" error make sure the following checks succeed: 1) make sure that the tag specified by
configVersion for the addon repo field exists (
git tag -l) 2) make sure the
master branch is currently checked out (
git branch -v)