---
# System prepended metadata

title: Rancher

---

# Rancher

1. GitOps - Fleet
    - Add KubeArmor deployment to github and manage it
    - https://fleet.rancher.io/gitrepo-structure
    
2. Change Branding in Configuration - Global Settings

3. UI Plugin
    - https://github.com/rancher/dashboard/blob/master/docusaurus/docs/guide/plugins.md
    - https://github.com/rancher/ui-plugin-examples
        - Need yarn patch to use upstream instead of local repo
        - API = https://localhost yarn dev


Talking to API - https://github.com/rancher/dashboard/blob/master/docusaurus/docs/code-base-works/api-resources-and-schemas.md

![](https://i.imgur.com/JpKgTqX.png)
Look into developing it as part of rancher/dashboard vs adding @rancher/shell as a dependency

Rancher API https://github.com/rancher/dashboard/blob/master/docusaurus/docs/code-base-works/api-resources-and-schemas.md#endpoints

1. Steve for management cluster
2. Kubernetes Proxy API to directly interact.

Adapter
- Interacts with rancher APIs
    - creates resources in local cluster
        - Resource contains
            - Old Policy => KSP
            - New Policy => Recommended Policy 
            - Apply state => False
        - How does the adapter know about old and new policies?
            - Interacts with proxy api

        - Change Apply State from UI
            - listen to these changes, and carry it to downstream clusters


- Per cluster UI for CRD