A flexible and easy way to connect and extend enterprise applications in a cloud-native world
Clone or download
venturasr and sayanh Add more logging when ns deletion fails to work (#1206)
* Fine tuned kubeless-test

- Added force deletion of all k8s resources
- Added extensive logging while deletion of ns times out
Latest commit 1bc49b4 Oct 15, 2018
Failed to load latest commit information.
.github Enable Probot Stale bot (#694) Sep 14, 2018
components Change tls cert name in re controller (#1240) Oct 15, 2018
docs Make Helm-Broker more resilient (#1180) Oct 14, 2018
installation Restore images with latest tag test (#1269) Oct 15, 2018
kyma-installer Local installation on kyma installer (#1182) Oct 10, 2018
resources Adding a possibility to skip SSL certificate verification in Connecto… Oct 15, 2018
tests Add more logging when ns deletion fails to work (#1206) Oct 15, 2018
tools Bump stability checker version (#1268) Oct 15, 2018
.dockerignore Added dockerignore file (#1194) Oct 9, 2018
.gitignore Generate changelog during release pipeline (#1040) Oct 5, 2018
CODEOWNERS Add codeowners for gateway subchart (#1264) Oct 15, 2018
CODE_OF_CONDUCT.md Initialize repository Jul 24, 2018
CONTRIBUTING.md Add project structure and development section to README.md (#163) Aug 21, 2018
Jenkinsfile Fix pipeline syntax issue (#1144) Oct 5, 2018
LICENSE Initialize repository Jul 24, 2018
NOTICE.md Initialize repository Jul 24, 2018
README.md Add GoReport badge (#444) Oct 15, 2018
azure.Jenkinsfile Jenkins notification move to slack channel c4core-kyma-ci-force (#494) Sep 5, 2018
ci.Dockerfile Local installation on kyma installer (#1182) Oct 10, 2018
governance.Jenkinsfile Enable external links validation on PRs (#1075) Oct 9, 2018
logo.png Initialize repository Jul 24, 2018
milv.config.yaml Update link in `alert-rules` Readme.md and and update milv.config.yaml ( Oct 11, 2018
orchestrator.Jenkinsfile Add istio-kyma-patch back (#1085) Oct 11, 2018
release.Jenkinsfile Add istio-kyma-patch back (#1085) Oct 11, 2018


Go Report Card


Kyma allows you to connect applications and third-party services in a cloud-native environment. Use it to create extensions for the existing systems, regardless of the language they are written in. Customize extensions with minimum effort and time devoted to learning their configuration details.

Go to the Kyma project website to learn more about the product, its features, and components.


Install Kyma locally and on a cluster.


Kyma comes with the ready-to-use code snippets that you can use to test the extensions and the core functionality. See the list of existing examples in the examples repository.


Develop on your remote repository forked from the original repository in Go. See the example that uses the ui-api-layer project located in the components directory but applies to any Go project. This set of instructions uses the recommended git workflow and the general contribution flow. Read also the CONTRIBUTING.md document that includes the contributing rules specific for this repository.

Follow these steps:

NOTE: The example assumes you have the $GOPATH already set.

  1. Fork the repository in GitHub.

  2. Clone the fork to your $GOPATH workspace. Use this command to create the folder structure and clone the repository under the correct location:

git clone git@github.com:{GitHubUsername}/kyma.git $GOPATH/src/github.com/kyma-project/kyma

Follow the steps described in the git-workflow.md document to configure your fork.

  1. Install dependencies.

Go to the main directory of the project in your workspace location and install the required dependencies:

$ cd components/ui-api-layer
$ dep ensure -vendor-only
  1. Build the project.

Every project runs differently. Follow instructions in the main README.md document of the given project to build it.

  1. Create a branch and start to develop.

Do not forget about creating unit and acceptance tests if needed. For the unit tests, follow the instructions specified in the main README.md document of the given project. For the details concerning the acceptance tests, go to the corresponding directory inside the tests directory. Find the information on how to run changes on the cluster without a Docker image in the Develop a service locally without using Docker document.

NOTE: For more details about testing, go to the Testing Kyma document.

  1. Test your changes.

Project structure

The repository has the following structure:

  ├── .github                     # Pull request and issue templates             
  ├── components                  # Source code of all Kyma components                                                
  ├── docs                        # Documentation source files
  ├── installation                # Installation scripts     
  ├── resources                   # Helm charts and Kubernetes resources for the Kyma installation
  ├── tests                       # Acceptance tests
  └── tools                       # Source code of utilities used, for example, for the installation and testing