# Helm - Dynatrace Operator installations compatibility with OCP 3.11

**URL:** <https://community.dynatrace.com/t/helm-dynatrace-operator-installations-compatibility-with-ocp-3-11/19314>\
**Category:** Container platforms\
**Tags:** installation, openshift, kubernetes\
**Created:** [May 12, 2020, 5:33am UTC](https://community.dynatrace.com/t/helm-dynatrace-operator-installations-compatibility-with-ocp-3-11/19314 "2020-05-12T05:33:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![alberto-jesus\_1](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@alberto-jesus\_1](https://community.dynatrace.com/u/alberto-jesus_1)\
**Post date:** [May 12, 2020, 5:33am UTC](https://community.dynatrace.com/t/helm-dynatrace-operator-installations-compatibility-with-ocp-3-11/19314/1 "2020-05-12T05:33:33Z")

</div>

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/](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.

---

<div class="post-metadata">

**Author:** ![mreider](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/mreider/32/14971_2.png) [@mreider](https://community.dynatrace.com/u/mreider)\
**Post date:** [May 12, 2020, 11:30am UTC](https://community.dynatrace.com/t/helm-dynatrace-operator-installations-compatibility-with-ocp-3-11/19314/2 "2020-05-12T11:30:13Z")

</div>

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:

> **[1803163 – Allow more fields at root of CRD schema if status is enabled](https://bugzilla.redhat.com/show_bug.cgi?id=1803163)**

Red Hat fixed the bug here:

> <https://github.com/openshift/origin/pull/24540>
>
> 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:

> <https://github.com/Dynatrace/dynatrace-oneagent-operator/blob/v0.7.0/deploy/openshift.yaml#L487>

Hope that helps

Note: we are adding this to our help pages shortly.