Update docs with later versions of Kyverno

[chipzoller]

What would you like to be added:

Update docs here with more recent information related to Kyverno.

Why is this needed:

The docs are outdated and refer to Kyverno 1.6. The current release of 1.10 (and some since then) does support the flags necessary to support the Karmada use case.

[RainbowMango]

Thanks @chipzoller for the reminder.
We will run a test against the newest version of Kyverno.

There is one thing that is not so convenient for the Karmada use case.
During the installation of Kyverno, we need to split the install yaml into two parts. one is the CRDs/namespaces/configmaps and the other is the components. Do you have any comments/suggestions about it?

PS:
Just took a glance at the latest install yamls, the it looks great that you have split the crd part from the installation yaml.

[chipzoller]

My suggestion would simply be provide the guidance in your documentation on which pieces users install where and not try and do the work for them, for simple maintenance reasons like this.

[RainbowMango]

Is it reasonable for Kyverno to split all these resources in install-latest-testing.yaml into some small pieces? Something like what we did on Karmada deployments.
For the Kyverno user experience, you still can have a unified yaml or shell script to deploy Kyverno in one-click.

[chipzoller]

Is it reasonable for Kyverno to split all these resources in install-latest-testing.yaml into some small pieces?

As we warn in our documentation, this manifest should never be used for anything other than experimentation or testing purposes. So, given that, no it doesn't make sense.