Limitations of Centralized Policy Management

This page describes some limitations that apply to the current release of centralized policy management.

Limitation for Imported Clusters

The policy-management framework included in HPE Ezmeral Runtime Enterprise has not been tested for use in imported clusters.

Limitation for hpecp-bootstrap-argocd Deployment Object

If you register or deregister a policy after the cluster is created, you must make sure that none of the policies that you are registering or deregistering blocks the hpecp-bootstrap-argocd deployment object from scaling up. The container platform uses the hpecp-bootstrap-argocd deployment object to register and deregister policies.

This limitation applies only if you register or deregister a policy after the cluster is created. A workaround for this limitation is to log on to the Argo CD Server as described in Logging in to the Argo CD Server and add the policy directly to Argo CD. For instructions, see Creating Apps Via UI.

To make sure that none of the policies that you are registering or deregistering blocks the hpecp-bootstrap-argocd deployment object:
  1. Compare your policy definition (template and constraint objects) against the definition of the hpecp-bootstrap-argocd deployment to make sure the policy does not block deployment. To display the definition of the hpecp-bootstrap-argocd deployment, use one of these commands:
    kubectl get deployment hpecp-bootstrap-argocd -n hpecp-bootstrap -o json
    or
    kubectl describe deployment hpecp-bootstrap-argocd -n hpecp-bootstrap
  2. After comparing, modify or create your policy to allow the hpecp-bootstrap-argocd deployment to scale up. Or modify the hpecp-bootstrap-argocd deployment to conform to the policy you are creating.
  3. If necessary, edit the hpecp-bootstrap-argocd deployment using the following command:
    kubectl edit deployment hpecp-bootstrap-argocd -n hpecp-bootstrap