-
Notifications
You must be signed in to change notification settings - Fork 719
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
OpenAPIV3 structural schema violations #2349
Comments
I don't have these violations, could you give more details about the steps you took and the K8S version (client and server) you are using ? With K8S 1.12 / Client 1.17 and all-in-one at version
|
I'm running Server 1.15.4-gke2 and Client 1.14 with |
I can repro it in 1.15 and opened #2365 to make spinning up 1.15 a little easier. Same in Kibana:
and apm
|
So this comes from the us embedding the corev1.ServiceSpec which has and we would also need to specify Looks like this already landed in controller-tools, but just missed the last release: So we should be able to update to the next version of controller-tools and regenerate CRDs to resolve these. |
I went ahead and verified tried to verify that would fix it. Looks like it adds that marker at least. Here's the CRD generated against the master branch of controller-tools But it causes more issues due to adding some other ones related to server side apply that don't seem to be recognized in 1.15:
tl;dr I think we want to wait until the next release of controller-tools and revisit |
Similar issues, installed from helm chart eck-operator-1.5.0, server version v1.20.2, kubectl client v1.19.7 |
I just saw in a related issue an elastic engineer say that you could still spin up resources despite this issue, and I want to clarify that now that schema is out and gaining adoption, tools are starting to depend on it. The new experimental terraform kubernetes provider can spin up CRD resources, but it can't spin up ECK ones, because the schema is busted. |
I think this should be fixed by #4489 |
Some violations appear when describing the CRD with
kubectl describe crd elasticsearch
:The text was updated successfully, but these errors were encountered: