Description of problem:
Use kubectl with client validation enabled (tried 1.18.3 kubectl from upstream). Then
kubectl create -f
error: error validating "sttts-bot-deploymentconfig.yaml": error validating data: ValidationError(DeploymentConfig.spec.template.spec.containers.env.valueFrom.fieldRef): unknown field "name" in io.k8s.api.core.v1.ObjectFieldSelector; if you choose to ignore these errors, turn validation off with --validate=false
The server accepts the file using oc.
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.
*** Bug 1844957 has been marked as a duplicate of this bug. ***
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
I don't we'll be able to tackle this for 4.6, moving to 4.7.
It's still an important topic for us we want to pursue.
This is being actively worked on.
The LifecycleStale keyword was removed because the needinfo? flag was reset.
The bug assignee was notified.
It's still in-progress pushing over to 4.8.
I'll be revisiting in the next few weeks.
There are still API changes needed to make this over the hump :-( this won't make 4.8
Given the sig-cli and sig-apimachinery direction towards making validation optional, and the switch to openapi v3 I'm closing this as won't fix.