You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have files which belong to kubernetes deployments and files which patch those deployments. Obviously patches are not valid kubernetes deployments, they miss required fields.
Ideally I'd like to configure extension to recognize patches, however ignoring schema for patches is also fine for me.
My names are like deploy.yaml, deploy-name.yaml, deploy-name-patch.yaml. First two are valid kubernetes deployments, third is patch.
I tried to configure this extension in the following way:
This does not work for patches. It works correctly for deployments, but for patches both schemas are applied, schema none does not even exist, so it just does not work well.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have files which belong to kubernetes deployments and files which patch those deployments. Obviously patches are not valid kubernetes deployments, they miss required fields.
Ideally I'd like to configure extension to recognize patches, however ignoring schema for patches is also fine for me.
My names are like
deploy.yaml
,deploy-name.yaml
,deploy-name-patch.yaml
. First two are valid kubernetes deployments, third is patch.I tried to configure this extension in the following way:
This does not work for patches. It works correctly for deployments, but for patches both schemas are applied, schema
none
does not even exist, so it just does not work well.Beta Was this translation helpful? Give feedback.
All reactions