Redpanda Operator: flag provided but not defined: -configurator-base-image

[josemanuelbadia]

Version & Environment

Redpanda version: 22.2.2, on kubernetes

• Kubernetes (use kubectl version):
  Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.5", GitCommit:"c285e781331a3785a7f436042c65c5641ce8a9e9", GitTreeState:"clean", BuildDate:"2022-03-16T15:51:05Z", GoVersion:"go1.17.8", Compiler:"gc", Platform:"darwin/amd64"}
  Server Version: version.Info{Major:"1", Minor:"23+", GitVersion:"v1.23.6", GitCommit:"", GitTreeState:"dirty", BuildDate:"", GoVersion:"go1.17.9", Compiler:"gc", Platform:"linux/amd64"}

What went wrong?

Manager pod fails with this error:
flag provided but not defined: -configurator-base-image Usage of /manager: -configurator-tag string Set the configurator tag (default "latest") -health-probe-bind-address string The address the probe endpoint binds to. (default ":8081") -kubeconfig string Paths to a kubeconfig. Only required if out-of-cluster. -leader-elect Enable leader election for controller manager. Enabling this will ensure there is only one active controller manager. -metrics-bind-address string The address the metric endpoint binds to. (default ":8080") -webhook-enabled Enable webhook Manager -zap-devel Development Mode defaults(encoder=consoleEncoder,logLevel=Debug,stackTraceLevel=Warn). Production Mode defaults(encoder=jsonEncoder,logLevel=Info,stackTraceLevel=Error) (default true) -zap-encoder value Zap log encoding (one of 'json' or 'console') -zap-log-level value Zap Level to configure the verbosity of logging. Can be one of 'debug', 'info', 'error', or any integer value > 0 which corresponds to custom debug levels of increasing verbosity -zap-stacktrace-level value Zap Level at and above which stacktraces are captured (one of 'info', 'error').

What should have happened instead?

On redpanda-operator/templates/deployment.yaml these flags arent recognized

#        - --configurator-base-image={{ .Values.configurator.repository }}
#        - --configurator-image-pull-policy={{ .Values.configurator.pullPolicy }}
#        - --cluster-domain={{ .Values.clusterDomain }}

commenting them out makes it work

How to reproduce the issue?

Install redpanda operator with helm and repo files using
helm install --namespace redpanda-system --create-namespace redpanda-system ./src/go/k8s/helm-chart/charts/redpanda-operator --values ./src/go/k8s/helm-chart/charts/redpanda-operator/values.yaml --version v22.2.2

Additional information

Please attach any relevant logs, backtraces, or metric charts.

JIRA Link: CORE-1030

[david-yu]

@josemanuelbadia Is this still outstanding, are you able to see if this works the newest version of Redpanda Operator?