Hello,
Since the last time we created Kubernetes tracks (back in 1.8, 1.8 tracks for Kubernetes) the procedure for requesting them has been formalized as described in Process for aliases, auto-connections and tracks. As such, we need to get some votes from reviewers/architects and have a period of a few days for those votes to be cast.
You have my +1 as reviewer, based on the fact that Kubernetes has precedent in using tracks and we’re all aware of its release cadence which makes use of tracks consistent with how the feature is designed.
I’ll check again early next week to see if we have the required votes.
- Daniel