upstream fail of the configuration-as-code:1.55.1 plugin

[rubbercable]

Describe the bug

TL;DR

kubectl get pod
NAMESPACE     NAME                               READY   STATUS                  RESTARTS        AGE
default       jenkins-0                          0/2     Init:CrashLoopBackOff   8 (69s ago)     7m34s
[ ... ]
kubectl logs -f jenkins-0 -c init
[ ... ]
Plugin kubernetes:1.31.3 (via credentials:1087.v16065d268466) depends on configuration-as-code:1414.v878271fc496f, but there is an older version defined on the top level - configuration-as-code:1.55.1,
Plugin workflow-aggregator:2.6 (via credentials:1087.v16065d268466) depends on configuration-as-code:1414.v878271fc496f, but there is an older version defined on the top level - configuration-as-code:1.55.1,
Plugin git:4.10.2 (via credentials:1087.v16065d268466) depends on configuration-as-code:1414.v878271fc496f, but there is an older version defined on the top level - configuration-as-code:1.55.1

helm search repo --versions |grep jenkins/jenkins |head -3
jenkins/jenkins                         3.11.8          2.332.1     Jenkins - Build great things at any scale! The ...
jenkins/jenkins                         3.11.7          2.332.1     Jenkins - Build great things at any scale! The ...
jenkins/jenkins                         3.11.6          2.332.1     Jenkins - Build great things at any scale! The ...

helm upgrade --install jenkins jenkins/jenkins

Version of Helm and Kubernetes

- Helm: v3.8.0
- Kubernetes: v1.23.3

Chart version

3.11.8

What happened?

tested on kind, minikube, VMs(vagrant and lxd), k3d in last couple of days
1. helm repo add jenkins https://charts.jenkins.io
2. helm repo update
3. helm upgrade --install jenkins  jenkins/jenkins

the jenkins-0 init-container kept dying
...

What you expected to happen?

default jenkins-0 2/2 Ready 0 69s ago

How to reproduce it

see [section "What happened?"]

Anything else we need to know?

No response

[rubbercable]

changing the values.file

installPlugins:
[...]
    - configuration-as-code:1414.v878271fc496f

fixes this

[y0zg]

@rubbercable Do you know how to mitigate such errors? It seems this error could occur during jenkins restart

[dmitriko]

controller:
  installLatestPlugins: false

did help me

[timja]

Long ago resolved by automating updating of plugins