[bitnami/pinniped] Incorrect CRD versions in use

[darrenwatt]

Name and Version

bitnami/pinniped 1.3.10

What architecture are you using?

amd64

What steps will reproduce the bug?

While testing the bitnami/pinniped helm chart I ran into an issue which required some troubleshooting.

On a base install, check the federationdomains CRD with this command:

kubectl get crd federationdomains.config.supervisor.pinniped.dev -o 'jsonpath={.spec.versions[0].additionalPrinterColumns[?(@.name=="Status")]}'

Are you using any custom parameters or values?

None required.

What is the expected behavior?

We're expecting output to be: {"jsonPath":".status.phase","name":"Status","type":"string"}

What do you see instead?

Currently with the helm chart we get this incorrect response:

{"jsonPath":".status.status","name":"Status","type":"string"}

This response is incorrect for v0.27.0 of Pinniped.

Additional information

This doesn't appear to affect authentication, but means checking status of the federationdomain configuration shows a blank space instead of the actual status. It's worth getting the CRDs aligned in case any other functionality is affected.

I believe the Pinniped devs are looking to version their CRDs in future to help keep this aligned.

[github-actions[bot]]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[darrenwatt]

Bump.

[CeliaGMqrz]

Hi @darrenwatt,

Sorry for the delay.

Thanks for reporting this issue! I have created a PR to resolve this issue. Once the team reviews and merges it, the issue will be automatically closed.

Thanks for your patience.