Deploying Orchestrator(v1.8) on AWS #15302
Replies: 4 comments 2 replies
-
Hi @oloruntoba-madamori , |
Beta Was this translation helpful? Give feedback.
-
Hi @oloruntoba-madamori, To resolve this issue, follow these steps: If your Kubernetes/EKS cluster is running version 1.27 or later and does not support the policy/v1beta1 API version for PodSecurityPolicy, ClusterRole, and CronJob, you will need to update your release manifests to use the policy/v1 API version instead. Here's how you can do it: Open your deployment manifests for PodSecurityPolicy, ClusterRole, and CronJob resources. By making this change, you will align your resources with the supported API version for Kubernetes/EKS version 1.27 and later. This should resolve the issue you are facing. Thanks, |
Beta Was this translation helpful? Give feedback.
-
@ShubhamTatvamasi please take a look if we need to update the scripts in 1.9 to avoid this issue. |
Beta Was this translation helpful? Give feedback.
-
Will target it for 1.9 and verify once the branch is cut. |
Beta Was this translation helpful? Give feedback.
-
Hello, I'm trying to deploy the orchestrator on aws and I ran into the following errors.
This is my first time deploying orc8r and I'm following the instructions on the official magma docs page for v1.8
I was able to successfully terraform apply the infrastructure and the secrets as specified by the instructions in the docs.
Running into this error when I try to install the orchestrator application.
Need help!! thanks.
Beta Was this translation helpful? Give feedback.
All reactions