goharbor/harbor-operator

Tutorial is Broken

Opened this issue · 2 comments

OpenGLShaders commented

If you are reporting a problem, please make sure the following information are provided:

Expected behavior and actual behavior:
Following the tutorial I run: kubectl apply -f https://raw.githubusercontent.com/goharbor/harbor-operator/main/manifests/cluster/deployment.yaml
and get the following:

[resource mapping not found for name: "serving-cert" namespace: "harbor-operator-ns" from "https://raw.githubusercontent.com/goharbor/harbor-operator/main/manifests/cluster/deployment.yaml": no matches for kind "Certificate" in version "cert-manager.io/v1"
ensure CRDs are installed first, resource mapping not found for name: "selfsigned-issuer" namespace: "harbor-operator-ns" from "https://raw.githubusercontent.com/goharbor/harbor-operator/main/manifests/cluster/deployment.yaml": no matches for kind "Issuer" in version "cert-manager.io/v1"
ensure CRDs are installed first]
Error from server (Invalid): error when creating "https://raw.githubusercontent.com/goharbor/harbor-operator/main/manifests/cluster/deployment.yaml": CustomResourceDefinition.apiextensions.k8s.io "jobservices.goharbor.io" is invalid: metadata.annotations: Too long: must have at most 262144 bytes
Error from server (Invalid): error when creating "https://raw.githubusercontent.com/goharbor/harbor-operator/main/manifests/cluster/deployment.yaml": CustomResourceDefinition.apiextensions.k8s.io "redisfailovers.databases.spotahome.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes

Steps to reproduce the problem:
kubectl apply -f https://raw.githubusercontent.com/goharbor/harbor-operator/main/manifests/cluster/deployment.yaml

Versions:
Please specify the versions of following systems.

  • harbor operator version: latest
  • harbor version: latest
  • kubernetes version: v1.28.3

Additional context:

I'm using minikube for local development and testing.

Workaround

kubectl create -f https://raw.githubusercontent.com/goharbor/harbor-operator/main/manifests/cluster/deployment.yaml
seems to work.

ta2lor commented

I also have a same error problem, Do you have any progress for that? or using other one?

mattmattox commented

This is still broken but I was able to workaround this by adding the server-side flag to the apply command.

kubectl apply --server-side=true --force-conflicts -f https://raw.githubusercontent.com/goharbor/harbor-operator/main/manifests/harbor/deployment.yaml

Doc