RuntimeSDK: Surface the usage of deprecated versions of a Runtime Hook

[sbueringer]

User Story

As an operator I would like to have a way to observe that a Runtime Extension uses a deprecated Runtime Hook version.

Detailed Description

Background information:

• Runtime Hooks can have multiple apiVersions just like regular API types
• When creating a new apiVersion of a Runtime Hook we can deprecate the old version
• Runtime Extension authors can still use the old version of the Runtime Hook, but they are expected to migrate to the new apiVersion before the old one is removed

Goal of this issue is to surface that an old Runtime Hook version is used, so that Runtime Extension authors are made aware of that they should migrate to using the new Runtime Hook version.

Anything else you would like to add:

Some ideas:

• We could surface it as condition on the ExtensionConfig during discovery
• We could potentially surface it as:
  • a warning via a ValidatingWebhook on ExtensionConfig
    • TBD how this would work given that we only have the information in status after discovery
  • a well known HTTP header
    • TBD on which HTTP call and how that would be noticed

Please note, we can already implement this, but it can only be used by users once we have multiple Runtime Hook versions.

/kind feature

[fabriziopandini]

/triage accepted

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[fabriziopandini]

/lifecycle frozen
/help

[k8s-ci-robot]

@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:

/lifecycle frozen
/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-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted