K
Q

Unable to deploy emissary-ingress in local kubernetes cluster. Fails with `error validating data: ValidationError(CustomResourceDefinition.spec)`

10/4/2021

I'm trying to install emissary-ingress using the instructions here.

It started failing with error no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta". I searched and found an answer on Stack Overflow which said to update apiextensions.k8s.io/v1beta1 to apiextensions.k8s.io/v1 which I did. It also asked to use the admissionregistration.k8s.io/v1 which my kubectl already uses.

When I run the kubectl apply -f filename.yml command, the above error was gone and a new error started popping in with error: error validating data: ValidationError(CustomResourceDefinition.spec): unknown field "validation" in io.k8s.apiextensions-apiserver.pkg.apis.apiextensions.v1.CustomResourceDefinitionSpec;

What should I do next?

My kubectl version - Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.4", GitCommit:"3cce4a82b44f032d0cd1a1790e6d2f5a55d20aae", GitTreeState:"clean", BuildDate:"2021-08-11T18:16:05Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"windows/amd64"} Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.2", GitCommit:"8b5a19147530eaac9476b0ab82980b4088bbc1b2", GitTreeState:"clean", BuildDate:"2021-09-15T21:32:41Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"linux/amd64"}

minikube version - minikube version: v1.23.2 commit: 0a0ad764652082477c00d51d2475284b5d39ceed

EDIT:

The custom resource definition yml file: here

The rbac yml file: here

-- Kartikeya Gokhale
ambassador
kubectl
kubernetes
minikube

Similar Questions

Is it possible to create a configmap with an empty/blank key? If yes, what should be the expected behaviour with respect to the pods?
Horizontal Pod Autoscale unable to read metrics
Kubernetes and Docker: how to let two service to communicate correctly
Running Firecracker inside Docker
Kubernetes wait that apiVersion and kind exists before trying to apply resource using those

1 Answer

10/6/2021

The validation field was officially deprecated in apiextensions.k8s.io/v1. According to the official kubernetes documentation, you should use schema as a substitution for validation. Here is a SAMPLE code using schema instead of validation:

apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  name: crontabs.stable.example.com
spec:
  group: stable.example.com
  versions:
    - name: v1
      served: true
      storage: true
--->  schema:  <---
        # openAPIV3Schema is the schema for validating custom objects.
        openAPIV3Schema:
          type: object
          properties:
            spec:
              type: object
              properties:
                cronSpec:
                  type: string
                  pattern: '^(\d+|\*)(/\d+)?(\s+(\d+|\*)(/\d+)?){4}
#x27;
                image:
                  type: string
                replicas:
                  type: integer
                  minimum: 1
                  maximum: 10
-- Vicente Ayala
Source: StackOverflow