Installing a tertiary Administration Console is not supported. You can install only primary and secondary Administration Consoles.
Customizing the path of the log files is not supported.
Combining components (Identity Server, Access Gateway, or Analytics Server) from various platforms is not supported. For example, you cannot use Identity Server deployed on Docker environment with Access Gateway deployed on a non-docker environment.
The release name used in one namespace cannot be used in another namespace. In a particular namespace, each cluster must be created as a separate release. The release name is a value that you specify in the Helm install or upgrade command.
If the release name contains many characters, the secondary Administration Console pod can go into an error state.
If you scale down any pod while upgrading to a new version, the deleted pod's persistent volume does not bind to the pod on performing a rollback.
Upgrading the Kubernetes cluster to a later version after installing Access Manager disrupts the Access Manager setup.
If Administration Console and device pods restart after an unexpected crash and if Administration Console is unable to restart, Identity Server pods, and Access Gateway pods will also be in the waiting state.
Converting a secondary Administration Console into a primary console is not supported.
In cloud deployments, such as EKS or AKS, upgrading a Kubernetes cluster is not supported.