Skip to content

s3Instance CRD is not included in the kustomization.yaml #113

@weberc2

Description

@weberc2

Bonjour!

It looks like the config/default/kustomization.yaml references config/crd/kustomization.yaml, but the latter does not include all of the CRDs defined in the config/crd/bases/ directory (it only omits the S3Instance CRD). I can make a PR editing the kustomization, but I can't tell if this is generated by the operator framework or not.

Merci beaucoup :)


So far my workaround is to explicitly reference the CRD from my downstream kustomization.yaml:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
- github.com/InseeFrLab/s3-operator/config/default?ref=v0.12.0
- github.com/InseeFrLab/s3-operator/config/prometheus?ref=v0.12.0

  # As of v0.12.0 the s3instance CRD is excluded from the
  # config/crd/kustomization.yaml template--we have to include it explicitly
- https://raw.githubusercontent.com/InseeFrLab/s3-operator/v0.12.0/config/crd/bases/s3.onyxia.sh_s3instances.yaml


namespace: s3-operator

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions