Can't use `kubectl explain` on nodes.nodebalancer.linode.upbound.io

Open

#21 opened on Sep 18, 2023 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language: Go
Stars: 14
Forks: 13
Avg merge: 10h 32m
Merged PRs (30d): 2

Description

I can't use the `kubectl explain` command on nodes.nodebalancer.linode.upbound.io.

Installed version of the provider is v0.0.12

```console
$ kubectl get crd | grep linode | awk '{print $1}' | xargs -i sh -c "echo explaining {}; kubectl explain {}" | grep "error\|explaining"
explaining accesscontrols.database.linode.upbound.io
explaining buckets.objectstorage.linode.upbound.io
explaining clusters.lke.linode.upbound.io
explaining configs.instance.linode.upbound.io
explaining configs.nodebalancer.linode.upbound.io
explaining devices.firewall.linode.upbound.io
explaining disks.instance.linode.upbound.io
explaining domains.domain.linode.upbound.io
explaining firewalls.firewall.linode.upbound.io
explaining images.image.linode.upbound.io
explaining instances.instance.linode.upbound.io
explaining ips.instance.linode.upbound.io
explaining ipv6ranges.ipv6.linode.upbound.io
explaining keys.objectstorage.linode.upbound.io
explaining mysqls.database.linode.upbound.io
explaining nodebalancers.nodebalancer.linode.upbound.io
explaining nodes.nodebalancer.linode.upbound.io
error: field "nodebalancer" does not exist
explaining objects.objectstorage.linode.upbound.io
explaining postgresqls.database.linode.upbound.io
explaining providerconfigs.linode.upbound.io
explaining providerconfigusages.linode.upbound.io
explaining rdns.rdns.linode.upbound.io
explaining records.domain.linode.upbound.io
explaining sharedips.instance.linode.upbound.io
explaining sshkeys.sshkey.linode.upbound.io
explaining stackscripts.stackscript.linode.upbound.io
explaining storeconfigs.linode.upbound.io
explaining tokens.token.linode.upbound.io
explaining users.user.linode.upbound.io
explaining volumes.volume.linode.upbound.io
```

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Research direction

Start by reproducing the reported kubectl explain command for nodes.nodebalancer.linode.upbound.io and inspect the generated CRD schema for that resource. Compare it with the other Linode CRDs listed in the output, then verify that kubectl explain no longer reports that the nodebalancer field is missing.

Written by the indexing model from the issue text.

Assessment

Tech stack: go, kubernetes
Domain: cloud, infrastructure
Issue type: Bug
Difficulty: 3/5
Estimated time: 1-2 days
Activity status: Stale
Clarity: Mostly clear
Newbie friendliness: 45/100