Clean up charts (#12282)

* Clean up charts

* Cleanup old installation scripts

* Remove dead links

CONTRIBUTING.md

@@ -2,18 +2,6 @@
 
 To contribute to this project, follow the rules from the general [CONTRIBUTING.md](https://github.com/kyma-project/community/blob/main/CONTRIBUTING.md) document in the `community` repository.
 
-## Documentation types
-
-These are the main types of documents used in the project:
-
-* `NOTES.txt`- This document type is an integral part of Helm charts. Its content displays in the terminal window after installing the chart. It is not mandatory to include `NOTES.txt` documents for sub-charts because the system ignores these documents. Provide `NOTES.txt` documents for the Core components. Use the [template](https://github.com/kyma-project/community/blob/main/templates/resources/NOTES.txt) to create `NOTES.txt` documents.
-
-* `README.md` - This document type contains information about other files in the directory. Each main directory in this repository, such as `cluster` or `resources`, requires a `README.md` document. Additionally, each chart and sub-chart needs such a document. Add a `README.md` document when you create a new directory or chart. Use the [template](https://github.com/kyma-project/community/blob/main/templates/resources/chart_README.md) to create `README.md` documents.
-
-    > **NOTE:** `README.md` documents imported to Kyma with external charts don't have to follow the template.
-
-    Do not change the names or the order of the main sections in the `README.md` documents. However, you can create subsections to adjust each `README.md` document to the project's or chart's specific requirements. See the example of a [README.md](resources/core/README.md) document.
-
 ## Contribution rules
 
 Apart from the general rules described in the `community` repository, every `kyma` repository contributor must follow these basic rules:

components/iam-kubeconfig-service/README.md

@@ -1,5 +1,4 @@
-# IAM Kubeconfig Service
-
+# TO BE REMOVED
 ## Overview
 
 This project is a generator of configurations used in Kyma.
@@ -11,10 +10,6 @@ The following tools are required to set up the project:
 - [Go](https://golang.org)
 - [Docker](https://www.docker.com/)
 
-## Installation
-
-For installation use the dedicated [Helm chart](../../resources/iam-kubeconfig-service).
-
 ## Usage
 
 ### Configuration

components/permission-controller/README.md

@@ -1,10 +1,7 @@
-# Permission Controller
-
+# TO BE REMOVED
 ## Overview
 The Permission Controller listens for new Namespaces and creates a RoleBinding for the users of the specified group to the **kyma-admin** role within these Namespaces. The Controller uses a blocking mechanism which defines the Namespaces in which the users of the defined group are not assigned the **kyma-admin** role. When the Controller is deployed in a cluster, it checks all existing Namespaces and assigns the roles accordingly.
 
-Click [here](/resources/permission-controller) to access the Helm chart that defines the component's installation.
-
 ## Prerequisites
 
 - working Kubernetes cluster
@@ -35,4 +32,3 @@ Use the `run` formula to run the controller using local sources:
   make run EXCLUDED_NAMESPACES={EXCLUDED_NAMESPACES} SUBJECT_GROUPS={SUBJECT_GROUPS} STATIC_CONNECTOR={STATIC_CONNECTOR}
   ```
 
-See [this file](/resources/permission-controller/README.md#configuration) to learn how to use the environment variables.