Open BryanDollery opened 4 days ago
Hey @BryanDollery! It is not currently possible to run the redpanda operator without having the flux controllers installed. We're in the middle of making this possible via the UseFlux
flag that you've seen but it's not yet ready. We're aiming to have this available for users by the end of October.
Hey @BryanDollery! It is not currently possible to run the redpanda operator without having the flux controllers installed. We're in the middle of making this possible via the
UseFlux
flag that you've seen but it's not yet ready. We're aiming to have this available for users by the end of October.
Thanks @chrisseto - is this on a specific branch? I might be able to provide some feedback if I can test it pre-release.
Thank you for volunteering but we're not aiming to provide a usable pre-release form of this functionality.
I'm trying something undocumented :)
I want to deploy rp etc. with the operator, but I want to drive everything with kustomize and I really do not want flux in the middle of everything either.
I'm stuck on an error. I have the operator running, but after I've applied my first RedPanda object, during reconciliation, I get ArtifactFailed:
HelmRepository 'bus/operator is not ready
. I have got the redpanda charts repo registered with helm as 'operator'. I'm deploying all the rp resources to the 'bus' namespace. I have specified the name of the repo as 'operator' in my kustomization file, but I don't know why it's prepending the bus name to the helm repo reference, or even if that's what's breaking it. For all I know, this could be a red herring and it might not be possible to make it work without flux (I have seen an approved pr for a UseFulx flag, and maybe that's part of the solution? I don't know).In case it helps, here's the configuration I'm using:
kustomization.yaml
server.yaml
rp-operator-values.yaml