-
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
📖 CAEP: Clusterctl redesign #1558
📖 CAEP: Clusterctl redesign #1558
Conversation
Welcome @fabriziopandini! |
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.
A couple of minor comments, otherwise 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.
Besides one minor nit it 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.
Gave a pretty good read at this proposal, it goes in the right direction and it's a great start.
/approve
1. Is based on a list of pre-configured provider repositories; it is possible to add new provider configurations to the list of known providers by using the clusterctl config file (see day 2 operations for more details about this). | ||
2. Assumes init will replace env variables defined in the components yaml read from provider repositories, or error out if such variables are missing. | ||
3. Assumes providers will be installed in the namespace defined in the yaml for installing components; at the time of this writing, this leads to having each provider in a dedicated namespace. This could be customized by specifying the --target-namespace flag. | ||
4. Assumes to not change the namespace each provider is watching on objects (settings defined in the yaml for installing components will be used); at the time of this writing, this leads to having each provider watching objects in all namespaces. Pending [1490](https://github.com/kubernetes-sigs/cluster-api/issues/1490) issue addressed, this could be customized by specifying the --watching-namespace flag. |
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.
If I understood this correctly, this is effectively saying that we assume that each manager (from CAPI, CAPA, CABPK) can only watch all namespaces for now? If so, we should make it more clear.
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. please let me know if the new version is more clear.
/assign |
/kind proposal |
Removing auto-approve so reviewers can manually indicate approval when it's ready. /approve cancel |
/approve cancel |
/approve cancel as per @ncdc comment |
|
||
Clusterctl consists of a single binary artifact implementing a CLI; the same features exposed by the CLI will be made available to other management tools via a client library. | ||
|
||
During provider installation, clusterctl internal pkg/lib is expected to access provider repositories and read the yaml file specifying all the provider components to be installed in the management cluster. |
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.
Maybe the internal library should be agnostic with respect of the source of this yaml and the cli or external tool should be the responsible of retrieving it. This would allow external tools to use other sources.
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 will let you specify alternative sources. Pulling from the provider repositories will be a default but not the only option. Does that address your comment?
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.
Yes I saw it below and commented more on this topic.
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.
@pablochacin just checking in - how are you feeling about this question?
/hold @detiber when you have time, please review & comment or GitHub-approve. Thanks! |
/lgtm |
e3c6aab
to
a5b0109
Compare
@ncdc fixed latest nits and squashed commits |
/lgtm Feel free to cancel the hold once ready to be merged. |
a5b0109
to
8c9d6a4
Compare
Approver list in the CAEP updated to match PR approvals |
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
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
@voor: changing LGTM is restricted to collaborators 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. |
FYI, as discussed in yesterday's community meeting, we'll be following lazy consensus and merging on Wednesday, November 6, or once all reviewers have approved the PR, whichever comes sooner. |
/lgtm Thanks for pushing this over the line @fabriziopandini !!! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: timothysc, vincepri 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 |
/hold cancel 🎉 |
Thanks to all the reviewers, this is a great milestone for the future of clusterctl 🎉 |
What this PR does / why we need it:
This PR adds the clusterctl redesign proposal
/assign @timothysc @frapposelli
/cc @ncdc @vincepri @detiber