rancher-operator

README

rancher-operator

rancher-operator aim to provide some new features not include directly in product.

Features

AutoProject

AutoProject add a new project (Rancher internal abstraction) in each cluster that your Rancher instance manage.

apiVersion: rancheroperator.barpilot.io/v1alpha1
kind: AutoProject
metadata:
  name: internal-ops
spec:
  projectSpec:
    displayName: Internal-Ops
    description: Project used by the ops team to give you the best kubernetes UX experience

AutoMultiClusterApp

AutoMultiClusterApp inject Multi-Cluster App in a project (based on label selector).

apiVersion: rancheroperator.barpilot.io/v1alpha1
kind: AutoMultiClusterApp
metadata:
  name: cert-manager
spec:
  multiClusterApp: cert-manager
  projectSelector: "autoproject/displayname==Internal-Ops"

Multi-Cluster App should already exists.

Status: ALPHA

Use it after tests and coffee.

Prerequisites

rancher-operator should be deployed in the same kubebernetes cluster where Rancher is deployed (local).

Use-Cases

For a KaaS team

A Kubernetes as a Service Team can add some default features to a cluster :

• log
• monitoring
• ingress
  • externalDNS
  • cert-manager

This add value to user with default "working" configuration.