operator rabbitmq-messaging-topology-operator (1.17.3)

[rabbitmq-ci]

Update operator rabbitmq-messaging-topology-operator (1.17.3)

[github-actions]

Dear @rabbitmq-ci,
Your forked procject is not rebased

To fix this issue please rebase or execute following commands:

git clone https://github.com/rabbitmq/community-operators /tmp/operators-repo
cd /tmp/operators-repo
git checkout origin/rabbitmq-messaging-topology-operator-1.17.3
git remote add upstream https://github.com/k8s-operatorhub/community-operators -f
git pull --rebase upstream main

[github-actions]

@Zerpet , please approve as you are original reviewer(s).

• To add more contributors to ci.yaml follow instruction here.
• To approve follow instruction here

[github-actions]

Dockerfile or bundle.Dockerfile is added/changed. Note that for security reasons none of these files are going to be used when building bundle. Docker file will be generated and all label information is taken from annotations.yaml.

[Zerpet]

/approve
/approved

[github-actions]

Dockerfile or bundle.Dockerfile is added/changed. Note that for security reasons none of these files are going to be used when building bundle. Docker file will be generated and all label information is taken from annotations.yaml.

[github-actions]

Dockerfile or bundle.Dockerfile is added/changed. Note that for security reasons none of these files are going to be used when building bundle. Docker file will be generated and all label information is taken from annotations.yaml.

[framework-automation]

/merge possible

[framework-automation]

/merge possible

[github-actions]

Current PR can be merged automatically, but there is missing authorized-changes label. One can find out more info here.

[github-actions]

Current PR can be merged automatically, but there is missing authorized-changes label. One can find out more info here.

[Zerpet]

/approve

[framework-automation]

/merge possible