Skip to content

Tracking issue for clusterctl v2 implementation #1729

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

Closed
59 of 62 tasks
fabriziopandini opened this issue Nov 7, 2019 · 5 comments
Closed
59 of 62 tasks

Tracking issue for clusterctl v2 implementation #1729

fabriziopandini opened this issue Nov 7, 2019 · 5 comments
Assignees
Labels
area/clusterctl Issues or PRs related to clusterctl lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@fabriziopandini
Copy link
Member

fabriziopandini commented Nov 7, 2019

Tracking issue for clusterctl v2 work

Initial work based on the clusterctl POC

POC code walkthrough: 1 and 2

IMPORTANT! Details about the following activity breakdown are available https://docs.google.com/document/d/1rLu1P7Bs6BJ1ZL6aOz3AAWGwQ9N8Q3hle7PC56G11t0/edit?usp=sharing

Potential code improvements/cleanups

Future work

  • Prototype interactive mode for allowing users to set "on-the-fly" the variables to be injected in the yaml for providers components or providers templates
  • Prototype a pluggable template system (vs supporting only variables substitution)
@vincepri
Copy link
Member

vincepri commented Nov 7, 2019

/milestone v0.3.0
/area clusterctl
/priority important-soon

@k8s-ci-robot k8s-ci-robot added this to the v0.3.0 milestone Nov 7, 2019
@k8s-ci-robot k8s-ci-robot added area/clusterctl Issues or PRs related to clusterctl priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Nov 7, 2019
@ncdc
Copy link
Contributor

ncdc commented Jan 10, 2020

/assign @fabriziopandini
for overall ownership 😄

@fabriziopandini
Copy link
Member Author

We are done for the upcoming RC, except eventually last minutes changes for the webhooks

/close
🎉 🎉 🎉 🎉 🎉

#2313, #2314 are small fixes, not blocking for the release.

Clusterctl adopts, E2E tests, and other minor improvements code/cleanup are shifting to the next round.

@k8s-ci-robot
Copy link
Contributor

@fabriziopandini: Closing this issue.

In response to this:

We are done for the upcoming RC, except eventually last minutes changes for the webhooks

/close
🎉 🎉 🎉 🎉 🎉

#2313, #2314 are small fixes, not blocking for the release.

Clusterctl adopts, E2E tests, and other minor improvements code/cleanup are shifting to the next round.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/clusterctl Issues or PRs related to clusterctl lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

4 participants