Hi,
there is a new update of the best approach about how to install Dynatrace in Openshift like Operator. It talks about using Helm package manager. I am missing a section on this page about minimal OCP version supported with Helm.
https://www.dynatrace.com/support/help/technology-support/cloud-platforms/openshift/other-deployments-and-configurations/understanding-openshift-deployment-strategies/
Looking for that information it seems that Helm is not supported for OCP 3.11 and Operator installation should be done as a regular one.
Have you used Helm for 3.11 OCP versions?
Thanks in advance.
Alberto.
Hi there. Make sure you are using Helm 3. It should work on OCP 3.11, though there is a bug prior to OCP 3.11.188 as documented here:
Red Hat fixed the bug here:
release-3.11 ← munnerz:crd-schema-type-at-root
opened 11:49AM - 14 Feb 20 UTC
This PR is a cherrypick from the upstream PR: https://github.com/kubernetes/kube… rnetes/pull/65357
We're specifically requesting this change be cherrypicked back to release-3.11 as it currently prevents a single set of CRD resources being compatible with OpenShift 3.11 whilst also being considered 'structural' in OpenShift 4.x (and newer Kubernetes versions).
Without this patch, users will see errors like:
```
Error from server (Invalid): error when creating "cert-manager-openshift-v0.13.0.yaml": CustomResourceDefinition.apiextensions.k8s.io "certificaterequests.cert-manager.io" is invalid: spec.validation.openAPIV3Schema: Invalid value: apiextensions.JSONSchemaProps{ID:""
...
ensions.JSONSchemaDefinitions(nil), ExternalDocs:(*apiextensions.ExternalDocumentation)(nil), Example:(*apiextensions.JSON)(nil)}: must only have "properties", "required" or "description" at the root if the status subresource is enabled
```
when installing CRDs that enable the `status` resource that (correctly) specify `type: object` at the root of their CRD schema.
See also: https://github.com/jetstack/cert-manager/issues/2200
This patch applied clean from the upstream PR. This is my first contribution to `origin` so please let me know if I need to make any changes to how I've submitted this 😄
/assign @sttts
And you can make things work properly (if you are on an earlier version) by deleting this line here:
Hope that helps
Note: we are adding this to our help pages shortly.