Description
Description
Remove the podTemplate field from the Operator's Keycloak CR. This will require some analysis beforehand of the impact, especially identifying critical use cases that are still not supported by the as first class citizen by the Keycloak CR.
Some more sub-issues for adding missing functionality might be added as a result of #40184.
Motivation
The podTemplate field was included in the Keycloak CR of the new Keycloak Operator since the very beginning. Its purpose was to provide an escape hatch for the users that would need to set some specific fields on the Keycloak pods that were not directly supported by the CR as first class citizen fields. Hence the podTemplate field was always considered only a workaround, and was never fully supported. This was often confusing to the users as they needed to rely on it but we could not guarantee we'll fix any issues related to it.
As the Operator evolved, more and more fields were added directly to the Keycloak CR making the podTemplate field not as needed as before. Though it still remains in the CR.
Additionally, removal of the podTemplate field would harden security by restricting access to what the user (that might not have permissions to manage namespace workloads directly) can do with the Pods.