## 6.4 Administration and Operations in the Kyma Environment
This is the managed offering of SAP BTP, Kyma runtime (based on the open-source project "Kyma"). The administrators of the Kyma environment take care of setting it up and make sure it is ready for developers to work with. Create your Kyma instance to build applications and extensions to SAP and third-party solutions, manage roles, have your Kubernetes objects backed up, and view metrics and logs.
##  Caution
Do not make changes in any Kyma-managed namespaces, the &lt;kube-system&gt; namespace, or to any resources marked with Do Not Edit . Changes to those resources could lead to exclusion or disruptions from the agreed SLA. If you decide to make changes despite this, consult support in advance, and proceed with caution.
## Creating a Kyma Instance [page 3125]
Set up a Kubernetes cluster with SAP BTP, Kyma runtime and use it to build applications and extensions to your SAP and third-party solutions.
## Managing Kyma Runtime Using the Provisioning Service API [page 3127]
The SAP Cloud Management service for SAP BTP (technical name: cis ) provides the Provisioning Service API to create and manage available environments. Use the Provisioning Service API to automatically manage and access SAP BTP, Kyma runtime.
## Available Plans in the Kyma Environment [page 3131]
Depending on your global account type, you have access to a different plan that specifies the cluster parameters for the Kyma environment.
## Provisioning and Updating Parameters in the Kyma Environment [page 3138]
You can configure the cluster parameters in the Kyma environment.
## Adding and Deleting a Kyma Module [page 3157]
To use a Kyma module, you must add it first. Use Kyma dashboard or Kyma CLI to do that. If you don't need the module anymore, delete it to save resources.
## Setting Your Module to the Unmanaged and Managed State [page 3159]
In some cases, for example, for testing, you may need to modify your module beyond what is supported by its configuration. By default, when a module is in the managed state, Kyma Control Plane governs its Kubernetes resources, reverting any manual changes during the next reconciliation loop. To modify Kubernetes objects directly without them being reverted, you must set the module to the unmanaged state. In this state, reconciliation is disabled, ensuring your manual changes are preserved.
## Access Kyma Application Logs [page 3161]
Get insights into your applications, microservices, and Functions by viewing the respective logs. To check out real-time logs immediately, use the Kubernetes functionalities - either in Kyma dashboard, or with kubectl.
## Kyma Environment Backup [page 3162]
## Kyma Modules' Sizing [page 3164]
The following tables show the resource consumption, such as memory, CPU, and storage, of Kyma modules.
## Change Storage Size in Kyma [page 3167]
If the amount of data for the applications in your Kyma environment grows, you can expand the storage size for your customer data by resizing the respective Persistent Volume Claim (PVC).
## Assigning Workloads to Worker Node Pools [page 3168]
In addition to the mandatory worker node pool existing in each Kyma runtime, you can add and configure custom worker node pools. These additional worker nodes are reserved for running your workloads with special computing requirements on optimized machines. To ensure your workload runs on the right worker node pool, assign workloads to particular worker nodes.
## Custom OpenID Connect Configuration [page 3170]
During SAP BTP, Kyma runtime provisioning or update, you can provide your custom Open ID Connect (OIDC) configuration as a list of oidc objects or as a single oidc object. Y ou can also have no OIDC configuration.