Skip to content

CRD group name not following conventions #66

@faebr

Description

@faebr

Bug report criteria

  • This bug report is not security related, security issues should be disclosed privately via netbox operator maintainers.
  • Existing open issues have been checked and this is not a duplicate.

What happened?

The CRD group name is netbox.dev but it should be netbox.netbox.dev following the conventions and the data entered in the PROJECT file. When using the kubebuilder cli to add another API, one needs to manually adapt some things.

What did you expect to happen?

Change the group name in PROJECT (since netbox.netbox.dev seems weird ) and then adapt the CRD group.

How can we reproduce it (as minimally and precisely as possible)?

Running:
kubebuilder create api --group netbox --version v1 --kind Attachment
and:
make manifests
-> there are issues like the kustomization in crd pointing to a non-existant file

Netbox operator version

0.0.1-alpha

Netbox operator configuration (command line flags or environment variables)

Relevant log output

No response

Anything else we need to know?

No response

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions