what's the difference between the office cloudnative-pg and noobaa forked cloudnative-pg?

[lzw06061139]

There is a option: --use-cnpg-api-group
Use the original CloudNativePG API group for the installation manifests. Should be used when using an original
image of CloudNativePG.

If I install the noobaa system with the default images and enable option --use-cnpg-api-group, like that:

noobaa install -n noobaa --use-cnpg-api-group=true --debug-level='all'.  

This is part of the output, noobaa creates crds for cloudnativepg operator:

INFO[0000] CloudNativePG Operator Install:              
INFO[0000] ✅ Created: CustomResourceDefinition "backups.postgresql.cnpg.io" 
INFO[0000] ✅ Created: CustomResourceDefinition "clusterimagecatalogs.postgresql.cnpg.io" 
INFO[0000] ✅ Created: CustomResourceDefinition "clusters.postgresql.cnpg.io" 
INFO[0000] ✅ Created: CustomResourceDefinition "databases.postgresql.cnpg.io" 
INFO[0000] ✅ Created: CustomResourceDefinition "imagecatalogs.postgresql.cnpg.io" 
INFO[0000] ✅ Created: CustomResourceDefinition "poolers.postgresql.cnpg.io" 
INFO[0000] ✅ Created: CustomResourceDefinition "publications.postgresql.cnpg.io" 
INFO[0000] ✅ Created: CustomResourceDefinition "scheduledbackups.postgresql.cnpg.io" 
INFO[0000] ✅ Created: CustomResourceDefinition "subscriptions.postgresql.cnpg.io" 

But, at last, the noobaa system failed because the cnpg controller manger failed:

can't find the crd Cluster with version postgresql.cnpg.noobaa.io/v1, more info see below:

{"level":"error","ts":"2025-05-13T06:32:02.05177134Z","logger":"setup","msg":"unable to create controller","controller":"Cluster","error":"failed to get restmapping: no matches for kind \"Cluster\" in version \"postgresql.cnpg.noobaa.io/v1\"","stacktrace":"github.com/cloudnative-pg/machinery/pkg/log.(*logger).Error\n\t/home/runner/go/pkg/mod/github.com/cloudnative-pg/[email protected]/pkg/log/log.go:125\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/controller.RunController\n\tinternal/cmd/manager/controller/controller.go:227\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/controller.NewCmd.func1\n\tinternal/cmd/manager/controller/cmd.go:43\ngithub.com/spf13/cobra.(*Command).execute\n\t/home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:985\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\t/home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:1041\nmain.main\n\tcmd/manager/main.go:68\nruntime.main\n\t/opt/hostedtoolcache/go/1.23.6/x64/src/runtime/proc.go:272"}

My Question are:

1. why the default(noobaa forked cloudnativepg) cnpg controller manager checks Cluster with version postgresql.cnpg.noobaa.io, not the created postgresql.cnpg.io as showed in the log?
2. what is the difference between noobaa forked cloudnative pg and official cloudnative pg?

Thank you in adance!

[nimrod-becker]

@dannyzaken

[dannyzaken]

Hi @lzw06061139,

1. The flag --use-cnpg-api-group is intended to be used with an independent installation of upstream cloudnative-pg. In that case, the Noobaa CLI should not install the modified cnpg operator, and the expectation is that cnpg will already be installed in the cluster (v1.25 and up). This is a bug in the install command. I will fix it and make the help output more straightforward.
2. The only difference between the fork and the official cloudnative-pg is the API group. This is done to provide a consistent build of cnpg for use by noobaa, without creating any conflicts with possible installations of the official cloudnative-pg CRDs.

[lzw06061139]

I got it. Thank you for your reply.