Fix the arguments being passed to kubectl patch

[ian-howell]

• The kubectl patch will fail if the --type merge argument is not
  passed. It also requires for the patch manifest to be enclosed in single
  quotes.

• This also updates the k8s resource example

Resolves #1223

[CLAassistant]

All committers have signed the CLA.

[jessesuen]

LGTM!

@sarabala1979 can you check?

[jessesuen]

@ian-howell - @sarabala1979 explained that this is the intended behavior which I agree with. We want the default behavior to use strategic merge patching (which is the kubectl default). If we need other merge types, we can supply it as a different field.

The kubectl patch will fail if the --type merge argument is not
passed. It also requires for the patch manifest to be enclosed in single
quotes.

This should be working for strategic merge patching.

[jessesuen]

The intention is for patch to use strategic merge patching. If we need to support other styles patching, we should provide it as an option

[ian-howell]

@jessesuen I understand. I'll take a second look at this tomorrow to suss out why patches are failing in my workflows

[ian-howell]

I'm not sure I understand. Without the --type merge flag, I get the error

Error from server (UnsupportedMediaType):
the body of the request was in an unknown format - accepted media types include:
application/json-patch+json, application/merge-patch+json

@jessesuen @sarabala1979 Could one of you provide an example patch to be used with this feature?

EDIT: On further inspection, I've found that patching doesn't work for me because I am using Custom Resources. I'll go ahead and work on getting other patch strategies as an option, as per @jessesuen's suggestion

[ian-howell]

Closing in favor of #1269

[sarabala1979]

yes, correct. strategic-merge-patch is supported only standard resources
https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/