Mention new behavior of operator manifests (#4213)

README.md

@@ -39,71 +39,9 @@ objects like permissions, custom resources and corresponding StatefulSets.
 
 ### Installation
 
-> For install instructions on Openshift, head to the
+> For install instructions, head to the
 > [official help page](https://www.dynatrace.com/support/help/shortlink/full-stack-dto-k8)
 
-To create the namespace and apply the operator run the following commands
-
-```sh
-kubectl create namespace dynatrace
-kubectl apply -f https://github.com/Dynatrace/dynatrace-operator/releases/latest/download/kubernetes.yaml
-```
-
-If using `cloudNativeFullStack` or `applicationMonitoring` with CSI driver, the following command is required as well:
-
-```sh
-kubectl apply -f https://github.com/Dynatrace/dynatrace-operator/releases/latest/download/kubernetes-csi.yaml
-```
-
-A secret holding tokens for authenticating to the Dynatrace cluster needs to be created upfront. Create access tokens of
-type *Dynatrace API* and use its values in the following commands respectively. For
-assistance please refer
-to [Create user-generated access tokens](https://www.dynatrace.com/support/help/shortlink/token#create-api-token).
-
-The token scopes required by the Dynatrace Operator are documented on our [official help page](https://www.dynatrace.com/support/help/shortlink/full-stack-dto-k8#tokens)
-
-```sh
-kubectl -n dynatrace create secret generic dynakube --from-literal="apiToken=DYNATRACE_API_TOKEN" --from-literal="dataIngestToken=DATA_INGEST_TOKEN"
-```
-
-#### Create `DynaKube` custom resource for ActiveGate and OneAgent rollout
-
-The rollout of the Dynatrace components is governed by a custom resource of type `DynaKube`. This custom resource will
-contain parameters for various Dynatrace capabilities (OneAgent deployment mode, ActiveGate capabilities, etc.)
-
-> Note: `.spec.tokens` denotes the name of the secret holding access tokens.
->
-> If not specified Dynatrace Operator searches for a secret called like the DynaKube custom resource `.metadata.name`.
-
-The recommended approach is using classic Fullstack injection to roll out Dynatrace to your cluster, available as [classicFullStack sample](assets/samples/dynakube/v1beta2/classicFullStack.yaml).
-In case you want to have adjustments please have a look at [our DynaKube Custom Resource examples](assets/samples/dynakube).
-
-Save one of the sample configurations, change the API url to your environment and apply it to your cluster.
-
-```sh
-kubectl apply -f cr.yaml
-```
-
-For detailed instructions see
-our [official help page](https://www.dynatrace.com/support/help/shortlink/full-stack-dto-k8).
-
-## Uninstall dynatrace-operator
-
-> For instructions on how to uninstall the dynatrace-operator on Openshift,
-> head to the [official help page](https://docs.dynatrace.com/docs/setup-and-configuration/setup-on-k8s/guides/operation/update-uninstall-operator#uninstall-dynatrace-operator)
-
-Clean-up all Dynatrace Operator specific objects:
-
-```sh
-kubectl delete -f https://github.com/Dynatrace/dynatrace-operator/releases/latest/download/kubernetes.yaml
-```
-
-If the CSI driver was installed, the following command is required as well:
-
-```sh
-kubectl delete -f https://github.com/Dynatrace/dynatrace-operator/releases/latest/download/kubernetes-csi.yaml
-```
-
 ## Hacking
 
 See [HACKING](HACKING.md) for details on how to get started enhancing Dynatrace Operator.