mxpc-cli apply-config fails to apply when managed namespace added using api
0
We have a kubernetes(mendix private cloud – connected mode) environment. We added a managed namespace in a Mendix cluster calling the createNamespaceManifest api '{"manifestVersion": "2.0.0", { "namespace": { "namespaceId":"81d1e78f-09dd-441a-8c3b-9a1737e3a270", "name":"my-namespace", "installationType":"Connected", "secret":"S0lqMEt2TGhDOVVsZEtUMQo=", "namespaceType":"managed" } }' The managed namespace is correctly added and appears in the Mendix portal Then when trying to install the namespace in the cluster executing mxpc-cli we systematically get an error : ./mxpc-cli apply-config --namespaceID 81d1e78f-09dd-441a-8c3b-9a1737e3a270 --secret KIj0KvLhC9UldKT1 --file ./mx_config_cli.yaml --global ./outils/manage-namespace/bin/mxpc-cli apply-config --namespaceID 81d1e78f-09dd-441a-8c3b-9a1737e3a270 --secret KIj0KvLhC9UldKT1 --file ./mx_config_cli.yaml --global -- Ensuring namespace exists... -- Ensuring Operator configuration exists... -- Ensuring Operator version exists... -- Ensuring Provisioner Service Account and Role configuration exists... -- Adding managed namespace to global Operator configuration... -- Restarting Mendix Agent... -- Restarting Mendix Operator.. -- Applying Kubernetes Secrets...Done! -- Applying Service Accounts...Done! -- Applying Storage Plans... -- Failed to apply Kubernetes Storage Plans: cloud portal returned invalid status code: 403 On the other hand If the managed namespace has been added to the cluster thru the UI (Mendix Platform - Cluster Details), then execution of mxpc-cli using the same configfile as above is successful. Any idea ?