gistfile1.txt

[hekonsek@konsekranch jx]$ jx install --provider=eks
Using helmBinary helm with feature flag: none
Storing the kubernetes provider eks in the TeamSettings
Updated the team settings in namespace jx
Git configured for user: Henryk Konsek and email [email protected]
Trying to create ClusterRoleBinding henryk-konsek-capsilon-com-adorable-hideout-1539079578-us-east-1-eksctl-io-cluster-admin-binding for role: cluster-admin for user [email protected]@adorable-hideout-1539079578.us-east-1.eksctl.io
: clusterrolebindings.rbac.authorization.k8s.io "henryk-konsek-capsilon-com-adorable-hideout-1539079578-us-east-1-eksctl-io-cluster-admin-binding" not foundCreated ClusterRoleBinding henryk-konsek-capsilon-com-adorable-hideout-1539079578-us-east-1-eksctl-io-cluster-admin-binding
Using helm2
Configuring tiller
Created ServiceAccount tiller in namespace kube-system
Trying to create ClusterRoleBinding tiller for role: cluster-admin and ServiceAccount: kube-system/tiller
Created ClusterRoleBinding tiller
Initialising helm using ServiceAccount tiller in namespace kube-system
Using helmBinary helm with feature flag: none
helm installed and configured
? No existing ingress controller found in the kube-system namespace, shall we install one? Yes
Using helm values file: /tmp/ing-values-419545241
Installing using helm binary: helm
Waiting for external loadbalancer to be created and update the nginx-ingress-controller service in kube-system namespace
External loadbalancer created
Waiting to find the external host name of the ingress controller Service in namespace kube-system with name jxing-nginx-ingress-controller

On AWS we recommend using a custom DNS name to access services in your Kubernetes cluster to ensure you can use all of your Availability Zones
If you do not have a custom DNS name you can use yet you can register a new one here: https://console.aws.amazon.com/route53/home?#DomainRegistration:

? Would you like to register a wildcard DNS ALIAS to point at this ELB address?  Yes

? Your custom DNS name:  [? for help] 
? Would you like to register a wildcard DNS ALIAS to point at this ELB address?  No

The Ingress address a6f5e6b78cbad11e8af3c023aba6eb8a-a96d1b2f50ddad96.elb.us-east-1.amazonaws.com is not an IP address. We recommend we try resolve it to a public IP address and use that for the domain to access services externally.
? Would you like wait and resolve this address to an IP address and use it for the domain? Yes

Waiting for a6f5e6b78cbad11e8af3c023aba6eb8a-a96d1b2f50ddad96.elb.us-east-1.amazonaws.com to be resolvable to an IP address...
retrying after error: Address cannot be resolved yet a6f5e6b78cbad11e8af3c023aba6eb8a-a96d1b2f50ddad96.elb.us-east-1.amazonaws.com
...
a6f5e6b78cbad11e8af3c023aba6eb8a-a96d1b2f50ddad96.elb.us-east-1.amazonaws.com resolved to IP 54.156.140.112
You can now configure a wildcard DNS pointing to the new loadbalancer address 54.156.140.112

If you do not have a custom domain setup yet, Ingress rules will be set for magic dns nip.io.
Once you have a customer domain ready, you can update with the command jx upgrade ingress --cluster
If you don't have a wildcard DNS setup then setup a new CNAME and point it at: 54.156.140.112.nip.io then use the DNS domain in the next input...
? Domain 54.156.140.112.nip.io
nginx ingress controller installed and configured
Lets set up a Git username and API token to be able to perform CI/CD

? Do you wish to use hekonsek as the GitHub username for CI/CD pipelines: Yes
Cloning the Jenkins X cloud environments repo to /home/hekonsek/.jx/cloud-environments
? A local Jenkins X cloud environments repository already exists, recreate with latest? Yes
Cloning the Jenkins X cloud environments repo to /home/hekonsek/.jx/cloud-environments
Enumerating objects: 44, done.
Counting objects: 100% (44/44), done.
Compressing objects: 100% (32/32), done.
Total 1001 (delta 19), reused 33 (delta 12), pack-reused 957
Generated helm values /home/hekonsek/.jx/extraValues.yaml
Installing Jenkins X platform helm chart from: /home/hekonsek/.jx/cloud-environments/env-eks
Installing jx into namespace jx
waiting for install to be ready, if this is the first time then it will take a while to download images
Jenkins X deployments ready in namespace jx

	
	********************************************************
	
	     NOTE: Your admin password is: thumbseed
	
	********************************************************
	
	
