This is a...
Proposed Solution:
Could you please use the "new syntax" first and then (if still needed) add the older syntax? That would be great. Thanks.
Page to Update:
https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
1.10
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle rotten
@rdxmb please help me understand what you mean by _use the "new syntax" first_ ? is there any example in the docs you mentioned ?
@DanyC97
The docs in https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#init-containers-in-use start with the example on version 1.5 - and then below adding 'There is a new syntax in Kubernetes 1.6'
I suggest just to switch the two parts.
perfect thank you @rdxmb !
since we are on 1.14 my view would be to drop the old syntax and only use the new one.
@zacharysarah @cody-clark thoughts ?
/assign
Most helpful comment
perfect thank you @rdxmb !
since we are on 1.14 my view would be to drop the old syntax and only use the new one.
@zacharysarah @cody-clark thoughts ?