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.

Sign up for GitHub

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

Jump to bottom

Operating CRDs should keep the API cache in sync #85

Open

jnummelin opened this issue Jan 4, 2019 · 0 comments

Contributor

jnummelin commented Jan 4, 2019

Now when e.g. removing a CRD and then trying to list resources everything borks, see kontena/pharos-cluster#949 for example.

This is caused by the API cache still having info on the CRDs defined API but the CRD itself is already gone.

Similar issues are likely happen if a CRD is updated.

See #13 and #14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment