fix: Use crd v1beta1 if kubernetes doesn't support v1

[tolusha]

Signed-off-by: Anatolii Bazko abazko@redhat.com

What does this PR do?

Use crd v1beta1 if kubernetes doesn't support v1

What issues does this PR fix or reference?

eclipse-che/che#19648

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[codecov-commenter]

Codecov Report

Merging #1193 (c0e99ec) into main (c3b5a87) will increase coverage by 0.02%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##             main    #1193      +/-   ##
==========================================
+ Coverage   10.26%   10.28%   +0.02%     
==========================================
  Files          60       60              
  Lines        6032     6035       +3     
  Branches     1016     1016              
==========================================
+ Hits          619      621       +2     
- Misses       5413     5414       +1     

Impacted Files	Coverage Δ
src/commands/server/deploy.ts	0.00% <0.00%> (ø)
src/commands/server/update.ts	0.00% <0.00%> (ø)
src/tasks/installers/operator.ts	0.00% <0.00%> (ø)
src/common-flags.ts	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c3b5a87...c0e99ec. Read the comment docs.

[mmorhun]

@tolusha it would be nice to have in the description why do we need to force CRD version.
As about flag name, does it make sense to have: --force-crd-version v1beta1? This way we will not need another flag if a new CRD version needs to be applied during the deploy process.

[mmorhun]

Agree, this way is better than your previous and suggested by me.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mmorhun, tolusha

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

[openshift-ci]

@tolusha: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/v8-chectl-e2e-operator-installer	156013c	link	/test v8-chectl-e2e-operator-installer
ci/prow/v7-chectl-e2e-olm-installer	156013c	link	/test v7-chectl-e2e-olm-installer

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.