JenkinsX Install using jx boot

2020testuser commented 4 years ago

Hi, I've been trying to get JenkinsX installed in an on-prem Kubernetes cluster. I tried to modify the jx-requirements.yaml to get JenkinsX install successful. But, no luck so far.

If anyone got JenkinsX insalled successfully in on-prem Kubernetes, could you please share the install steps and jx-requirements.yaml (with sensitive info. replaced with dummy values)? Thanks,

havenqi commented 4 years ago

Try this, jx successfully installed

autoUpdate:
  enabled: false
  schedule: ""
bootConfigURL: https://github.com/xxx/jenkins-x-boot-config
cluster:
  clusterName: tf-jx-evolving-x
  devEnvApprovers:
  - xxx
  environmentGitOwner: My-org
  gitKind: github
  gitName: github
  gitServer: https://github.com
  namespace: jx
  provider: eks
  region: us-east-1
  registry: .dkr.ecr.us-east-1.amazonaws.com
environments:
- ingress:
    domain: 0.0.0.0.nip.io
    externalDNS: false
    ignoreLoadBalancer: true
    namespaceSubDomain: -jx.
    tls:
      email: ""
      enabled: false
      production: false
  key: dev
  repository: environment-tf-jx-evolving-x-dev
- ingress:
    domain: ""
    externalDNS: false
    namespaceSubDomain: ""
    tls:
      email: ""
      enabled: false
      production: false
  key: staging
  repository: environment-tf-jx-evolving-x-staging
- ingress:
    domain: ""
    externalDNS: false
    namespaceSubDomain: ""
    tls:
      email: ""
      enabled: false
      production: false
  key: production
  repository: environment-tf-jx-evolving-x-production
gitops: true
ingress:
  domain: 0.0.0.0.nip.io
  externalDNS: false
  ignoreLoadBalancer: true
  namespaceSubDomain: -jx.
  tls:
    email: ""
    enabled: false
    production: false
kaniko: true
repository: nexus
secretStorage: vault
storage:
  backup:
    enabled: false
    url: ""
  logs:
    enabled: true
    url: s3://logs-tf-jx-evolving-x-x
  reports:
    enabled: true
    url: s3://reports-tf-jx-evolving-x-x
  repository:
    enabled: true
    url: s3://repository-tf-jx-evolving-x-x
terraform: true
vault:
  aws:
    dynamoDBRegion: us-east-1
    dynamoDBTable: vault-unseal-tf-jx-evolving-x-x
    kmsKeyId: 189bd97d-x-4873-8d82-x
    kmsRegion: us-east-1
    s3Bucket: vault-unseal-tf-jx-evolving-x-x
    s3Region: us-east-1
velero:
  schedule: ""
  ttl: ""
versionStream:
  ref: v1.0.492
  url: https://github.com/jenkins-x/jenkins-x-versions.git
webhook: lighthouse

2020testuser commented 4 years ago

@havenqi - Thanks! I'm using kubernetes provider (on-prem) and the above yaml uses 'eks'. Could you please let me know whether this has been tested for on-prem? Thanks!

deanesmith commented 4 years ago

Hi @2020testuser, Take a look at the current state of the Jenkins X Capabilities Matrix. OpenShift will work reasonably on-prem but the docs are fully in order yet. For other on-prem solutions you are on your own right now but there are indeed people who are doing it. jx install instead of boot might help, but it will be deprecated eventually in favor of boot.

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

jenkins-x-bot commented 4 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/7305#issuecomment-723581710): >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.

jenkins-x / jx

JenkinsX Install using jx boot #7305