search

jenkins-x / jx

Jenkins X provides automated CI+CD for Kubernetes with Preview Environments on Pull Requests using Cloud Native pipelines from Tekton
https://jenkins-x.io/
Apache License 2.0
4.58k stars 788 forks source link

jx boot for on-premise kubernetes #6741

Closed arfiqbal closed 3 years ago

arfiqbal commented 4 years ago

How do i use jx boot for on-premise kubernetes

Below is my jx-requirements.yml `autoUpdate: enabled: false schedule: "" bootConfigURL: https://mygithub-enterprise.com/githubadmin/jenkins-x-boot-config cluster: gitKind: github gitName: github gitServer: https://mygithub-enterprise.com namespace: jenkinsx project: jenkinsx provider: kubernetes environments:

STEP: validate-git command: /bin/sh -c jx step git validate in dir: /home/arif/jenkins-x-boot-config/env

Git configured for user: arif and email arf.@xxx.com

STEP: verify-preinstall command: /bin/sh -c jx step verify preinstall --provider-values-dir="kubeProviders" in dir: /home/arif/jenkins-x-boot-config

jx boot has only been validated on GKE and EKS, we'd love feedback and contributions for other Kubernetes providers `

jx version

NAME VERSION jx 2.0.1180 jenkins x platform 2.0.1965 Kubernetes cluster v1.16.6 kubectl v1.16.0 helm client Client: v2.12.2+g7d2b0c7 git 2.17.1 Operating System Ubuntu 18.04.3 LTS

ankitm123 commented 4 years ago

I tried jx boot on Linode Kubernetes Engine, which is basically on-prem as far as jx is concerned, and it worked. You just need to continue, after you get that message (jx boot has only been validated on GKE and EKS, we'd love feedback and contributions for other Kubernetes providers). What is the error message you are seeing? @arfiqbal

ravenchilde commented 4 years ago

@arfiqbal - I'm using it on an on-prem install on VMs using RHEL7.5 (Kubernetes 1.16.6), and it works fine except it won't accept or add CA for self-signed certs for Bitbucket Server.

2020testuser commented 4 years ago

Is this issue resolved? I also ran into self-signed certs error. Any info. would be very useful.

infa-ddeore commented 4 years ago

is there an jx install --on-premise equivalent option in jx-requirements.yml ?

jx boot fails on minukube while waiting on external ingress, there is an option to use jx install command instead with --on-premise but document comes under deprecated section.

STEP: create-install-values command: /bin/sh -c jx step create install values -b in dir: /Users/test/tmp/tekton/jenkins-x-boot-config/env

Waiting to find the external host name of the ingress controller Service in namespace kube-system with name jxing-nginx-ingress-controller
If you are installing Jenkins X on premise you may want to use the '--on-premise' flag or specify the '--external-ip' flags. See: https://jenkins-x.io/getting-started/install-on-cluster/#installing-jenkins-x-on-premise
No domain flag provided so using default  to generate Ingress rules
waiting for external Host on the ingress service jxing-nginx-ingress-controller in namespace kube-system ...
error: failed to discover the Ingress domain: getting a domain for ingress service kube-system/jxing-nginx-ingress-controller: Timed out after 5m0s, last error: %!s(<nil>)
error: failed to interpret pipeline file jenkins-x.yml: failed to run '/bin/sh -c jx step create install values -b' command in directory 'env', output: ''

jx install gives deprecated warning

$ jx install --on-premise --provider=kubernetes
Command "install" is deprecated, it will be removed on Sep 1 2020. We now highly recommend you use jx boot instead. Please check https://jenkins-x.io/docs/getting-started/setup/boot/ for more details.
? Configured Jenkins installation type: Serverless Jenkins X Pipelines with Tekton
jenkins-x-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

ravenchilde commented 4 years ago

Fixed by installing gitlab. /close

On Sat, Oct 10, 2020 at 12:00 AM jenkins-x-bot notifications@github.com wrote:

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jenkins-x/jx/issues/6741#issuecomment-706494058, or unsubscribe https://github.com/notifications/unsubscribe-auth/AETUNTHZU2ZC5R3KBWVZID3SJ7Z67ANCNFSM4KUPELUQ .

jenkins-x-bot commented 3 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle rotten

jenkins-x-bot commented 3 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten. Provide feedback via https://jenkins-x.io/community. /close

jenkins-x-bot commented 3 years ago

@jenkins-x-bot: Closing this issue.

In response to [this](https://github.com/jenkins-x/jx/issues/6741#issuecomment-747174018): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. >Provide feedback via https://jenkins-x.io/community. >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [jenkins-x/lighthouse](https://github.com/jenkins-x/lighthouse/issues/new?title=Command%20issue:) repository.