0.7.0-rc1

Local Kyma installation

Use the following command to run Kubernetes locally via Minikube:
$ ./installation/scripts/minikube.sh --domain "kyma.local" --vm-driver "hyperkit"

Kyma installation requires increased permissions granted by the cluster-admin role. To bind the role to the default ServiceAccount, run the following command:
$ kubectl apply -f ./installation/resources/default-sa-rbac-role.yaml

Wait until the coredns Pod is ready. Run this script to setup Tiller:
$ ./installation/scripts/install-tiller.sh

Deploy Kyma Installer using the local installer file:
$ kubectl apply -f https://github.com/kyma-project/kyma/releases/download/0.7.0-rc1/kyma-installer-local.yaml

Configure the Kyma installation using the local configuration file:
$ kubectl apply -f https://github.com/kyma-project/kyma/releases/download/0.7.0-rc1/kyma-config-local.yaml

To trigger the installation process, label the kyma-installation custom resource:
$ kubectl label installation/kyma-installation action=install

Track progress of the installation using the following script:
$ ./installation/scripts/is-installed.sh

Installation on Google Kubernetes Engine

1. Make sure that you have gcloud tool installed. Set environment variables for your Google project identifier and your cluster name. You can keep your demo cluster name but your Google project identifier must be changed. Then you can spin up the cluster:

   export CLUSTER_NAME=demo
   export PROJECT=YOUR_PROJECT_ID
   
   gcloud beta container --project "$PROJECT" clusters \
   create "$CLUSTER_NAME" --zone "europe-west1-b" \
   --cluster-version "1.10.12" --machine-type "n1-standard-2" \
   --addons HorizontalPodAutoscaling,HttpLoadBalancing,KubernetesDashboard 
   

2. Install Tiller:

   kubectl apply -f https://raw.githubusercontent.com/kyma-project/kyma/0.7.0-rc1/installation/resources/tiller.yaml
   

3. Download the release and replace the placeholders with the proper values. The placeholders are the upper case variables surrounded by double underscore, such as __DOMAIN__. These are the mandatory values to change:

   • __DOMAIN__ which specifies your domain, for example kyma.example.com.
   • __TLS_CERT__ which is a PEM format, base64-encoded TLS certifcate.
   • __TLS_KEY__ which is a base64-encoded TLS private key.

   If you don't know how to set other values, replace them with an empty string.

   You can use this script to set only three mandatory values:

   export DOMAIN=kyma.example.com
   export TLS_CERT=base64_PEM_TLS_certificate
   export TLS_KEY=base64_TLS_private_key
   cat kyma-config-cluster.yaml | sed -e "s/__DOMAIN__/$DOMAIN/g" |sed -e "s/__TLS_CERT__/$TLS_CERT/g" | sed -e "s/__TLS_KEY__/$TLS_KEY/g" |sed -e "s/__.*__//g" >my-kyma.yaml
   

   As a result, you get the my-kyma.yaml file which you can deploy on the GKE cluster.

4. Configure kubectl to use your new cluster, add yourself as the cluster admin, and deploy Kyma installer with your configuration.

   gcloud container clusters get-credentials $CLUSTER_NAME --zone europe-west1-b --project $PROJECT
   
   kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account)
   
   kc apply -f https://github.com/kyma-project/kyma/releases/download/0.7.0-rc1/kyma-installer-cluster.yaml
   
   kubectl apply -f my-kyma.yaml
   

5. Check if tiller and kyma-installer Pods are up and running. Start the installation process with this command:

   kubectl label installation/kyma-installation action=install
   

   Watch installation progress:

   kubectl logs -n kyma-installer [kyma-installer-pod] -f
   

