Prow: Use latest CRDs

The CRDs were pinned because of an upstream issue. It has been solved, so we can go back to using the latest. The upstream issue is documented here: kubernetes-sigs/prow#181 Signed-off-by: Lennart Jern <[email protected]>
metal3-io · Jan 9, 2025 · 91269d6 · 91269d6
1 parent 6d3818e
commit 91269d6
Showing 1 changed file with 1 addition and 2 deletions.
diff --git a/prow/README.md b/prow/README.md
@@ -451,8 +451,7 @@ You may also have to create a keypair with the Metal3 CI ssh key.
     # Create the CRDs. These are applied separately and using server side apply
     # since they are so huge that the "last applied" annotation that would be
     # added with a normal apply, becomes larger than the allowed limit.
-    # TODO: This is pinned for now because of https://github.com/kubernetes-sigs/prow/issues/181.
-    kubectl apply --server-side=true -f https://raw.githubusercontent.com/kubernetes-sigs/prow/e67659d368fd013492a9ce038d801ba8998b7d10/config/prow/cluster/prowjob-crd/prowjob_customresourcedefinition.yaml
+    kubectl apply --server-side=true -f https://github.com/kubernetes-sigs/prow/raw/main/config/prow/cluster/prowjob-crd/prowjob_customresourcedefinition.yaml
 
     # Deploy all prow components
     kubectl apply -k manifests/overlays/metal3