With Ansible 2.6, an updated k8s module has been made available that makes use of a dynamic python client. This provides greater power and flexibility (like acting on CustomResourceDefinitions as well as interacting with the aggregated API servers). With this change though, there are a couple of conveniences that were in k8s_raw that are no longer available. For instance, you used to be able to include the name and namespace (see k8s_raw examples) where you now must put them under the metadata section (see k8s examples).

I wanted to take a look through and highlight a few places that would likely need updating.

Looking at mysql-dc.yml.j2:

• name + namespace need to go under metadata (https://github.com/ansibleplaybookbundle/rhpam-apb/blob/master/roles/deploy-mysql/templates/mysql-dc.yml.j2#L3-L4)
• the ImageChange trigger likely needs to be updated (_from stood out to me). I don't recall exactly the changes here, if you were to take a deployed deployment config yaml (ie. oc get dc/mysql -o yaml) that would better tell you how this should be formatted. https://github.com/ansibleplaybookbundle/rhpam-apb/blob/master/roles/deploy-mysql/templates/mysql-dc.yml.j2#L15-L22 (also, maybe this is helpful? https://docs.openshift.com/container-platform/3.5/dev_guide/builds/triggering_builds.html#image-change-triggers)
• emptyDir: {} at https://github.com/ansibleplaybookbundle/rhpam-apb/blob/master/roles/deploy-mysql/templates/mysql-dc.yml.j2#L66

There are a few other places where I see the name and namespace needing to go under metadata:

• https://github.com/ansibleplaybookbundle/rhpam-apb/blob/master/roles/deploy-businesscentral/tasks/services.yml#L8-L9
• https://github.com/ansibleplaybookbundle/rhpam-apb/blob/master/roles/deploy-businesscentral/tasks/routes.yml#L8-L9

Another thing to note, is that openshift_raw is no longer needed now that we are using a dynamic client, it is all available with the k8s module.