frontend: Fix wrong apiVersion used when CRUDing a CustomResource

[damsien]

Summary

This PR fixes the "wrong apiVersion set on the editor" bug by actually checking the storage version of the CRD when getting the BaseObject.

Related Issue

Fixes #4223

Changes

• Added/Updated [component/file/logic]
• Fixed [bug/issue/typo]
• Refactored [code/module] for clarity/performance

Steps to Test

Prerequisites:
Having a CRD that have multiple versions installed on the cluster

Steps to reproduce the bug:

1. Go to the 'Custom Resources' page of that CRD
2. Click 'Create' to enter in the editor
3. See the apiVersion is correctly set to the actual storage version of the CRD

Screenshots (if applicable)

The CRD versions:

The apiVersion automatically set when creating the Custom Resource:

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: damsien
Once this PR has been reviewed and has the lgtm label, please assign sniok for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @damsien!

It looks like this is your first PR to kubernetes-sigs/headlamp 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/headlamp has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