-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📖 Document multi-tenancy contract #4074
📖 Document multi-tenancy contract #4074
Conversation
@fabriziopandini: GitHub didn't allow me to request PR reviews from the following users: MarcelMue. Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@@ -283,8 +283,6 @@ Provider authors should be aware of the following transformations that `clusterc | |||
* Enforcement of target namespace: | |||
* The name of the namespace object is set; | |||
* The namespace field of all the objects is set (with exception of cluster wide objects like e.g. ClusterRoles); | |||
* ClusterRole and ClusterRoleBinding are renamed by adding a “${namespace}-“ prefix to the name; this change reduces the risks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wfernandes this is a clusterctl internal; we should probably re-consider this during the implementation phase of the CAPI provider operator
- All the infrastructure provider are required to manage different credentials. | ||
- All the provider should deploy and run web-hook and with managers; | ||
please note this is the default in controllers generated with kubebuilder. | ||
- All the provider are required to create a `component.yaml` accordingly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My intent is to link documentation from #3985 here, depending on which PR is going to merge first
docs/book/src/developer/architecture/controllers/multi-tenancy.md
Outdated
Show resolved
Hide resolved
docs/book/src/developer/architecture/controllers/multi-tenancy.md
Outdated
Show resolved
Hide resolved
docs/book/src/developer/architecture/controllers/multi-tenancy.md
Outdated
Show resolved
Hide resolved
docs/book/src/developer/architecture/controllers/support-multiple-instances.md
Outdated
Show resolved
Hide resolved
docs/book/src/developer/architecture/controllers/support-multiple-instances.md
Outdated
Show resolved
Hide resolved
docs/book/src/developer/architecture/controllers/support-multiple-instances.md
Outdated
Show resolved
Hide resolved
docs/book/src/developer/architecture/controllers/support-multiple-instances.md
Outdated
Show resolved
Hide resolved
|
||
- In the Cluster API project, we are not going to include release a `component.yaml` file supporting this scenario; | ||
however it will be possible to create such file starting from the content of the `/config` folder. | ||
- clusterctl and the CAPI provider operator are not going to support deploying/managing multiple instances of the same provider. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- clusterctl and the CAPI provider operator are not going to support deploying/managing multiple instances of the same provider. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should state this in order to set clear expectations, unless you think this is clear from the previous statement
docs/book/src/developer/architecture/controllers/support-multiple-instances.md
Outdated
Show resolved
Hide resolved
docs/book/src/developer/architecture/controllers/support-multiple-instances.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great
@@ -0,0 +1,41 @@ | |||
# Support running multiple instances of the same provider | |||
|
|||
Up until v1alpha3, the need of supporting multiple credentials was addressed by running multiple |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might make sense to also add a note to https://github.com/kubernetes-sigs/cluster-api/blob/master/docs/book/src/developer/providers/v1alpha3-to-v1alpha4.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, PTAL
docs/book/src/developer/architecture/controllers/support-multiple-instances.md
Outdated
Show resolved
Hide resolved
LGTM after reading through it closely. |
/milestone v0.4.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/assign @detiber @CecileRobertMichon
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No blockers. LGTM.
docs/book/src/developer/architecture/controllers/support-multiple-instances.md
Outdated
Show resolved
Hide resolved
docs/book/src/developer/architecture/controllers/support-multiple-instances.md
Outdated
Show resolved
Hide resolved
7e6ed1f
to
bb54134
Compare
Latest comments addressed + squash |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
As per discussion on January 13th office hour meeting, this PR updates the cluster API book by:
Please note that the last point most probably does not represent yet the final state and it should be intended as a hook for the follow-up work for #4004.
/area clusterctl
/cc @wfernandes @vincepri @CecileRobertMichon @detiber @MarcelMue @yastij @randomvariable