Getting Jenkins API Token
Using url http://jenkins.jx.54.156.140.112.nip.io/me/configure
2018/10/09 12:30:06 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:06 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:06 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:06 error: could not perform (childNodeInserted) operation on node 15 (wait node): timeout waiting for node `15`
2018/10/09 12:30:06 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:06 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:06 error: could not perform (childNodeRemoved) operation on node 15 (wait node): timeout waiting for node `15`
2018/10/09 12:30:06 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:06 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:06 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:06 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 18 (wait node): timeout waiting for node `18`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 18 (wait node): timeout waiting for node `18`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 16 (wait node): timeout waiting for node `16`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 18 (wait node): timeout waiting for node `18`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 18 (wait node): timeout waiting for node `18`
2018/10/09 12:30:07 error: could not perform (childNodeCountUpdated) operation on node 18 (wait node): timeout waiting for node `18`
logging in
Getting the API Token...
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 82 (wait node): timeout waiting for node `82`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 82 (wait node): timeout waiting for node `82`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeRemoved) operation on node 79 (wait node): timeout waiting for node `79`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeInserted) operation on node 79 (wait node): timeout waiting for node `79`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 80 (wait node): timeout waiting for node `80`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 82 (wait node): timeout waiting for node `82`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 82 (wait node): timeout waiting for node `82`
2018/10/09 12:30:19 error: could not perform (childNodeCountUpdated) operation on node 82 (wait node): timeout waiting for node `82`
Found API Token
Created user admin API Token for Jenkins server jenkins.jx.54.156.140.112.nip.io at http://jenkins.jx.54.156.140.112.nip.io
Updating Jenkins with new external URL details http://jenkins.jx.54.156.140.112.nip.io
Creating default staging and production environments
Using Git provider GitHub at https://github.com


About to create repository environment-scowlmica-staging on server https://github.com with user hekonsek


Creating repository hekonsek/environment-scowlmica-staging
Creating Git repository hekonsek/environment-scowlmica-staging
Pushed Git repository to https://github.com/hekonsek/environment-scowlmica-staging

Created environment staging
Created Jenkins Project: http://jenkins.jx.54.156.140.112.nip.io/job/hekonsek/job/environment-scowlmica-staging/

Note that your first pipeline may take a few minutes to start while the necessary images get downloaded!

Creating GitHub webhook for hekonsek/environment-scowlmica-staging for url http://jenkins.jx.54.156.140.112.nip.io/github-webhook/
Using Git provider GitHub at https://github.com


About to create repository environment-scowlmica-production on server https://github.com with user hekonsek


Creating repository hekonsek/environment-scowlmica-production
Creating Git repository hekonsek/environment-scowlmica-production
Pushed Git repository to https://github.com/hekonsek/environment-scowlmica-production

Created environment production
Created Jenkins Project: http://jenkins.jx.54.156.140.112.nip.io/job/hekonsek/job/environment-scowlmica-production/

Note that your first pipeline may take a few minutes to start while the necessary images get downloaded!

Creating GitHub webhook for hekonsek/environment-scowlmica-production for url http://jenkins.jx.54.156.140.112.nip.io/github-webhook/

Jenkins X installation completed successfully

	
	********************************************************
	
	     NOTE: Your admin password is: thumbseed
	
	********************************************************
	
	

Your Kubernetes context is now set to the namespace: jx 
To switch back to your original namespace use: jx ns default
For help on switching contexts see: https://jenkins-x.io/developing/kube-context/

To import existing projects into Jenkins:       jx import
To create a new Spring Boot microservice:       jx create spring -d web -d actuator
To create a new microservice from a quickstart: jx create quickstart