Skip to content

kube-apiserver 1.16+ complains that CiliumNode CRD is non-strucutural #13192

@christarazi

Description

@christarazi
$ kubectl get crds ciliumnodes.cilium.io -o yaml

status:
  acceptedNames:
    kind: CiliumNode
    listKind: CiliumNodeList
    plural: ciliumnodes
    shortNames:
    - cn
    - ciliumn
    singular: ciliumnode
  conditions:
  - lastTransitionTime: "2020-09-16T21:46:24Z"
    message: 'spec.validation.openAPIV3Schema.type: Required value: must not be empty
      at the root'
    reason: Violations
    status: "True"
    type: NonStructuralSchema
  - lastTransitionTime: "2020-09-16T21:46:24Z"
    message: the initial names have been accepted
    reason: InitialNamesAccepted
    status: "True"
    type: Established
  storedVersions:
  - v2

Cilium version: 1.8.3, not master
K8s version: 1.16+

Steps to reproduce:

  1. Deploy Cilium 1.8.3 on a K8s 1.16 environment
  2. Run command from above

Metadata

Metadata

Assignees

Labels

area/k8sImpacts the kubernetes API, or kubernetes -> cilium internals translation layers.kind/bugThis is a bug in the Cilium logic.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions