bug: vcluster version too old for OpenShift

[MikeSpreitzer]

Describe the bug

I tried installing kubestellar v0.29.0 in an OpenShift 4.19 cluster.
Lots of pods in its1 will not run. Here is an example of one.

bash-5.3$ kubectl events --for pod/coredns-b5b5c4c6f-g99q6 -n kube-system
LAST SEEN              TYPE      REASON      OBJECT                        MESSAGE
64s (x17 over 6m47s)   Warning   SyncError   Pod/coredns-b5b5c4c6f-g99q6   Error syncing to physical cluster: admission webhook "policyeval.stackrox.io" denied the request: 
The attempted operation violated 1 enforced policy, described below:

Policy: Block images older than 1 year
- Description:
    ↳ Block deployments based on 1 year old images
- Rationale:
    ↳ Deployment based on 1 year old image, as such it is vulnerable to exploits due
      to the lack of security updates.
- Remediation:
    ↳ Re-deploy using newer up-to-date image.
- Violations:
    - Container 'coredns' has image created at 2023-02-06 18:31:00 (UTC)

Steps To Reproduce

See above.

Expected Behavior

vcluster ControlPlanes are usable on OpenShift.

Additional Context

No response

[MikeSpreitzer]

FYI, following are later minor releases of vcluster.

• v0.17.0: No breaking changes noted
• v0.18.0: no breaking changes noted
• v0.19.0: several architectural changes noted, none called breaking
• v0.20.0: breaking changes in vcluster.yaml
• v0.21.0: no breaking changes noted
• v0.22.0: no breaking changes noted
• v0.23.0, Feb '25: no breaking changes noted
• v0.24.0, Mar '25: no breaking changes noted
• v0.25.0, May '25: no breaking changes noted

[antedotee]

/assign
I will try to look into this.

[rishi-jat]

@antedotee still working on this ?

[antedotee]

You can try and raise a PR if you want.

[MikeSpreitzer]

• v0.26.0, June '25: no breaking changes noted
• v0.27.0: notes a critical bug
• v0.28.0: notes a critical bug
• v0.29.2, Sep '25: no breaking changes noted
• v0.30.0, Oct '25: no breaking changes noted