Merge branch 'kyma-project:main' into main

.github/package.json

@@ -10,6 +10,7 @@
   "changelog": {
     "repo": "kyma-project/kyma",
     "labels": {
+      "area/api-gateway": "Api Gateway",
       "area/application-connector": "Application Connector",
       "area/serverless": "Serverless",
       "area/cluster": "Cluster",

.github/workflows/github-release.yaml

@@ -7,10 +7,12 @@ jobs:
     environment:
       name: release
     container:
-      image: eu.gcr.io/kyma-project/test-infra/kyma-integration:v20211027-f0dd11ca
+      image: eu.gcr.io/kyma-project/test-infra/githubrelease:v20220916-ba91989d
     steps:
       - name: Checkout code
         uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
       - name: Check if not in master
         id: check_if_master
         shell: bash
@@ -33,14 +35,28 @@ jobs:
               echo "The ${NEXT_RELEASE} is already published on github. Stopping."
               exit 1
           fi
+      - name: Generate changelog
+        id: changelog
+        shell: bash
+        env:
+          CONFIG_FILE: .github/package.json
+          GITHUB_AUTH: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          git config --global --add safe.directory '*'
+          git config --global user.email "kyma-bot@kyma-project.io"
+          git config --global user.name "Kyma Bot"
+          export NEW_RELEASE_TITLE="$(cat "VERSION")"
+          export FROM_TAG=$(git describe --tags $(git rev-list --tags) --always | grep -F . | grep -v "-" | head -1)
+          /app/generate-release-changelog.sh
       - name: Make Kyma release
         id: make_release
         env:
           GOOGLE_APPLICATION_CREDENTIALS_JSON: ${{ secrets.GOOGLE_APPLICATION_CREDENTIALS }}
           GOOGLE_APPLICATION_CREDENTIALS: 'creds.json'
         run: |
-          echo $GOOGLE_APPLICATION_CREDENTIALS_JSON | base64 --decode > creds.json
-          /prow-tools/githubrelease -targetCommit=${{ github.ref }} \
+          echo $GOOGLE_APPLICATION_CREDENTIALS_JSON | base64 -d > creds.json
+          /githubrelease -targetCommit=${{ github.ref }} \
+                                    -kymaChangelog=.changelog/release-changelog.md \
                                     -githubRepoOwner=${{ github.event.repository.owner.login }} \
                                     -githubRepoName=${{ github.event.repository.name }} \
                                     -githubAccessToken=${{ secrets.GITHUB_TOKEN }} \

README.md

@@ -109,7 +109,7 @@ If you would like to join us and work together on the Kyma project, there are so
   - Downloading additional tools modules with the `go get` command
 
 - Kubernetes basic skillset:
-  - Understanding basic [Kubernetes architecture](https://shipit.dev/posts/kubernetes-overview-diagrams.html) and basic concepts such as: Namespace, Pod, Deployment, Secret, Config Map, Replica Set, Service, Custom Resource Definition, Kubernetes Control Loop; understanding Kubernetes Design Patterns such as sidecars and init containers
+  - Understanding basic [Kubernetes architecture](https://shipit.dev/posts/kubernetes-overview-diagrams.html) and basic concepts such as: Namespace, Pod, Deployment, Secret, ConfigMap, ReplicaSet, Service, CustomResourceDefinition, Kubernetes Control Loop; understanding Kubernetes Design Patterns such as sidecars and init containers
   - Using a kubeconfig file to connect to a cluster
   - Browsing cluster resources using `kubectl` commands and editing Kubernetes resources using Terminal
   - Applying YAML files to a cluster with Kubernetes resources

components/README.md

@@ -13,16 +13,16 @@ Every Kyma component resides in a dedicated folder which contains its sources an
 The component's name consists of a term describing the component, followed by the **component type**. The first part of the name may differ depending on the component's purpose.
 This table lists the available types:
 
-| Type | Description | Example|
+| Type | Description | Example |
 |---|---|---|
-| **controller** | A [Kubernetes Controller](https://kubernetes.io/docs/concepts/workloads/controllers/) which reacts to a standard Kubernetes resource or manages [Custom Resource Definition](https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/) resources. The component's name reflects the name of the primary resource it controls.| Function-controller |
-| **controller-manager** |A daemon that embeds all [Kubernetes Controllers](https://kubernetes.io/docs/concepts/workloads/controllers/) of a domain. Such an approach brings operational benefits in comparison to shipping all controllers separately. A `controller-manager` takes the name of the domain it belongs to. | - |
-| **operator** |is a [Kubernetes Operator](https://coreos.com/operators/) which covers the application-specific logic behind the operation of the application, such as steps to upscale a stateful application. It reacts on changes made to custom resources derived from a given [Custom Resource Definition](https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/). It uses the name of the application it operates. | telemetry-operator |
+| **controller** | A [Kubernetes Controller](https://kubernetes.io/docs/concepts/workloads/controllers/) which reacts to a standard Kubernetes resource or manages [CustomResourceDefinition](https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/) resources. The component's name reflects the name of the primary resource it controls. | Function-controller |
+| **controller-manager** | A daemon that embeds all [Kubernetes Controllers](https://kubernetes.io/docs/concepts/workloads/controllers/) of a domain. Such an approach brings operational benefits in comparison to shipping all controllers separately. A `controller-manager` takes the name of the domain it belongs to. | - |
+| **operator** | A [Kubernetes Operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) which covers the application-specific logic behind the operation of the application, such as steps to upscale a stateful application. It reacts on changes made to custom resources derived from a given [CustomResourceDefinition](https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/). It uses the name of the application it operates. | telemetry-operator |
 | **job** | A [Kubernetes Job](https://kubernetes.io/docs/tasks/job/) which performs a task once or periodically. It uses the name of the task it performs. |istio-patch-job (not renamed yet)|
 | **proxy** | Acts as a proxy for an existing component, usually introducing a security model for this component. It uses the component's name. | - |
-| **service** | Serves an HTTP/S-based API, usually securely exposed to the public. It uses the domain name and the API it serves.| - |
-| **broker** | Implements the [Open Service Broker](https://www.openservicebrokerapi.org/) specification to enrich the Kyma Service Catalog with the services of a provider. It uses the name of the provider it integrates with.| azure-broker |
-| **configurer** | A one-time task which usually runs as an [Init Container](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/) in order to configure the application.| - |
+| **service** | Serves an HTTP/S-based API, usually securely exposed to the public. It uses the domain name and the API it serves. | - |
+| **broker** | Implements the [Open Service Broker](https://www.openservicebrokerapi.org/) specification to enrich the Kyma Service Catalog with the services of a provider. It uses the name of the provider it integrates with. | azure-broker |
+| **configurer** | A one-time task which usually runs as an [Init Container](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/) in order to configure the application. | - |
 
 ## Development