Kubernetes docs: Replace static tables with the auto-generated tables

[Sgitario]

I found out that some properties were not synced between the content in the Kubernetes guide and the config-all page (which uses the auto generated table).

Let's use the auto-generated tables also in the Kubernetes guide, so we avoid having to maintain these properties, plus also having to explain the inner basic types (as it's already part of the auto generated table).

[Sgitario]

cc @geoand @iocanel

[Sgitario]

Not sure if we should delete the openshift part taking into account we have a separated guide for OpenShift: https://quarkus.io/guides/deploying-to-openshift

And perhaps we should move the knative part into a new guide too.
Let me know your thoughts about it.

[gsmet]

@iocanel could you have a look at this one?

[iocanel]

+100 on the idea. However, it's not clear to me who generates those files. I've seen in the past some related jbang scripts which seemed to convert Config object to adoc files. Do I remember correctly?

[Sgitario]

+100 on the idea. However, it's not clear to me who generates those files. I've seen in the past some related jbang scripts which seemed to convert Config object to adoc files. Do I remember correctly?

I'm unsure which tool is generating the adoc files from Config objects, but it's working fine so far.
I've just resolved the conflicts.

[iocanel]

+100 on the idea. However, it's not clear to me who generates those files. I've seen in the past some related jbang scripts which seemed to convert Config object to adoc files. Do I remember correctly?

I'm unsure which tool is generating the adoc files from Config objects, but it's working fine so far. I've just resolved the conflicts.

Ok, I'll take your word for it 😄

[iocanel]

LGTM

[gsmet]

@Sgitario @iocanel the files are generated during the build by the Quarkus extension plugin (if you don't skip the doc generation).