Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while installing the operator manifest #128

Closed
viveksinghggits opened this issue Feb 12, 2020 · 5 comments
Closed

Error while installing the operator manifest #128

viveksinghggits opened this issue Feb 12, 2020 · 5 comments
Labels
bug Something isn't working question Further information is requested

Comments

@viveksinghggits
Copy link
Contributor

We get below error, if we just follow the step that is mentioned in the README to install the operator

kubectl apply -f https://raw.githubusercontent.com/foundationdb/fdb-kubernetes-operator/master/config/samples/deployment.yaml -n fdb-err
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply
role.rbac.authorization.k8s.io/fdb-kubernetes-operator-manager-role created
rolebinding.rbac.authorization.k8s.io/fdb-kubernetes-operator-manager-rolebinding created
deployment.apps/fdb-kubernetes-operator-controller-manager created
The CustomResourceDefinition "foundationdbclusters.apps.foundationdb.org" is invalid: metadata.annotations: Too long: must have at most 262144 characters

It seems the resource manifest is too long.

@brownleej
Copy link
Member

Ah, you're right. I think the addition of the pod spec to the CRD caused it to get too long for kubectl apply to handle. There's a similar issue on the kubebuilder repo: kubernetes-sigs/kubebuilder#1140

@viveksinghggits
Copy link
Contributor Author

@brownleej there seems to be another issue, if I just kubectl apply the manifests that are mentioned in the README, we get the error in the operator pod saying its not able to list the pods. I think you might wanna look at that as well.

@brownleej
Copy link
Member

Can you clarify which manifests you are installing? I would expect the deployment.yaml to hit the issue you described above with the annotation length. Absent that manifest, you wouldn't have the operator installed at all, unless you installed it through some other means, which could cause the permissions issue you're seeing.

@brownleej brownleej added bug Something isn't working question Further information is requested labels Feb 15, 2020
@viveksinghggits
Copy link
Contributor Author

I will post the details in some time.

@brownleej
Copy link
Member

I've made a change to remove the CRD from the sample deployment, and updated the README with new installation instructions. @viveksinghggits Can you see if you are able to install the operator based on the updated instructions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants