Project: KubeCarrier (App Definition and Development / Application Definition & Image Build)
File: README.md

This configuration is used within KubeCarrier's CLI and the KubeCarrier Operator to bootstrap and reconcile KubeCarrier installation, it's not meant for direct use. master/advanced/addons/). The addon is dependent on cert-manger, which can be installed as a separate addon located in the `cert-manager` subfolder. The KubeCarrier addon provides one config option: `SingleCluster` (boolean): If enabled, KubeCarrier will run in single-cluster mode, where the same cluster will run KubeCarrier Control Plane as well as act as a service cluster. For the cert-manger addon: ```yaml apiVersion: kubermatic.k8s.io/v1 kind: Addon metadata: name: cert-manager namespace: cluster-bjg9qmhctj spec: cluster: kind: Cluster name: bjg9qmhctj uid: 30c13f8b-235e-4512-8673-d9b0f3a41f27 name: cert-manager ``` For the KubeCarrier addon (with `SingleCluster` mode enabled and a dependency on cert-manager CRD): ```yaml apiVersion: kubermatic.k8s.io/v1 kind: Addon metadata: name: kubecarrier namespace: cluster-bjg9qmhctj spec: cluster: kind: Cluster name: bjg9qmhctj uid: 30c13f8b-235e-4512-8673-d9b0f3a41f27 name: kubecarrier variables: {"SingleCluster":true} requiredResourceTypes: Group: cert-manager.io Version: v1alpha2 Kind: CertificateRequest ``` Update `kustomization.yaml` with desired image name and tag. After changing, run: ```shell script kustomize build . > kubecarrier/operator.yaml ``` See the for instructions on how to enable the addon in your KKP installation. 12] on the . Thanks for taking the time to join our community and start contributing! Feedback and discussion are available on . Please familiarize yourself with the before contributing. See for instructions on the developer certificate of origin that we require. We welcome pull requests. Feel free to dig through the and jump in. The from RedHat and 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. The 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. See to find out about feature changes. Region API Aggregation Provide a single API to access and work with the object across multiple regions Project Bulward Integration Advanced multi-tenancy on Kubernetes. Enable the management of custom sub-roles for KubeCarrier Account. Client Operator Kubernetes Operator to enable the provisioning of new services, provided with KubeCarrier from within your own client Kubernetes cluster. Secret Management Credential propagation mechanism to utilize Kubernetes Secrets. Service Groups Combine multiple related APIs e.g.(EtcdClusters, EtcdBackups, EtcdRestores) into a group for easier discovery. Audit Logging Multi-Tenancy audit logging within KubeCarrier. UI TBD