jenkins-x-plugins / jenkins-x-plugins/jx-admin
job.batch/jx-boot fails to start Pods when Installing Git Operator on On-Premises K8S
- Dominant language
- Go
- Stars
- 6
- Forks
- 15
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
Please we're facing an issue when installing Git Operator using the < jx admin operator --username mygituser --token mygittoken> command on Onpremise Kubernetes cluster.
All the Pods are in Init:Error state with the following message:
_**WARNING: could not default pipeline user/email from requirements as file does not exist: jx-requirements.yml
setup git user email jenkins-x@googlegroups.com
generated Git credentials file: /workspace/xdg_config/git/credentials with username: *** email:
no custom git initialisation scripts
ran git init commands: echo 'no custom git initialisation scripts'
error: failed to git clone URL https://github.com/***/***.git to dir source: failed to clone repository https://github.com/***/***.git to directory: source: failed to run 'git clone https://github.com/***/***.git source' command in directory '.', output: 'Cloning into 'source'...
fatal: unable to access 'https://github.com/***/***.git/': Could not resolve host: github.com'**_
Contributor guide
Research direction
Start by reproducing the `jx admin operator --username mygituser --token mygittoken` installation on an on-premises Kubernetes cluster and inspect the failing Pods in `Init:Error`. Verify the reported inability to resolve `github.com` during the Git clone, then determine the project entry point or configuration responsible; done means the Git Operator installation can start its Pods and clone the repository successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100