Remove example from --runtime-extension flag in clusterctl

[cahillsf]

The clusterctl help text for the --runtime-extension options provides an example:
Runtime extension providers and versions (e.g. test:v0.0.1) to add to the management cluster.

Applying this option and example param results in the following error:
Error: failed to get configuration for the RuntimeExtensionProvider with name test. Please check the provider name and/or add configuration for new providers using the .clusterctl config

[cahillsf]

/kind feature
/area clusterctl

[sbueringer]

Sounds good!

/triage accepted

[cahillsf]

/assign cahillsf

[fabriziopandini]

I don't think we should expose test extensions without some docs about what they are and how to use them.

Frankly speaking, I would simply remove the example from the flag description, plus eventually add a note that clusterctl doesn't include any default runtime extensions.

Runtime extension providers and versions to add to the management cluster; please note that clusterctl doesn't include any default runtime extensions and thus it is required to use custom configuration files to register runtime extensions.

[sbueringer]

I'm fine either way. The reason I wrote sounds good is because I thought it is similar to CAPD.

[fabriziopandini]

The reason I wrote sounds good is because I thought it is similar to CAPD.

They are the kind the same, but for CAPD we have a quick start doc that tells users when and how to use CAPD (while we don't have an equivalent for test extensions).
Also, test extensions were mostly implemented to exercise some code path or as a code example, we never really focused on things like user experience or simulating use cases that could make sense for a final user, and thus I fear they might be confusing for people approaching it just because a flag uses it as an example value.

[sbueringer]

Makes sense and I agree. Let's keep it "more internal" for the time being.

[cahillsf]

sounds good, ill close out the existing PR and cut a new one with the doc/help text update suggested

[fabriziopandini]

/good-first-issue

[k8s-ci-robot]

@fabriziopandini:
This request has been marked as suitable for new contributors.

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-good-first-issue command.

In response to this:

/good-first-issue

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.

[avaneesh634]

/assign avaneesh634