bumped schema to v1.25.3 (#501)

[adietish]

fixes #501

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[lstocchi]

LGTM

[adietish]

@lstocchi, @jeffmaury: it's striking how much is removed with this bump:

The explanation is that many deprecated items were removed. The details can be read in the deprecation guide at kubernetes.io: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25

The v1.25 release will stop serving the following deprecated API versions:

• CronJob
• EndpointSlice
• Event
• HorizontalPodAutoscaler
• PodDisruptionBudget
• PodSecurityPolicy
• PodSecurityPolicy
• RuntimeClass

One could wonder if we should support multiple schema.
Thoughts?

[jeffmaury]

@lstocchi, @jeffmaury: it's striking how much is removed with this bump:

The explanation is that many deprecated items were removed. The details can be read in the deprecation guide at kubernetes.io: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25

The v1.25 release will stop serving the following deprecated API versions:

• CronJob
• EndpointSlice
• Event
• HorizontalPodAutoscaler
• PodDisruptionBudget
• PodSecurityPolicy
• PodSecurityPolicy
• RuntimeClass

One could wonder if we should support multiple schema. Thoughts?

We should support several Kubernetes versions and not only the last one.
In IntelliJ Tekton they removed some CRDs but I kept the schemas

[mohitsuman]

@adietish What's the status of this PR ? Should we merge this to main ?

[jeffmaury]

Is it still valid ?

[adietish]

The issue is, the PR isnt. The PR is badly incomplete. It is simply bumping the supported schema where support for multiple schema should be provided (not just the latest but query the cluster for supported ones and then provide a matching schema in the editor).
I'm closing this PR since it's outdated.