Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Implement a smoke test for clusterctl plugins #10219

Open
fabriziopandini opened this issue Feb 29, 2024 · 5 comments · May be fixed by #11950
Open

Implement a smoke test for clusterctl plugins #10219

fabriziopandini opened this issue Feb 29, 2024 · 5 comments · May be fixed by #11950
Assignees
@prashantrewar
Labels
area/clusterctl Issues or PRs related to clusterctl help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@fabriziopandini
Copy link
Member

What would you like to be added (User Story)?

As a developer I would like to change clusterctl with confidence
As a user I would like to have guarantee about clusterctl plugins

Detailed Description

We should implement a smoke test about clusterctl plugin, creating a foo plugin a checking that it is loaded and executed when running clusterctl foo

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature
/area clusterctl
/triage accepted

/help
@k8s-ci-robot
Copy link
Contributor

@fabriziopandini:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

What would you like to be added (User Story)?

As a developer I would like to change clusterctl with confidence
As a user I would like to have guarantee about clusterctl plugins

Detailed Description

We should implement a smoke test about clusterctl plugin, creating a foo plugin a checking that it is loaded and executed when running clusterctl foo

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature
/area clusterctl
/triage accepted

/help

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.

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. area/clusterctl Issues or PRs related to clusterctl triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Feb 29, 2024
@chrischdi chrischdi changed the title Implement a smoke test for clutsterctl plugins Implement a smoke test for clusterctl plugins Feb 29, 2024
@prashantrewar
Copy link

Hey @fabriziopandini I want to give it a try. Could you please help me and guide me on this issue?

@fabriziopandini
Copy link
Member Author

@prashantrewar thanks for volunteering!
I did not research the topic specifically but I think I would start doing something like:

@fabriziopandini
Copy link
Member Author

/assign @prashantrewar

@fabriziopandini
Copy link
Member Author

/priority important-longterm

@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 11, 2024
@dmvolod dmvolod linked a pull request Mar 10, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@prashantrewar prashantrewar

Labels
area/clusterctl Issues or PRs related to clusterctl help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

🌱 Implement a smoke test for clusterctl plugins dmvolod/cluster-api
3 participants
@fabriziopandini @k8s-ci-robot @prashantrewar