6. Configure DNS for two load balancers created by the Kyma installation, which are istio-ingressgateway and core-nginx-ingress-controller. You need the following DNS records:

   • *.kyma.example.com A EXTERNAL_PUBLIC_IP
   • gateway.kyma.example.com A REMOTE_ENV_IP

   You can use this script to get external IP addresses for load balancers:

   export EXTERNAL_PUBLIC_IP=$(kubectl get service -n istio-system istio-ingressgateway -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   export REMOTE_ENV_IP=$(kubectl get service -n kyma-system application-connector-nginx-ingress-controller -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   gcloud dns --project=$PROJECT record-sets transaction start --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $EXTERNAL_PUBLIC_IP --name=\*.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $REMOTE_ENV_IP --name=\gateway.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction execute --zone=$DNS_ZONE
   
   

Read this document for more information on installing Kyma.

0.7.0-rc1 (2019-02-11)

Application Connector

• #2645 Split Application Connector certificates secret (@Szymongib)
• #2468 Adjust Connector Service chart to API changes (@Szymongib)
• #2620 Document securing APIs with generated client cert. (@tomekpapiernik)
• #2465 Add Application header to Connector Service call (@Szymongib)
• #2389 Connector Service API upgrade (@Szymongib)
• #2575 Fix broken diagram links for Application Broker (@tomekpapiernik)
• #2561 Update application-operator image version (@montaro)
• #2556 Move the Application Broker documentation to the Application Connector topic (@klaudiagrz)
• #2543 Update Application Registry API spec (@Szymongib)
• #2474 Bump image of Lambda UI (@Szymongib)
• #2446 Generate clientset for Token Request CRD (@janmedrek)
• #2423 Update "Get the client certificate" tutorial (@tomekpapiernik)
• #2424 Increasing memory limit for size of the body in Application Registry (@lszymik)
• #2412 Increasing memory limit for size of the body in Application Registry (@lszymik)
• #2405 Bump application proxy version (@lszymik)
• #2339 Bump ui-api-layer and console images (@franpog859)
• #2328 Rename environments to namespaces in ui-api-layer under Application domain (@franpog859)
• #2386 Fixing the constance variable for basic auth (@lszymik)
• #2396 Rename outstanding items from "remote env." to "application" renaming (@tomekpapiernik)
• #2357 Update filenames to use new numbering format (@tomekpapiernik)
• #2383 Fix proxy certs in scratch image - image bump (@crabtree)
• #2327 Set sidecar injection annotations to false in Application Connector charts (@kfurgol)
• #2382 Fix proxy certs in scratch image (@crabtree)
• #2352 Bump images of Application Registry and Application Proxy (@Szymongib)
• #2335 Add certificates authorization to Application Connector (@Szymongib)
• #2275 Application Connector components hardening - bump (@crabtree)
• #2264 Application Connector components hardening (@crabtree)
• #2307 Bump image of Application Registry (@Szymongib)
• #2306 Fix adding connected app label (@Szymongib)
• #2227 Bump application-connector-tests and acceptance-tests images (@franpog859)
• #2241 Fix image name of Application Operator tests ([@Szymongib](https://github.c...

0.6.1

Local Kyma installation

Use the following command to run Kubernetes locally via Minikube:
$ ./installation/scripts/minikube.sh --domain "kyma.local" --vm-driver "hyperkit"

Kyma installation requires increased permissions granted by the cluster-admin role. To bind the role to the default ServiceAccount, run the following command:
$ kubectl apply -f ./installation/resources/default-sa-rbac-role.yaml

Wait until the kube-dns Pod is ready. Run this script to setup Tiller:
$ ./installation/scripts/install-tiller.sh

Configure the Kyma installation using the local configuration file:
$ kubectl apply -f https://github.com/kyma-project/kyma/releases/download/0.6.1/kyma-config-local.yaml

To trigger the installation process, label the kyma-installation custom resource:
$ kubectl label installation/kyma-installation action=install

Track progress of the installation using the following script:
$ ./installation/scripts/is-installed.sh

Installation on Google Kubernetes Engine

1. Make sure that you have gcloud tool installed. Set environment variables for your Google project identifier and your cluster name. You can keep your demo cluster name but your Google project identifier must be changed. Then you can spin up the cluster:

   export CLUSTER_NAME=demo
   export PROJECT=YOUR_PROJECT_ID
   
   gcloud beta container --project "$PROJECT" clusters \
   create "$CLUSTER_NAME" --zone "europe-west1-b" \
   --cluster-version "1.10.7" --machine-type "n1-standard-2" \
   --addons HorizontalPodAutoscaling,HttpLoadBalancing,KubernetesDashboard 
   

2. Install Tiller:

   kubectl apply -f https://raw.githubusercontent.com/kyma-project/kyma/0.6.1/installation/resources/tiller.yaml
   

3. Download the release and replace the placeholders with the proper values. The placeholders are the upper case variables surrounded by double underscore, such as __DOMAIN__. These are the mandatory values to change:

   • __DOMAIN__ which specifies your domain, for example kyma.example.com.
   • __TLS_CERT__ which is a PEM format, base64-encoded TLS certifcate.
   • __TLS_KEY__ which is a base64-encoded TLS private key.

   If you don't know how to set other values, replace them with an empty string.

   You can use this script to set only three mandatory values:

   export DOMAIN=kyma.example.com
   export TLS_CERT=base64_PEM_TLS_certificate
   export TLS_KEY=base64_TLS_private_key
   cat kyma-config-cluster.yaml | sed -e "s/__DOMAIN__/$DOMAIN/g" |sed -e "s/__TLS_CERT__/$TLS_CERT/g" | sed -e "s/__TLS_KEY__/$TLS_KEY/g" |sed -e "s/__.*__//g" >my-kyma.yaml
   

   As a result, you get the my-kyma.yaml file which you can deploy on the GKE cluster.

4. Configure kubectl to use your new cluster, add yourself as the cluster admin, and deploy Kyma installer with your configuration.

   gcloud container clusters get-credentials $CLUSTER_NAME --zone europe-west1-b --project $PROJECT
   
   kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account)
   
   kubectl apply -f my-kyma.yaml
   

5. Check if tiller and kyma-installer Pods are up and running. Start the installation process with this command:

   kubectl label installation/kyma-installation action=install
   

   Watch installation progress:

   kubectl logs -n kyma-installer [kyma-installer-pod] -f
   

6. Configure DNS for two load balancers created by the Kyma installation, which are istio-ingressgateway and core-nginx-ingress-controller. You need the following DNS records:

   • *.kyma.example.com A EXTERNAL_PUBLIC_IP
   • gateway.kyma.example.com A REMOTE_ENV_IP

   You can use this script to get external IP addresses for load balancers:

   export EXTERNAL_PUBLIC_IP=$(kubectl get service -n istio-system istio-ingressgateway -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   export REMOTE_ENV_IP=$(kubectl get service -n kyma-system application-connector-nginx-ingress-controller -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   gcloud dns --project=$PROJECT record-sets transaction start --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $EXTERNAL_PUBLIC_IP --name=\*.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $REMOTE_ENV_IP --name=\gateway.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction execute --zone=$DNS_ZONE
   
   

Read this document for more information on installing Kyma.

0.6.1 (2019-01-15)

Console

• #2274 Configure luigified console title, logo and favicon (#2274) (@kwiatekus)

0.6.0

Local Kyma installation

Use the following command to run Kubernetes locally via Minikube:
$ ./installation/scripts/minikube.sh --domain "kyma.local" --vm-driver "hyperkit"

Kyma installation requires increased permissions granted by the cluster-admin role. To bind the role to the default ServiceAccount, run the following command:
$ kubectl apply -f ./installation/resources/default-sa-rbac-role.yaml

Wait until the kube-dns Pod is ready. Run this script to setup Tiller:
$ ./installation/scripts/install-tiller.sh

Configure the Kyma installation using the local configuration file:
$ kubectl apply -f https://github.com/kyma-project/kyma/releases/download/0.6.0/kyma-config-local.yaml

To trigger the installation process, label the kyma-installation custom resource:
$ kubectl label installation/kyma-installation action=install

Track progress of the installation using the following script:
$ ./installation/scripts/is-installed.sh

Installation on Google Kubernetes Engine

1. Make sure that you have gcloud tool installed. Set environment variables for your Google project identifier and your cluster name. You can keep your demo cluster name but your Google project identifier must be changed. Then you can spin up the cluster:

   export CLUSTER_NAME=demo
   export PROJECT=YOUR_PROJECT_ID
   
   gcloud beta container --project "$PROJECT" clusters \
   create "$CLUSTER_NAME" --zone "europe-west1-b" \
   --cluster-version "1.10.7" --machine-type "n1-standard-2" \
   --addons HorizontalPodAutoscaling,HttpLoadBalancing,KubernetesDashboard 
   

2. Install Tiller:

   kubectl apply -f https://raw.githubusercontent.com/kyma-project/kyma/0.6.0/installation/resources/tiller.yaml
   

3. Download the release and replace the placeholders with the proper values. The placeholders are the upper case variables surrounded by double underscore, such as __DOMAIN__. These are the mandatory values to change:

   • __DOMAIN__ which specifies your domain, for example kyma.example.com.
   • __TLS_CERT__ which is a PEM format, base64-encoded TLS certifcate.
   • __TLS_KEY__ which is a base64-encoded TLS private key.

   If you don't know how to set other values, replace them with an empty string.

   You can use this script to set only three mandatory values:

   export DOMAIN=kyma.example.com
   export TLS_CERT=base64_PEM_TLS_certificate
   export TLS_KEY=base64_TLS_private_key
   cat kyma-config-cluster.yaml | sed -e "s/__DOMAIN__/$DOMAIN/g" |sed -e "s/__TLS_CERT__/$TLS_CERT/g" | sed -e "s/__TLS_KEY__/$TLS_KEY/g" |sed -e "s/__.*__//g" >my-kyma.yaml
   

   As a result, you get the my-kyma.yaml file which you can deploy on the GKE cluster.

4. Configure kubectl to use your new cluster, add yourself as the cluster admin, and deploy Kyma installer with your configuration.

   gcloud container clusters get-credentials $CLUSTER_NAME --zone europe-west1-b --project $PROJECT
   
   kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account)
   
   kubectl apply -f my-kyma.yaml
   

5. Check if tiller and kyma-installer Pods are up and running. Start the installation process with this command:

   kubectl label installation/kyma-installation action=install
   

   Watch installation progress:

   kubectl logs -n kyma-installer [kyma-installer-pod] -f
   

6. Configure DNS for two load balancers created by the Kyma installation, which are istio-ingressgateway and core-nginx-ingress-controller. You need the following DNS records:

   • *.kyma.example.com A EXTERNAL_PUBLIC_IP
   • gateway.kyma.example.com A REMOTE_ENV_IP

   You can use this script to get external IP addresses for load balancers:

   export EXTERNAL_PUBLIC_IP=$(kubectl get service -n istio-system istio-ingressgateway -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   export REMOTE_ENV_IP=$(kubectl get service -n kyma-system application-connector-nginx-ingress-controller -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   gcloud dns --project=$PROJECT record-sets transaction start --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $EXTERNAL_PUBLIC_IP --name=\*.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $REMOTE_ENV_IP --name=\gateway.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction execute --zone=$DNS_ZONE
   
   

Read this document for more information on installing Kyma.

0.6.0 (2019-01-14)

Console

• #2261 Fix BackendModule test in UI API Layer acceptance tests (@pkosiec)

Documentation

• #2263 Remove redundant ticks from console docs (@michal-hudy)

Committers: 3

• Michal Kempski (@polskikiel)
• Michał Hudy (@michal-hudy)
• Paweł Kosiec (@pkosiec)

0.6.0-rc2 (2019-01-11)

Documentation

• #2231 Release 0.6.0 rc2 (@aszecowka)

CI

• #2231 Release 0.6.0 rc2 (@aszecowka)

Committers: 1

• Adam Szecówka (@aszecowka)

0.6.0-rc1 (2019-01-10)

Application Connector

• #2119 Bump version of Application Broker (@adamwalach)
• #2108 Fix Service Broker labels (@adamwalach)
• #2115 Bump version of connector-service-tests image (@crabtree)
• #2111 Add ca-cert to connector-service-tests image (@crabtree)
• #2094 Align Dockerfiles in connectivity components - bump (@crabtree)
• #2093 Align Dockerfiles in connectivity components (@crabtree)
• #2083 Update images version for ui-api and acceptance tests (@mszostok)
• #2065 Bump images after renaming (@Szymongib)
• #2006 Rename AC components to follow new architecture diagrams - charts (@crabtree)
• #1993 Rename AC components to follow new architecture diagrams (@crabtree)
• #2029 Update and adjust code for Application and ApplicationMapping (@mszostok)
• #2069 Bump connection token handler image (@franpog859)
• #2008 Rename RE to Application - documentation (@tomekpapiernik)
• #1965 Rename tokenrequest CR (@franpog859)
• #2040 Rename REB to AB - stage2 (@adamwalach)
• #2038 Update and adjust ui-api-acceptance code for Application (@polskikiel)
• #2052 Adjust acceptance test after renaming RemoteEnvironment (@mszostok)
• #2005 Renaming Connector Service (@janmedrek)
• #2019 Application Operator: rename Remote Environment to Application (@akgalwas)
• #1996 Rename of Remote Environment to Application - Metadata Service, Proxy Service (@Maladie)
• #1997 Rename Remote Environment to Application (@Szymongib)
• #2028 Add ApplicationMapping to know types in client (@mszostok)
• #2022 Rename REB chart to AB in application connector (@adamwalach)
• #2021 Add ApplicationMapping client (@mszostok)
• #2012 Bump version of Application Operator (@Szymongib)
• #1928 Rename of Remote Environment Controller to Application Operator (@Szymongib)
• #1950 Increase timeout of Connector Service call (@Szymongib)
• [#1958](https://github.com/kyma-pr...

0.6.0-rc2

Local Kyma installation

Use the following command to run Kubernetes locally via Minikube:
$ ./installation/scripts/minikube.sh --domain "kyma.local" --vm-driver "hyperkit"

Kyma installation requires increased permissions granted by the cluster-admin role. To bind the role to the default ServiceAccount, run the following command:
$ kubectl apply -f ./installation/resources/default-sa-rbac-role.yaml

Wait until the kube-dns Pod is ready. Run this script to setup Tiller:
$ ./installation/scripts/install-tiller.sh

Configure the Kyma installation using the local configuration file:
$ kubectl apply -f https://github.com/kyma-project/kyma/releases/download/0.6.0-rc2/kyma-config-local.yaml

To trigger the installation process, label the kyma-installation custom resource:
$ kubectl label installation/kyma-installation action=install

Track progress of the installation using the following script:
$ ./installation/scripts/is-installed.sh

Installation on Google Kubernetes Engine

1. Make sure that you have gcloud tool installed. Set environment variables for your Google project identifier and your cluster name. You can keep your demo cluster name but your Google project identifier must be changed. Then you can spin up the cluster:

   export CLUSTER_NAME=demo
   export PROJECT=YOUR_PROJECT_ID
   
   gcloud beta container --project "$PROJECT" clusters \
   create "$CLUSTER_NAME" --zone "europe-west1-b" \
   --cluster-version "1.10.7" --machine-type "n1-standard-2" \
   --addons HorizontalPodAutoscaling,HttpLoadBalancing,KubernetesDashboard 
   

2. Install Tiller:

   kubectl apply -f https://raw.githubusercontent.com/kyma-project/kyma/0.6.0-rc2/installation/resources/tiller.yaml
   

3. Download the release and replace the placeholders with the proper values. The placeholders are the upper case variables surrounded by double underscore, such as __DOMAIN__. These are the mandatory values to change:

   • __DOMAIN__ which specifies your domain, for example kyma.example.com.
   • __TLS_CERT__ which is a PEM format, base64-encoded TLS certifcate.
   • __TLS_KEY__ which is a base64-encoded TLS private key.

   If you don't know how to set other values, replace them with an empty string.

   You can use this script to set only three mandatory values:

   export DOMAIN=kyma.example.com
   export TLS_CERT=base64_PEM_TLS_certificate
   export TLS_KEY=base64_TLS_private_key
   cat kyma-config-cluster.yaml | sed -e "s/__DOMAIN__/$DOMAIN/g" |sed -e "s/__TLS_CERT__/$TLS_CERT/g" | sed -e "s/__TLS_KEY__/$TLS_KEY/g" |sed -e "s/__.*__//g" >my-kyma.yaml
   

   As a result, you get the my-kyma.yaml file which you can deploy on the GKE cluster.

4. Configure kubectl to use your new cluster, add yourself as the cluster admin, and deploy Kyma installer with your configuration.

   gcloud container clusters get-credentials $CLUSTER_NAME --zone europe-west1-b --project $PROJECT
   
   kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account)
   
   kubectl apply -f my-kyma.yaml
   

5. Check if tiller and kyma-installer Pods are up and running. Start the installation process with this command:

   kubectl label installation/kyma-installation action=install
   

   Watch installation progress:

   kubectl logs -n kyma-installer [kyma-installer-pod] -f
   

6. Configure DNS for two load balancers created by the Kyma installation, which are istio-ingressgateway and core-nginx-ingress-controller. You need the following DNS records:

   • *.kyma.example.com A EXTERNAL_PUBLIC_IP
   • gateway.kyma.example.com A REMOTE_ENV_IP

   You can use this script to get external IP addresses for load balancers:

   export EXTERNAL_PUBLIC_IP=$(kubectl get service -n istio-system istio-ingressgateway -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   export REMOTE_ENV_IP=$(kubectl get service -n kyma-system application-connector-nginx-ingress-controller -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   gcloud dns --project=$PROJECT record-sets transaction start --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $EXTERNAL_PUBLIC_IP --name=\*.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $REMOTE_ENV_IP --name=\gateway.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction execute --zone=$DNS_ZONE
   
   

Read this document for more information on installing Kyma.

0.6.0-rc2 (2019-01-11)

Application Connector

• #2241 Fix image name of Application Operator tests (@Szymongib)
• #2232 Bump image of Application Operator (@Szymongib)
• #2199 Add finalizers to Applications (@Szymongib)
• #2154 Skip Application charts installation in acceptance tests if not needed (@franpog859)

Service Catalog

• #2234 Bump console images for scrollspy feature on content-ui (@magicmatatjahu)
• #2174 Split "servicecatalog" domain in UI API Layer (@pkosiec)
• #2178 Use bundles 0.2.0 - added testing bundles. (@piotrmiskiewicz)

Installation

• #2226 Remove function for calling Bash scripts from the Installer component (@jakkab)
• #2204 Incorporate default ClusterRoleBinding into the minikube.sh script (@jakkab)
• #2087 Make is-installed script not exit on error (@kubadz)

Console

• #2239 Fix console-basic-test (@kwiatekus)
• #2207 Adjust labels in console UI (@kwiatekus)
• #2229 Introduce UI API Layer documentation (@pkosiec)
• #2228 Disable cache in ui tests (@kwiatekus)
• #2201 Stabilize ui tests for variable network conditions (@kwiatekus)
• #2174 Split "servicecatalog" domain in UI API Layer (@pkosiec)
• #2168 Split "servicecatalog" module in UI API Layer Acceptance tests (@pkosiec)
• #1991 Luigified Console (@kwiatekus)

Documentation

• #2235 Add cluster name info to the stability checker summary (@polskikiel)
• #2242 Change Help label to Docs in core navigation on console ui (@magicmatatjahu)
• #2234 Bump console images for scrollspy feature on content-ui (@magicmatatjahu)
• #2229 Introduce UI API Layer documentation (@pkosiec)
• #2205 Update xip installation documentation (@kfurgol)
• #2218 Add docs how to install Knative from release (@sjanota)
• #2198 Fix the links in the SC documentation (@klaudiagrz)
• #2177 Improve the overall SC documentation (@klaudiagrz)
• #2178 Use bundles 0.2.0 - added testing bundles. (@piotrmiskiewicz)

CI

• #2087 Make is-installed script not exit on error (@kubadz)

Committers: 18

• Franciszek Pogodziński (@franpog859)
• Jakub Dziechciewicz (@kubadz)
• Jakub Kabza (@jakkab)
• Jesús Real Serrano (@jesusreal)
• Klaudia Grzondziel (@klaudiagrz)
• Krzysztof (@kwiatekus)
• Lukasz Gornicki (@derberg)
• Maciej Urbańczyk (@magicmatatjahu)
• Michal Kempski (@polskikiel)
• Paweł Kosiec (@pkosiec)
• Piotr (@pbochynski)
• Piotr Miśkiewicz ([@piotrmiskiewicz](https...

0.6.0-rc1

Local Kyma installation

Use the following command to run Kubernetes locally via Minikube:
$ ./installation/scripts/minikube.sh --domain "kyma.local" --vm-driver "hyperkit"

Kyma installation requires increased permissions granted by the cluster-admin role. To bind the role to the default ServiceAccount, run the following command:
$ kubectl apply -f ./installation/resources/default-sa-rbac-role.yaml

Wait until the kube-dns Pod is ready. Run this script to setup Tiller:
$ ./installation/scripts/install-tiller.sh

Configure the Kyma installation using the local configuration file:
$ kubectl apply -f https://github.com/kyma-project/kyma/releases/download/0.6.0-rc1/kyma-config-local.yaml

To trigger the installation process, label the kyma-installation custom resource:
$ kubectl label installation/kyma-installation action=install

Track progress of the installation using the following script:
$ ./installation/scripts/is-installed.sh

Installation on Google Kubernetes Engine

1. Make sure that you have gcloud tool installed. Set environment variables for your Google project identifier and your cluster name. You can keep your demo cluster name but your Google project identifier must be changed. Then you can spin up the cluster:

   export CLUSTER_NAME=demo
   export PROJECT=YOUR_PROJECT_ID
   
   gcloud beta container --project "$PROJECT" clusters \
   create "$CLUSTER_NAME" --zone "europe-west1-b" \
   --cluster-version "1.10.7" --machine-type "n1-standard-2" \
   --addons HorizontalPodAutoscaling,HttpLoadBalancing,KubernetesDashboard 
   

2. Install Tiller:

   kubectl apply -f https://raw.githubusercontent.com/kyma-project/kyma/0.6.0-rc1/installation/resources/tiller.yaml
   

3. Download the release and replace the placeholders with the proper values. The placeholders are the upper case variables surrounded by double underscore, such as __DOMAIN__. These are the mandatory values to change:

   • __DOMAIN__ which specifies your domain, for example kyma.example.com.
   • __TLS_CERT__ which is a PEM format, base64-encoded TLS certifcate.
   • __TLS_KEY__ which is a base64-encoded TLS private key.

   If you don't know how to set other values, replace them with an empty string.

   You can use this script to set only three mandatory values:

   export DOMAIN=kyma.example.com
   export TLS_CERT=base64_PEM_TLS_certificate
   export TLS_KEY=base64_TLS_private_key
   cat kyma-config-cluster.yaml | sed -e "s/__DOMAIN__/$DOMAIN/g" |sed -e "s/__TLS_CERT__/$TLS_CERT/g" | sed -e "s/__TLS_KEY__/$TLS_KEY/g" |sed -e "s/__.*__//g" >my-kyma.yaml
   

   As a result, you get the my-kyma.yaml file which you can deploy on the GKE cluster.

4. Configure kubectl to use your new cluster, add yourself as the cluster admin, and deploy Kyma installer with your configuration.

   gcloud container clusters get-credentials $CLUSTER_NAME --zone europe-west1-b --project $PROJECT
   
   kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account)
   
   kubectl apply -f my-kyma.yaml
   

5. Check if tiller and kyma-installer Pods are up and running. Start the installation process with this command:

   kubectl label installation/kyma-installation action=install
   

   Watch installation progress:

   kubectl logs -n kyma-installer [kyma-installer-pod] -f
   

6. Configure DNS for two load balancers created by the Kyma installation, which are istio-ingressgateway and core-nginx-ingress-controller. You need the following DNS records:

   • *.kyma.example.com A EXTERNAL_PUBLIC_IP
   • gateway.kyma.example.com A REMOTE_ENV_IP

   You can use this script to get external IP addresses for load balancers:

   export EXTERNAL_PUBLIC_IP=$(kubectl get service -n istio-system istio-ingressgateway -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   export REMOTE_ENV_IP=$(kubectl get service -n kyma-system application-connector-nginx-ingress-controller -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   gcloud dns --project=$PROJECT record-sets transaction start --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $EXTERNAL_PUBLIC_IP --name=\*.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $REMOTE_ENV_IP --name=\gateway.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction execute --zone=$DNS_ZONE
   
   

0.6.0-rc1 (2019-01-10)

Application Connector

• #2195 Fix connection-token-handler Gopkg.lock (@crabtree)
• #2119 Bump version of Application Broker (@adamwalach)
• #2108 Fix Service Broker labels (@adamwalach)
• #2115 Bump version of connector-service-tests image (@crabtree)
• #2111 Add ca-cert to connector-service-tests image (@crabtree)
• #2094 Align Dockerfiles in connectivity components - bump (@crabtree)
• #2093 Align Dockerfiles in connectivity components (@crabtree)
• #2083 Update images version for ui-api and acceptance tests (@mszostok)
• #2065 Bump images after renaming (@Szymongib)
• #2006 Rename AC components to follow new architecture diagrams - charts (@crabtree)
• #1993 Rename AC components to follow new architecture diagrams (@crabtree)
• #2029 Update and adjust code for Application and ApplicationMapping (@mszostok)
• #2069 Bump connection token handler image (@franpog859)
• #2008 Rename RE to Application - documentation (@tomekpapiernik)
• #1965 Rename tokenrequest CR (@franpog859)
• #2040 Rename REB to AB - stage2 (@adamwalach)
• #2038 Update and adjust ui-api-acceptance code for Application (@polskikiel)
• #2052 Adjust acceptance test after renaming RemoteEnvironment (@mszostok)
• #2005 Renaming Connector Service (@janmedrek)
• #2019 Application Operator: rename Remote Environment to Application (@akgalwas)
• #1996 Rename of Remote Environment to Application - Metadata Service, Proxy Service (@Maladie)
• #1997 Rename Remote Environment to Application (@Szymongib)
• #2028 Add ApplicationMapping to know types in client (@mszostok)
• #2022 Rename REB chart to AB in application connector (@adamwalach)
• #2021 Add ApplicationMapping client (@mszostok)
• #2012 Bump version of Application Operator (@Szymongib)
• #1928 Rename of Remote Environment Controller to Application Operator (@Szymongib)
• #1950 Increase timeout of Connector Service call (@Szymongib)
• #1958 Bump image of Metadata Service and UI API (@Szymongib)
• #1910 Fix Minio related leak in Metadata Service and UI API layer (@Szymongib)
• #1858 Add prow related components for connection-token-handler component (@crabtree)
• #1867 Add prow related files for proxy-service component (@crabtree)
• #1852 Migrate RE Controller and RE Controller Tests to Prow (@Szymongib)
• #1860 Migrate Metadata Service and Metadata Service Tests to Prow (@Szymongib)
• [#1847](https://github.co...

0.5.0

Local Kyma installation

Use the following command to run Kubernetes locally via Minikube:
$ ./installation/scripts/minikube.sh --domain "kyma.local" --vm-driver "hyperkit"

Kyma installation requires increased permissions granted by the cluster-admin role. To bind the role to the default ServiceAccount, run the following command:
$ kubectl apply -f ./installation/resources/default-sa-rbac-role.yaml

Wait until the kube-dns Pod is ready. Run this script to setup Tiller:
$ ./installation/scripts/install-tiller.sh

Configure the Kyma installation using the local configuration file:
$ kubectl apply -f https://github.com/kyma-project/kyma/releases/download/0.5.0/kyma-config-local.yaml

To trigger the installation process, label the kyma-installation custom resource:
$ kubectl label installation/kyma-installation action=install

Track progress of the installation using the following script:
$ ./installation/scripts/is-installed.sh

Installation on Google Kubernetes Engine

1. Make sure that you have gcloud tool installed. Set environment variables for your Google project identifier and your cluster name. You can keep your demo cluster name but your Google project identifier must be changed. Then you can spin up the cluster:

   export CLUSTER_NAME=demo
   export PROJECT=YOUR_PROJECT_ID
   
   gcloud beta container --project "$PROJECT" clusters \
   create "$CLUSTER_NAME" --zone "europe-west1-b" \
   --cluster-version "1.10.7" --machine-type "n1-standard-2" \
   --addons HorizontalPodAutoscaling,HttpLoadBalancing,KubernetesDashboard 
   

2. Install Tiller:

   kubectl apply -f https://raw.githubusercontent.com/kyma-project/kyma/0.5.0/installation/resources/tiller.yaml
   

3. Download the release and replace the placeholders with the proper values. The placeholders are the upper case variables surrounded by double underscore, such as __DOMAIN__. These are the mandatory values to change:

   • __DOMAIN__ which specifies your domain, for example kyma.example.com.
   • __TLS_CERT__ which is a PEM format, base64-encoded TLS certifcate.
   • __TLS_KEY__ which is a base64-encoded TLS private key.

   If you don't know how to set other values, replace them with an empty string.

   You can use this script to set only three mandatory values:

   export DOMAIN=kyma.example.com
   export TLS_CERT=base64_PEM_TLS_certificate
   export TLS_KEY=base64_TLS_private_key
   cat kyma-config-cluster.yaml | sed -e "s/__DOMAIN__/$DOMAIN/g" |sed -e "s/__TLS_CERT__/$TLS_CERT/g" | sed -e "s/__TLS_KEY__/$TLS_KEY/g" |sed -e "s/__.*__//g" >my-kyma.yaml
   

   As a result, you get the my-kyma.yaml file which you can deploy on the GKE cluster.

4. Configure kubectl to use your new cluster, add yourself as the cluster admin, and deploy Kyma installer with your configuration.

   gcloud container clusters get-credentials $CLUSTER_NAME --zone europe-west1-b --project $PROJECT
   
   kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account)
   
   kubectl apply -f my-kyma.yaml
   

5. Check if tiller and kyma-installer Pods are up and running. Start the installation process with this command:

   kubectl label installation/kyma-installation action=install
   

   Watch installation progress:

   kubectl logs -n kyma-installer [kyma-installer-pod] -f
   

6. Configure DNS for two load balancers created by the Kyma installation, which are istio-ingressgateway and core-nginx-ingress-controller. You need the following DNS records:

   • *.kyma.example.com A EXTERNAL_PUBLIC_IP
   • gateway.kyma.example.com A REMOTE_ENV_IP

   You can use this script to get external IP addresses for load balancers:

   export EXTERNAL_PUBLIC_IP=$(kubectl get service -n istio-system istio-ingressgateway -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   export REMOTE_ENV_IP=$(kubectl get service -n kyma-system application-connector-nginx-ingress-controller -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   gcloud dns --project=$PROJECT record-sets transaction start --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $EXTERNAL_PUBLIC_IP --name=\*.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $REMOTE_ENV_IP --name=\gateway.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction execute --zone=$DNS_ZONE
   
   

Changelog

Application Connector

• #1607 Cluster overrides allow skipping TLS verification in Application Connector tests (@franpog859)
• #1590 Connector test skip verify (@Szymongib)
• #1486 Support self-signed certificate in the testsof Application Connector components (@franpog859)
• #1468 Add scripts to run acceptance tests on Minikube (@Szymongib)
• #1473 Update Remote Environment Client (@Szymongib)
• #1340 Added Helm hook for kyma-integration namespace installation (@Szymongib)
• #1432 Update nginx-ingress-controller name (@tomekpapiernik)
• #1250 #529 Updating Remote Environment Controller and Remote Environments charts (@akgalwas)
• #1196 Rename gateway (@akgalwas)
• #1228 #529 Renaming gateway to proxy service in remote-environment-controller (@akgalwas)
• #1413 Bump version of RE Controller (@Szymongib)
• #1309 Application Connector getting started tutorials (@Szymongib)
• #1333 Update RE client in RE Controller (@Szymongib)
• #1385 Assign crabtree in connector, metadata and remote environemnts (@crabtree)
• #1349 Remove YAML definition for registering REB as ClusterServiceBroker (@mszostok)
• #1335 Add Application Connector to cluster installation (@Szymongib)
• #1153 Prepare Application Connector for Modularisation (@janmedrek)
• #1324 Added different limits for Nginx-Ingress on local and on cluster (@Szymongib)
• #1317 Fix RE installation on cluster (@Szymongib)
• #1212 Bump REB and acceptance test (@polskikiel)
• #1019 Remote Environments installation cleanup (@Szymongib)
• #1301 Increase Minio memory limit for cluster installation (@pkosiec)
• #1164 Make REB namespaced only (@polskikiel)
• #1286 Update Application Connector documentation (@tomekpapiernik)
• #1278 Fix Connector Service Tests chart (@Szymongib)
• #1241 Adding a possibility to skip SSL certificateverification in Connector Service acceptance tests (@lszymik)
• #1258 Bump Remote Environment Controller tests (@Szymongib)
• #1058 Improve error messages returned from the Metadata Service (@franpog859)
• #1217 Added RE Controller test for setting access-label (@Szymongib)
• #1246 Application Connector CRD desc. update + fixes (@tomekpapiernik)
• #836 Make the Application Connector documentation more clear (@lszymik)
• #1213 Bump ui-api and ui-api-acceptance version (@polskikiel)
• #1207 Bumped version of Remote Environment Controller (@Szymongib)
• #1055 Create mutations for RemoteEnvironment ([@polskikiel...

0.5-rc2

Local Kyma installation

Use the following command to run Kubernetes locally via Minikube:
$ ./installation/scripts/minikube.sh --domain "kyma.local" --vm-driver "hyperkit"

Kyma installation requires increased permissions granted by the cluster-admin role. To bind the role to the default ServiceAccount, run the following command:
$ kubectl apply -f ./installation/resources/default-sa-rbac-role.yaml

Wait until the kube-dns Pod is ready. Run this script to setup Tiller:
$ ./installation/scripts/install-tiller.sh

Configure the Kyma installation using the local configuration file:
$ kubectl apply -f https://github.com/kyma-project/kyma/releases/download/0.5-rc2/kyma-config-local.yaml

To trigger the installation process, label the kyma-installation custom resource:
$ kubectl label installation/kyma-installation action=install

Track progress of the installation using the following script:
$ ./installation/scripts/is-installed.sh

Installation on Google Kubernetes Engine

1. Make sure that you have gcloud tool installed. Set environment variables for your Google project identifier and your cluster name. You can keep your demo cluster name but your Google project identifier must be changed. Then you can spin up the cluster:

   export CLUSTER_NAME=demo
   export PROJECT=YOUR_PROJECT_ID
   
   gcloud beta container --project "$PROJECT" clusters \
   create "$CLUSTER_NAME" --zone "europe-west1-b" \
   --cluster-version "1.10.7-gke.11" --machine-type "n1-standard-2" \
   --addons HorizontalPodAutoscaling,HttpLoadBalancing,KubernetesDashboard 
   

2. Install Tiller:

   kubectl apply -f https://raw.githubusercontent.com/kyma-project/kyma/0.5-rc2/installation/resources/tiller.yaml
   

3. Download the release and replace the placeholders with the proper values. The placeholders are the upper case variables surrounded by double underscore, such as __DOMAIN__. These are the mandatory values to change:

   • __DOMAIN__ which specifies your domain, for example kyma.example.com.
   • __TLS_CERT__ which is a PEM format, base64-encoded TLS certifcate.
   • __TLS_KEY__ which is a base64-encoded TLS private key.

   If you don't know how to set other values, replace them with an empty string.

   You can use this script to set only three mandatory values:

   export DOMAIN=kyma.example.com
   export TLS_CERT=base64_PEM_TLS_certificate
   export TLS_KEY=base64_TLS_private_key
   cat kyma-config-cluster.yaml | sed -e "s/__DOMAIN__/$DOMAIN/g" |sed -e "s/__TLS_CERT__/$TLS_CERT/g" | sed -e "s/__TLS_KEY__/$TLS_KEY/g" |sed -e "s/__.*__//g" >my-kyma.yaml
   

   As a result, you get the my-kyma.yaml file which you can deploy on the GKE cluster.

4. Configure kubectl to use your new cluster, add yourself as the cluster admin, and deploy Kyma installer with your configuration.

   gcloud container clusters get-credentials $CLUSTER_NAME --zone europe-west1-b --project $PROJECT
   
   kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account)
   
   kubectl apply -f my-kyma.yaml
   

5. Check if tiller and kyma-installer Pods are up and running. Start the installation process with this command:

   kubectl label installation/kyma-installation action=install
   

   Watch installation progress:

   kubectl logs -n kyma-installer [kyma-installer-pod] -f
   

6. Configure DNS for two load balancers created by the Kyma installation, which are istio-ingressgateway and core-nginx-ingress-controller. You need the following DNS records:

   • *.kyma.example.com A EXTERNAL_PUBLIC_IP
   • gateway.kyma.example.com A REMOTE_ENV_IP

   You can use this script to get external IP addresses for load balancers:

   export EXTERNAL_PUBLIC_IP=$(kubectl get service -n istio-system istio-ingressgateway -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   export REMOTE_ENV_IP=$(kubectl get service -n kyma-system application-connector-nginx-ingress-controller -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   gcloud dns --project=$PROJECT record-sets transaction start --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $EXTERNAL_PUBLIC_IP --name=\*.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $REMOTE_ENV_IP --name=\gateway.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction execute --zone=$DNS_ZONE
   
   

Changelog

Application Connector

• #1607 Cluster overrides allow skipping TLS verification in Application Connector tests (@franpog859)
• #1590 Connector test skip verify (@Szymongib)
• #1486 Support self-signed certificate in the testsof Application Connector components (@franpog859)
• #1468 Add scripts to run acceptance tests on Minikube (@Szymongib)
• #1473 Update Remote Environment Client (@Szymongib)
• #1340 Added Helm hook for kyma-integration namespace installation (@Szymongib)
• #1432 Update nginx-ingress-controller name (@tomekpapiernik)
• #1250 #529 Updating Remote Environment Controller and Remote Environments charts (@akgalwas)
• #1196 Rename gateway (@akgalwas)
• #1228 #529 Renaming gateway to proxy service in remote-environment-controller (@akgalwas)
• #1413 Bump version of RE Controller (@Szymongib)
• #1309 Application Connector getting started tutorials (@Szymongib)
• #1333 Update RE client in RE Controller (@Szymongib)
• #1385 Assign crabtree in connector, metadata and remote environemnts (@crabtree)
• #1349 Remove YAML definition for registering REB as ClusterServiceBroker (@mszostok)
• #1335 Add Application Connector to cluster installation (@Szymongib)
• #1153 Prepare Application Connector for Modularisation (@janmedrek)
• #1324 Added different limits for Nginx-Ingress on local and on cluster (@Szymongib)
• #1317 Fix RE installation on cluster (@Szymongib)
• #1212 Bump REB and acceptance test (@polskikiel)
• #1019 Remote Environments installation cleanup (@Szymongib)
• #1301 Increase Minio memory limit for cluster installation (@pkosiec)
• #1164 Make REB namespaced only (@polskikiel)
• #1286 Update Application Connector documentation (@tomekpapiernik)
• #1278 Fix Connector Service Tests chart (@Szymongib)
• #1241 Adding a possibility to skip SSL certificateverification in Connector Service acceptance tests (@lszymik)
• #1258 Bump Remote Environment Controller tests (@Szymongib)
• #1058 Improve error messages returned from the Metadata Service (@franpog859)
• #1217 Added RE Controller test for setting access-label (@Szymongib)
• #1246 Application Connector CRD desc. update + fixes (@tomekpapiernik)
• #836 Make the Application Connector documentation more clear (@lszymik)
• #1213 Bump ui-api and ui-api-acceptance version (@polskikiel)
• #1207 Bumped version of Remote Environment Controller (@Szymongib)
• #1055 Create mutations for RemoteEnvironment ...

0.5-rc

Local Kyma installation

Use the following command to run Kubernetes locally via Minikube:
$ ./installation/scripts/minikube.sh --domain "kyma.local" --vm-driver "hyperkit"

Kyma installation requires increased permissions granted by the cluster-admin role. To bind the role to the default ServiceAccount, run the following command:
$ kubectl apply -f ./installation/resources/default-sa-rbac-role.yaml

Wait until the kube-dns Pod is ready. Run this script to setup Tiller:
$ ./installation/scripts/install-tiller.sh

Configure the Kyma installation using the local configuration file:
$ kubectl apply -f https://github.com/kyma-project/kyma/releases/download/0.5-rc/kyma-config-local.yaml

To trigger the installation process, label the kyma-installation custom resource:
$ kubectl label installation/kyma-installation action=install

Track progress of the installation using the following script:
$ ./installation/scripts/is-installed.sh

Installation on Google Kubernetes Engine

1. Make sure that you have gcloud tool installed. Set environment variables for your Google project identifier and your cluster name. You can keep your demo cluster name but your Google project identifier must be changed. Then you can spin up the cluster:

   export CLUSTER_NAME=demo
   export PROJECT=YOUR_PROJECT_ID
   
   gcloud beta container --project "$PROJECT" clusters \
   create "$CLUSTER_NAME" --zone "europe-west1-b" \
   --cluster-version "1.10.7-gke.9" --machine-type "n1-standard-2" \
   --addons HorizontalPodAutoscaling,HttpLoadBalancing,KubernetesDashboard 
   

2. Install Tiller:

   kubectl apply -f https://raw.githubusercontent.com/kyma-project/kyma/0.5-rc/installation/resources/tiller.yaml
   

3. Download the release and replace the placeholders with the proper values. The placeholders are the upper case variables surrounded by double underscore, such as __DOMAIN__. These are the mandatory values to change:

   • __DOMAIN__ which specifies your domain, for example kyma.example.com.
   • __TLS_CERT__ which is a PEM format, base64-encoded TLS certifcate.
   • __TLS_KEY__ which is a base64-encoded TLS private key.

   If you don't know how to set other values, replace them with an empty string.

   You can use this script to set only three mandatory values:

   export DOMAIN=kyma.example.com
   export TLS_CERT=base64_PEM_TLS_certificate
   export TLS_KEY=base64_TLS_private_key
   cat kyma-config-cluster.yaml | sed -e "s/__DOMAIN__/$DOMAIN/g" |sed -e "s/__TLS_CERT__/$TLS_CERT/g" | sed -e "s/__TLS_KEY__/$TLS_KEY/g" |sed -e "s/__.*__//g" >my-kyma.yaml
   

   As a result, you get the my-kyma.yaml file which you can deploy on the GKE cluster.

4. Configure kubectl to use your new cluster, add yourself as the cluster admin, and deploy Kyma installer with your configuration.

   gcloud container clusters get-credentials $CLUSTER_NAME --zone europe-west1-b --project $PROJECT
   
   kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account)
   
   kubectl apply -f my-kyma.yaml
   

5. Check if tiller and kyma-installer Pods are up and running. Start the installation process with this command:

   kubectl label installation/kyma-installation action=install
   

   Watch installation progress:

   kubectl logs -n kyma-installer [kyma-installer-pod] -f
   

6. Configure DNS for two load balancers created by the Kyma installation, which are istio-ingressgateway and core-nginx-ingress-controller. You need the following DNS records:

   • *.kyma.example.com A EXTERNAL_PUBLIC_IP
   • gateway.kyma.example.com A REMOTE_ENV_IP

   You can use this script to get external IP addresses for load balancers:

   export EXTERNAL_PUBLIC_IP=$(kubectl get service -n istio-system istio-ingressgateway -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   export REMOTE_ENV_IP=$(kubectl get service -n kyma-system application-connector-nginx-ingress-controller -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   gcloud dns --project=$PROJECT record-sets transaction start --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $EXTERNAL_PUBLIC_IP --name=\*.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction add $REMOTE_ENV_IP --name=\gateway.$DOMAIN. --ttl=60 --type=A --zone=$DNS_ZONE
   
   gcloud dns --project=$PROJECT record-sets transaction execute --zone=$DNS_ZONE
   
   

Changelog

Application Connector

• #1607 Cluster overrides allow skipping TLS verification in Application Connector tests (@franpog859)
• #1590 Connector test skip verify (@Szymongib)
• #1486 Support self-signed certificate in the testsof Application Connector components (@franpog859)
• #1468 Add scripts to run acceptance tests on Minikube (@Szymongib)
• #1473 Update Remote Environment Client (@Szymongib)
• #1340 Added Helm hook for kyma-integration namespace installation (@Szymongib)
• #1432 Update nginx-ingress-controller name (@tomekpapiernik)
• #1250 #529 Updating Remote Environment Controller and Remote Environments charts (@akgalwas)
• #1196 Rename gateway (@akgalwas)
• #1228 #529 Renaming gateway to proxy service in remote-environment-controller (@akgalwas)
• #1413 Bump version of RE Controller (@Szymongib)
• #1309 Application Connector getting started tutorials (@Szymongib)
• #1333 Update RE client in RE Controller (@Szymongib)
• #1385 Assign crabtree in connector, metadata and remote environemnts (@crabtree)
• #1349 Remove YAML definition for registering REB as ClusterServiceBroker (@mszostok)
• #1335 Add Application Connector to cluster installation (@Szymongib)
• #1153 Prepare Application Connector for Modularisation (@janmedrek)
• #1324 Added different limits for Nginx-Ingress on local and on cluster (@Szymongib)
• #1317 Fix RE installation on cluster (@Szymongib)
• #1212 Bump REB and acceptance test (@polskikiel)
• #1019 Remote Environments installation cleanup (@Szymongib)
• #1301 Increase Minio memory limit for cluster installation (@pkosiec)
• #1164 Make REB namespaced only (@polskikiel)
• #1286 Update Application Connector documentation (@tomekpapiernik)
• #1278 Fix Connector Service Tests chart (@Szymongib)
• #1241 Adding a possibility to skip SSL certificateverification in Connector Service acceptance tests (@lszymik)
• #1258 Bump Remote Environment Controller tests (@Szymongib)
• #1058 Improve error messages returned from the Metadata Service (@franpog859)
• #1217 Added RE Controller test for setting access-label (@Szymongib)
• #1246 Application Connector CRD desc. update + fixes (@tomekpapiernik)
• #836 Make the Application Connector documentation more clear (@lszymik)
• #1213 Bump ui-api and ui-api-acceptance version (@polskikiel)
• #1207 Bumped version of Remote Environment Controller (@Szymongib)
• #1055 Create mutations for RemoteEnvironment ([@p...

0.4.3

Local Kyma installation

Use the following command to run Kubernetes locally via Minikube:
$ ./installation/scripts/minikube.sh --domain "kyma.local" --vm-driver "hyperkit"

Kyma installation requires increased permissions granted by the cluster-admin role. To bind the role to the default ServiceAccount, run the following command:
$ kubectl apply -f ./installation/resources/default-sa-rbac-role.yaml

Wait until the kube-dns Pod is ready. Run this script to setup Tiller:
$ ./installation/scripts/install-tiller.sh

Configure the Kyma installation using the local configuration file:
$ kubectl apply -f https://github.com/kyma-project/kyma/releases/download/0.4.3/kyma-config-local.yaml

To trigger the installation process, label the kyma-installation custom resource:
$ kubectl label installation/kyma-installation action=install

Track progress of the installation using the following script:
$ ./installation/scripts/is-installed.sh

Installation on Google Kubernetes Engine

1. Make sure that you have gcloud tool installed. Set environment variables for your Google project identifier and your cluster name. You can keep your demo cluster name but your Google project identifier must be changed. Then you can spin up the cluster:

   export CLUSTER_NAME=demo
   export PROJECT=YOUR_PROJECT_ID
   
   gcloud beta container --project "$PROJECT" clusters \
   create "$CLUSTER_NAME" --zone "europe-west1-b" \
   --cluster-version "1.10.7-gke.2" --machine-type "n1-standard-2" \
   --addons HorizontalPodAutoscaling,HttpLoadBalancing,KubernetesDashboard 
   

2. Install Tiller:

   kubectl apply -f https://raw.githubusercontent.com/kyma-project/kyma/0.4.3/installation/resources/tiller.yaml
   

3. Download the release and replace the placeholders with the proper values. The placeholders are the upper case variables surrounded by double underscore, such as __DOMAIN__. These are the mandatory values to change:

   • __DOMAIN__ which specifies your domain, for example kyma.example.com.
   • __TLS_CERT__ which is a PEM format, base64-encoded TLS certifcate.
   • __TLS_KEY__ which is a base64-encoded TLS private key.

   If you don't know how to set other values, replace them with an empty string.

   You can use this script to set only three mandatory values:

   export DOMAIN=kyma.example.com
   export TLS_CERT=base64_PEM_TLS_certificate
   export TLS_KEY=base64_TLS_private_key
   cat kyma-config-cluster.yaml | sed -e "s/__DOMAIN__/$DOMAIN/g" |sed -e "s/__TLS_CERT__/$TLS_CERT/g" | sed -e "s/__TLS_KEY__/$TLS_KEY/g" |sed -e "s/__.*__//g" >my-kyma.yaml
   

   As a result, you get the my-kyma.yaml file which you can deploy on the GKE cluster.

4. Configure kubectl to use your new cluster, add yourself as the cluster admin, and deploy Kyma installer with your configuration.

   gcloud container clusters get-credentials $CLUSTER_NAME --zone europe-west1-b --project $PROJECT
   
   kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account)
   
   kubectl apply -f my-kyma.yaml
   

5. Check if tiller and kyma-installer Pods are up and running. Start the installation process with this command:

   kubectl label installation/kyma-installation action=install
   

   Watch installation progress:

   kubectl logs -n kyma-installer [kyma-installer-pod] -f
   

6. Configure DNS for two load balancers created by the Kyma installation, which are istio-ingressgateway and core-nginx-ingress-controller. You need the following DNS records:

   • *.kyma.example.com A EXTERNAL_PUBLIC_IP
   • gateway.kyma.example.com A REMOTE_ENV_IP

   You can use this script to get external IP addresses for load balancers:

   export EXTERNAL_PUBLIC_IP=$(kubectl get service -n istio-system istio-ingressgateway -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   export REMOTE_ENV_IP=$(kubectl get service -n kyma-system core-nginx-ingress-controller -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   

Changelog

0.4.3 (2018-10-17)

Application Connector

• #1301 Increase Minio memory limit for cluster installation (@pkosiec)
• #985 Enable dynamic versioning (@Szymongib)
• #1246 Application Connector CRD desc. update + fixes (@tomekpapiernik)
• #836 Make the Application Connector documentation more clear (@lszymik)
• #1207 Bumped version of Remote Environment Controller (@Szymongib)
• #1183 Setting Access Label in RE Controller (@Szymongib)

Service Catalog

• #1301 Increase Minio memory limit for cluster installation (@pkosiec)

Security

• #1099 Add apiserver proxy component to release jenkinsfile (@kubadz)

Service Mesh

• #1107 Add memory limits for local pilot (@sjanota)
• #1101 Give mixer more memory on cluster (@sjanota)

Installation

• #1107 Add memory limits for local pilot (@sjanota)

Tracing

• #1074 Closes #989 Multiple request in same trace (@abbi-gaurav)

Console

• #1124 Adding console title and logoUrl to installer overrides (@kwiatekus)

Documentation

• #1246 Application Connector CRD desc. update + fixes (@tomekpapiernik)
• #836 Make the Application Connector documentation more clear (@lszymik)

Committers: 10

• Gaurav Abbi (@abbi-gaurav)
• Jakub Dziechciewicz (@kubadz)
• Krzysztof (@kwiatekus)
• Lukasz Szymik (@lszymik)
• Paweł Kosiec (@pkosiec)
• Sayan Hazra (@sayanh)
• Szymon Gibała (@Szymongib)
• Szymon Janota (@sjanota)
• Tomasz Papiernik (@tomekpapiernik)
• @venturasr

0.4.1

Local Kyma installation

Use the following command to run Kubernetes locally via Minikube:
$ ./installation/scripts/minikube.sh --domain "kyma.local" --vm-driver "hyperkit"

Kyma installation requires increased permissions granted by the cluster-admin role. To bind the role to the default ServiceAccount, run the following command:
$ kubectl apply -f ./installation/resources/default-sa-rbac-role.yaml

Wait until the kube-dns Pod is ready. Run this script to setup Tiller:
$ ./installation/scripts/install-tiller.sh

Configure the Kyma installation using the local configuration file:
$ kubectl apply -f https://github.com/kyma-project/kyma/releases/download/0.4.1/kyma-config-local.yaml

To trigger the installation process, label the kyma-installation custom resource:
$ kubectl label installation/kyma-installation action=install

Track progress of the installation using the following script:
$ ./installation/scripts/is-installed.sh

Installation on Google Kubernetes Engine

1. Make sure that you have gcloud tool installed. Set environment variables for your Google project identifier and your cluster name. You can keep your demo cluster name but your Google project identifier must be changed. Then you can spin up the cluster:

   export CLUSTER_NAME=demo
   export PROJECT=YOUR_PROJECT_ID
   
   gcloud beta container --project "$PROJECT" clusters \
   create "$CLUSTER_NAME" --zone "europe-west1-b" \
   --cluster-version "1.10.7-gke.2" --machine-type "n1-standard-2" \
   --addons HorizontalPodAutoscaling,HttpLoadBalancing,KubernetesDashboard 
   

2. Install Tiller:

   kubectl apply -f https://raw.githubusercontent.com/kyma-project/kyma/0.4.1/installation/resources/tiller.yaml
   

3. Download the release and replace the placeholders with the proper values. The placeholders are the upper case variables surrounded by double underscore, such as __DOMAIN__. These are the mandatory values to change:

   • __DOMAIN__ which specifies your domain, for example kyma.example.com.
   • __TLS_CERT__ which is a PEM format, base64-encoded TLS certifcate.
   • __TLS_KEY__ which is a base64-encoded TLS private key.

   If you don't know how to set other values, replace them with an empty string.

   You can use this script to set only three mandatory values:

   export DOMAIN=kyma.example.com
   export TLS_CERT=base64_PEM_TLS_certificate
   export TLS_KEY=base64_TLS_private_key
   cat kyma-config-cluster.yaml | sed -e "s/__DOMAIN__/$DOMAIN/g" |sed -e "s/__TLS_CERT__/$TLS_CERT/g" | sed -e "s/__TLS_KEY__/$TLS_KEY/g" |sed -e "s/__.*__//g" >my-kyma.yaml
   

   As a result, you get the my-kyma.yaml file which you can deploy on the GKE cluster.

4. Configure kubectl to use your new cluster, add yourself as the cluster admin, and deploy Kyma installer with your configuration.

   gcloud container clusters get-credentials $CLUSTER_NAME --zone europe-west1-b --project $PROJECT
   
   kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account)
   
   kubectl apply -f my-kyma.yaml
   

5. Check if tiller and kyma-installer Pods are up and running. Start the installation process with this command:

   kubectl label installation/kyma-installation action=install
   

   Watch installation progress:

   kubectl logs -n kyma-installer [kyma-installer-pod] -f
   

6. Configure DNS for two load balancers created by the Kyma installation, which are istio-ingressgateway and core-nginx-ingress-controller. You need the following DNS records:

   • *.kyma.example.com A EXTERNAL_PUBLIC_IP
   • gateway.kyma.example.com A REMOTE_ENV_IP

   You can use this script to get external IP addresses for load balancers:

   export EXTERNAL_PUBLIC_IP=$(kubectl get service -n istio-system istio-ingressgateway -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   export REMOTE_ENV_IP=$(kubectl get service -n kyma-system core-nginx-ingress-controller -o jsonpath="{.status.loadBalancer.ingress[0].ip}")
   
   

Changelog

Application Connector

• #999 Disabled Remote Environment Controller tests (@Szymongib)
• #967 Update Metadata Service API Spec (@Szymongib)
• #957 Update Remote Environment chart in RE Controller (@Szymongib)
• #928 Fix for description being skipped during struct mapping (@janmedrek)
• #879 Disable SourceClear from AC components (@Szymongib)
• #885 Fix RE Controller Tests retries (@Szymongib)
• #808 Metadata service must return 404 when service is not existing (@lszymik)
• #762 Remote Environment Controller acceptance tests chart (@Szymongib)
• #799 Change Metadata Service API to follow new CRD definition (@janmedrek)
• #710 Remote Environment Controller acceptance tests (@Szymongib)
• #787 Updated Remote Environment Client in Gateway (@Szymongib)
• #800 Updated Remote Environment client in RE Controller (@Szymongib)
• #820 Fix the name of the port in Event service to resolve an issue with checks (@lszymik)
• #760 Bumped Connector Service Tests (@Szymongib)
• #618 Remote Environment Controller chart (@Szymongib)
• #587 Remote Environment Controller implementation (@Szymongib)
• #600 One-click-configuration updated with nodeport notice for local installation (@tomekpapiernik)
• #559 Bump gateway version (@janmedrek)
• #396 Auth token cache (@janmedrek)

Serverless

• #1013 Update lambda image (@venturasr)
• #1067 Adjust local settings, memory resources for Prometheus and Logging (@venturasr)
• #492 Bump kubless test client image (@sayanh)
• #489 Removed the dependencies from test functions (@sayanh)
• #433 Bumped kubeless test image (@sayanh)
• #431 Adding more logs to kubeless test client (@sayanh)

Service Catalog

• #1062 Limit Minio resources (@michal-hudy)
• #1021 Bump catalog-ui image to 0.1.188 (@magicmatatjahu)
• #937 Enhance SB/SBU mutations (@piotrmiskiewicz)
• #933 Expose ServicePlan createSB schema via ui-api-layer (@polskikiel)
• #991 Fix 404 links in service catalog etcd doc (@mwieczorek)
• #969 Expose bindings stats via ui-api-layer (@polskikiel)
• #784 Replace etcd-operator with statefulset for service catalog and helm broker datastore (@mwieczorek)
• #886 Relist broker on mapping creation and deletion (@polskikiel)
• #877 Add bindable resources endpoint (@piotrmiskiewicz)
• #909 Fix core acceptance tests (@mszostok)
• #823 Fix bug with Events displaying in catalog and instances (@magicmatatjahu)
• #794 Skip UI API Acceptance Tests when SCI is enabled (@michal-hudy)
• #730 Use custom service-catalog docker image 0.1.32 with memory-leak fix ([@piotrmiskiewicz](https://github.com/piotrmiskie...