The following provides important information related to Usage Engine 3.12:

Anchor

...

The following values have been removed from the Helm chart:

...

ingress-nginx-v4.*: The bundled ingress-nginx helm chart that was installed by setting ingress-nginx-v4.enabled=true has been removed. If you were using this, immediately after upgrading to 3.0.0, please install the Ingress NGINX controller helm chart on its own in order to secure a smooth upgrade. Example:

helm install my-ingress ingress-nginx/ingress-nginx --version 4.0.17 -f ingress-nginx-values.yaml

...

...

The default resources for the platform container have been removed. From now on it is an active choice to set resources if needed. The default resources used to be:

platform:
  resources:
    limits:
      memory: 2350Mi
    requests:
      memory: 256Mi

By default, this is now just:

platform:
  resources: {}

...

Also, if you are using your own service account(s) for your ECD(s), specified via the operator.common.ecd value, then you need to make sure that it has permissions to get and patch the pods/status resource.

kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: my-ecd-role
rules:
  - apiGroups: [""]
    resources: ["pods/status"]
    verbs: ["get", "patch"]

The default memory limits for the platform JVM have changed. What used to be:

jvmArgs:
  - XX:MaxDirectMemorySize=4096m
  - XX:MaxMetaspaceSize=256m
  - Xms256m
  - Xmx512m

Is now:

jvmArgs:
  - XX:MaxMetaspaceSize=512m
  - Xms256m
  - Xmx2g

Anchor
rollback rollback

Action Required for Rollback from 3.x to 2.x

If you need to perform a helm rollback from a 3.x version to a 2.x version, the existing EC Deployment needs to be patched after having run the helm rollback command.

...

The solution to this is to install the Ingress NGINX controller helm chart separately.

Anchor
dtk dtk

Agents Built Using DTK Can Only Be Used in Desktop Client

Currently the agents built using the Development Toolkit can only be used in the Desktop Client.