Skip to content

Commit

Permalink
Update README.md after renaming (kyma-project#129)
Browse files Browse the repository at this point in the history
Update README.md
  • Loading branch information
jakobmoellerdev authored Aug 26, 2022
1 parent 79bd8c6 commit 2e677c0
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# kyma-operator
# lifecycle-manager

Kyma is the opinionated set of Kubernetes based modular building blocks that includes the necessary capabilities to develop and run enterprise-grade cloud-native applications. Kyma operator is a tool that manages the lifecycle of these components in your cluster.

# Architecture

The architecture of `kyma-operator` and component operators is based on Kubernetes controllers/operators. `kyma-operator` is a meta operator that coordinates and tracks the lifecycle of kyma components by delegating it to component operators.
The architecture of `lifecycle-manager` and component operators is based on Kubernetes controllers/operators. `lifecycle-manager` is a meta operator that coordinates and tracks the lifecycle of kyma components by delegating it to component operators.

Before you go further please make sure you understand concepts of Kubernetes API and resources. Recommended reading:
- [Kubebuilder book](https://book.kubebuilder.io/)
Expand All @@ -17,9 +17,9 @@ Some architecture decisions were derived from business requirements and experime

![](docs/assets/kyma-operator-architecture.svg)

`kyma-operator ` manages Clusters through the `Kyma` custom resource (CR). `Kyma` contains a desired state of all components in a cluster for a given Kyma Release.
`lifecycle-manager` manages Clusters through the `Kyma` custom resource (CR). `Kyma` contains a desired state of all components in a cluster for a given Kyma Release.

`kyma-operator` creates component custom resources and updates `Kyma`'s status subresource based on the observed status changes in the component custom resource (similar to a deployment tracking pods).
`lifecycle-manager` creates component custom resources and updates `Kyma`'s status subresource based on the observed status changes in the component custom resource (similar to a deployment tracking pods).

Component operators watch only their own custom resources and reconcile components in the target clusters to the desired state. These states are then aggregated in `Kyma` to reflect the cluster state.

Expand All @@ -40,4 +40,4 @@ spec:
- name: serverless
```

The creation of the custom resource triggers a reconciliation of kyma-operator, that creates 2 custom resources: `ServerlessComponent` and `IstioConfiguration` based on a template. These custom resources will trigger serverless-operator and istio-operator. When each component operator completes the installation it updates it's own resource status (`ServerlessComponent/status` and `IstioConfiguration/status`). Status changes trigger kyma-operator to update `Kyma` resource status and aggregate and combine the readiness condition of the cluster.
The creation of the custom resource triggers a reconciliation of kyma-operator, that creates 2 custom resources: `ServerlessComponent` and `IstioConfiguration` based on a template. These custom resources will trigger serverless-operator and istio-operator. When each component operator completes the installation it updates it's own resource status (`ServerlessComponent/status` and `IstioConfiguration/status`). Status changes trigger kyma-operator to update `Kyma` resource status and aggregate and combine the readiness condition of the cluster.

0 comments on commit 2e677c0

Please sign in to comment.