01-30-2023 06:15 AM
Our company are in the throes of purchasing Alfresco Content Services Enterprise and this will be deployed in our production environment.
Before we do so, I have been tasked with installing a proof of concept (PoC) version in our test AWS environment so ithought the Community Edition would be a good place to start.
The chosen method therefore being Helm with AWS EKS.
I'm working through the below Alfresco guide:
Already, I have created an EKS cluster and completed the tasks as set out in the documentation.
Now however, I am trying to deploy the external-dns service.
I run this command:
kubectl apply -f external-dns.yaml -n kube-system
But receive the following error message:
"resource mapping not found for name: "external-dns" namespace: "" from "external-dns.yaml": no matches for kind "ClusterRole" in version "rbac.authorization.k8s.io/v1beta1"
ensure CRDs are installed first
resource mapping not found for name: "external-dns-viewer" namespace: "" from "external-dns.yaml": no matches for kind "ClusterRoleBinding" in version "rbac.authorization.k8s.io/v1beta1"
ensure CRDs are installed first"
After some investigation, I believe this to be related to the rbac.authorization.k8s.io/v1beta1 API not being supported by Kubernetes versions newer than v1.22 (see below).
https://kubernetes.io/docs/reference/using-api/deprecation-guide/
Installed on the EC2 instance from which I am running these commands is:
eksctl 0.126.0
Helm v3.11.0
kubectl v1.24.7-eks...
So my guess is that the provided external-dns.yaml is referencing an out of date API.
Must I downgrade Kubernetes or is there a non-deprecated rbac.authorization.k8s.io API I can reference please?
And should I be following the wrong instructions or if there is anything on which I can elaborate, I'm happy to share and discuss.
Thanks
Explore our Alfresco products with the links below. Use labels to filter content by product module.