test.bash

anoop@myMac ~ $ jx init
? Cloud Provider gke
Trying to create ClusterRoleBinding cluster-admin-cluster-admin-binding for role: cluster-admin for user cluster-admin
clusterrolebinding "cluster-admin-cluster-admin-binding" created
Created ClusterRoleBinding cluster-admin-cluster-admin-binding
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
$HELM_HOME has been configured at /Users/xxxx/.helm.

Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.

Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
Happy Helming!
$HELM_HOME has been configured at /Users/xxxx/.helm.

Tiller (the Helm server-side component) has been upgraded to the current version.
Happy Helming!
"jenkins-x" has been added to your repositories
helm installed and configured
remote: Counting objects: 8, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 8 (delta 6), reused 8 (delta 6), pack-reused 0
Unpacking objects: 100% (8/8), done.
From https://github.com/jenkins-x/draft-packs
   86d33ee..d1efc13  master     -> origin/master
Updating 86d33ee..d1efc13
Fast-forward
 packs/appserver/.dockerignore                    |  5 +++++
 packs/appserver/.gitignore                       |  9 +++++++++
 packs/appserver/Dockerfile                       |  6 ++++++
 packs/appserver/Jenkinsfile                      | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 packs/appserver/charts/.helmignore               | 21 +++++++++++++++++++++
 packs/appserver/charts/Chart.yaml                |  5 +++++
 packs/appserver/charts/Makefile                  | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
 packs/appserver/charts/README.md                 |  1 +
 packs/appserver/charts/templates/NOTES.txt       |  4 ++++
 packs/appserver/charts/templates/_helpers.tpl    | 16 ++++++++++++++++
 packs/appserver/charts/templates/deployment.yaml | 39 +++++++++++++++++++++++++++++++++++++++
 packs/appserver/charts/templates/service.yaml    | 19 +++++++++++++++++++
 packs/appserver/charts/values.yaml               | 33 +++++++++++++++++++++++++++++++++
 packs/appserver/preview/Chart.yaml               |  5 +++++
 packs/appserver/preview/Makefile                 | 22 ++++++++++++++++++++++
 packs/appserver/preview/requirements.yaml        | 13 +++++++++++++
 packs/appserver/preview/values.yaml              | 22 ++++++++++++++++++++++
 packs/appserver/skaffold.yaml                    | 14 ++++++++++++++
 packs/liberty/Dockerfile                         |  2 +-
 19 files changed, 375 insertions(+), 1 deletion(-)
 create mode 100644 packs/appserver/.dockerignore
 create mode 100644 packs/appserver/.gitignore
 create mode 100644 packs/appserver/Dockerfile
 create mode 100644 packs/appserver/Jenkinsfile
 create mode 100644 packs/appserver/charts/.helmignore
 create mode 100644 packs/appserver/charts/Chart.yaml
 create mode 100644 packs/appserver/charts/Makefile
 create mode 100644 packs/appserver/charts/README.md
 create mode 100644 packs/appserver/charts/templates/NOTES.txt
 create mode 100644 packs/appserver/charts/templates/_helpers.tpl
 create mode 100644 packs/appserver/charts/templates/deployment.yaml
 create mode 100644 packs/appserver/charts/templates/service.yaml
 create mode 100644 packs/appserver/charts/values.yaml
 create mode 100644 packs/appserver/preview/Chart.yaml
 create mode 100755 packs/appserver/preview/Makefile
 create mode 100644 packs/appserver/preview/requirements.yaml
 create mode 100644 packs/appserver/preview/values.yaml
? No existing ingress controller found in the kube-system namespace, shall we install one? Yes
NAME:   jxing ingress controller found in the kube-system namespace, shall we install one? [? for help] (Y/n)
LAST DEPLOYED: Sat Apr 28 07:54:55 2018
NAMESPACE: kube-system
STATUS: DEPLOYED

RESOURCES:
==> v1beta1/PodDisruptionBudget
NAME                                 MIN AVAILABLE  MAX UNAVAILABLE  ALLOWED DISRUPTIONS  AGE
jxing-nginx-ingress-controller       1              N/A              0                    1s
jxing-nginx-ingress-default-backend  1              N/A              0                    1s

==> v1beta1/ClusterRole
NAME                 AGE
jxing-nginx-ingress  1s

==> v1/Service
NAME                                 TYPE          CLUSTER-IP    EXTERNAL-IP  PORT(S)                     AGE
jxing-nginx-ingress-controller       LoadBalancer  10.51.242.85  <pending>    80:31365/TCP,443:30449/TCP  1s
jxing-nginx-ingress-default-backend  ClusterIP     10.51.255.70  <none>       80/TCP                      1s

==> v1beta1/Deployment
NAME                                 DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
jxing-nginx-ingress-controller       1        1        1           0          1s
jxing-nginx-ingress-default-backend  1        1        1           0          1s

==> v1beta1/Role
NAME                 AGE
jxing-nginx-ingress  1s

==> v1beta1/RoleBinding
NAME                 AGE
jxing-nginx-ingress  1s

==> v1/Pod(related)
NAME                                                  READY  STATUS             RESTARTS  AGE
jxing-nginx-ingress-controller-d559f4497-9snqc        0/1    ContainerCreating  0         1s
jxing-nginx-ingress-default-backend-6f4ff5fcbc-w7prt  0/1    ContainerCreating  0         1s

==> v1/ConfigMap
NAME                            DATA  AGE
jxing-nginx-ingress-controller  1     1s

==> v1/ServiceAccount
NAME                 SECRETS  AGE
jxing-nginx-ingress  1        1s

==> v1beta1/ClusterRoleBinding
NAME                 AGE
jxing-nginx-ingress  1s


NOTES:
The nginx-ingress controller has been installed.
It may take a few minutes for the LoadBalancer IP to be available.
You can watch the status by running 'kubectl --namespace kube-system get services -o wide -w jxing-nginx-ingress-controller'

An example Ingress that makes use of the controller:


    server: https://35.204.17.194

  apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    annotations:
      kubernetes.io/ingress.class: nginx
    name: example
    namespace: foo
  spec:
    rules:
      - host: www.example.com
        http:
          paths:
            - backend:
                serviceName: exampleService
                servicePort: 80
              path: /
    # This section is only required if TLS is to be enabled for the Ingress
    tls:
        - hosts:
            - www.example.com
          secretName: example-tls

If TLS is enabled for the Ingress, a Secret containing the certificate and key must also be provided:

  apiVersion: v1
  kind: Secret
  metadata:
    name: example-tls
    namespace: foo
  data:
    tls.crt: <base64 encoded cert>
    tls.key: <base64 encoded key>
  type: kubernetes.io/tls

Waiting for external loadbalancer to be created and update the nginx-ingress-controller service in kube-system namespace
Note: this loadbalancer will fail to be provisioned if you have insufficient quotas, this can happen easily on a GKE free account. To view quotas run: gcloud compute project-info describe
External loadbalancer created
? Domain 35.204.17.80.nip.io
nginx ingress controller installed and configured
anoop@myMac ~ $