Skip to content
This repository has been archived by the owner on Mar 6, 2024. It is now read-only.

Commit

Permalink
Add FAQ to Readme.md (#281)
Browse files Browse the repository at this point in the history
* Add FAQ to Readme.md

* Add links to other projects

* missing `
  • Loading branch information
Nico Schieder authored Mar 12, 2020
1 parent 269be4c commit def9a6e
Showing 1 changed file with 19 additions and 1 deletion.
20 changes: 19 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ KubeCarrier is an open source system for managing applications and services acro
- [Before you start](#before-you-start)
- [Pull Requests](#pull-requests)
- [Developer Documentation](developer-documentation)
- [FAQ](#faq)
- [Changelog](#changelog)

---
Expand All @@ -34,7 +35,7 @@ KubeCarrier is an open source system for managing applications and services acro

## Project Status

KubeCarrier is currently in alpha and is not ready for production use, the APIs are not yet final and breaking changes might be introduced in every release.
KubeCarrier is currently in early development and is not ready for production use, the APIs are not yet final and breaking changes might be introduced in every release.

## Features

Expand Down Expand Up @@ -537,6 +538,23 @@ Feedback and discussion are available on [the mailing list][11].
* We welcome pull requests. Feel free to dig through the [issues][1] and jump in.
## FAQ
### What`s the difference to OLM / Crossplane?
The [Operator Lifecycle Manager](https://github.com/operator-framework/operator-lifecycle-manager) from RedHat and [Crossplane](https://crossplane.io/) are both projects that manage installation, upgrade and deletion of Operators and their CustomResourceDefinitions in a Kubernetes cluster.
KubeCarrier on the other hand is just working with existing CustomResourceDefinitions and already installed Operators.
As both OLM and Crossplane are driven by CRDs, they can be combined with KubeCarrier to manage their configuration across clusters.
### What`s the difference to KubeFed - Kubernetes Federation?
The [Kubernetes Federation Project](https://github.com/kubernetes-sigs/kubefed) was created to distribute Workload across Kubernetes Clusters for e.g. geo-replication and disaster recovery.
It's intentionally low-level to work for generic workload to be spread across clusters.
While KubeCarrier is also operating on multiple clusters, KubeCarrier operates on a higher abstraction level.
KubeCarrier assigns applications onto single pre-determined Kubernetes clusters. Kubernetes Operators that enable these applications, may still use KubeFed underneath to spread the workload across clusters.
## Changelog
See [the list of releases][3] to find out about feature changes.
Expand Down

0 comments on commit def9a6e

Please sign in to comment.