Skip to content

Commit

Permalink
Change name to CAPI Provider Operator
Browse files Browse the repository at this point in the history
  • Loading branch information
Warren Fernandes committed Jan 8, 2021
1 parent b4f2a79 commit efdf19d
Show file tree
Hide file tree
Showing 5 changed files with 10 additions and 9 deletions.
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: Management Cluster Operator
title: CAPI Provider Operator
authors:
- "@fabriziopandini"
- "@wfernandes"
Expand All @@ -16,11 +16,11 @@ see-also:
https://github.com/kubernetes-sigs/cluster-api/blob/master/docs/proposals/20191016-clusterctl-redesign.md
---

# Management cluster operator
# CAPI Provider operator

## Table of Contents

* [Management cluster operator](#management-cluster-operator)
* [CAPI provider operator](#capi-provider-operator)
* [Table of Contents](#table-of-contents)
* [Glossary](#glossary)
* [Summary](#summary)
Expand Down Expand Up @@ -625,10 +625,11 @@ The installation process managed by the operator is consistent with the
implementation underlying the `clusterctl init` command and includes the
following steps:
- Fetching the provider artifacts (the components yaml and the metadata.yaml
file)
- Applying image overrides, if any
- Replacing variables
- Applying the resulting yaml to the cluster
file).
- Applying image overrides, if any.
- Replacing variables in the infrastructure-components from EnvVar and
Secret.
- Applying the resulting yaml to the cluster.

As a final consideration, please note that
- The operator executes installation for 1 provider at time, while `clusterctl
Expand Down Expand Up @@ -671,7 +672,7 @@ Please note that:
configuration file; this should be changed in order to use in cluster
provider configurations.

![Figure 1](./images/management-cluster-operator/fig1.png "Figure for
![Figure 1](./images/capi-provider-operator/fig1.png "Figure for
upgrading provider without changing contract")
<div align="center">Upgrading providers without changing contract</div>
<br/>
Expand All @@ -682,7 +683,7 @@ If the new version of the provider does abide by a new version of the Cluster
API contract, it is required to ensure all the other providers in the
management cluster should get the new version too.

![Figure 2](./images/management-cluster-operator/fig2.png "Figure for
![Figure 2](./images/capi-provider-operator/fig2.png "Figure for
upgrading provider and changing contract")
<div align="center">Upgrading providers and changing contract</div>
<br/>
Expand Down

0 comments on commit efdf19d

Please sign in to comment.