config-registry-cert config map is erased when tekton operator pod restarts

[lucienbanholzer]

Dear team,

In order to be able to pull images from our private registry I need to declare custom SSL certificates in configmap config-registry-cert.

The issue is when tekton-operator pod restarts this configmap resource is deleted (and a fresh one without my certificates is created).

I don't find any solution in tekton operator config to make it persistent.

Do you have a solution for this ?

Thanks a lot for your help,

BR

[lucienbanholzer]

Any idea ?

[vdemeester]

cc @jkandasa

This is "expected" behavior so far, as those configmap are managed by the operator. We probably need to add an option to configure this configmap from the operator 👼🏼

[jkandasa]

I just checked the code and sadly we do not have an option to ignore it in the current design 🙁
On operator pod restarts installersets reconciles and revert back the resources into it is original state.

[jkandasa]

/kind bug

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[vdemeester]

/remove-lifecycle stale

[vdemeester]

@jkandasa could we remove it entirely from they payload and let users create it on demand ? I wonder if pipeline fails or not if the configmap doesn't exists.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[vdemeester]

/remove-lifecycle stale

[jkandasa]

@lucienbanholzer Now it is possible with additional field options: https://tekton.dev/vault/operator-main/tektonconfig/#additional-fields-as-options available from v0.68.0 release.

example:

apiVersion: operator.tekton.dev/v1alpha1
kind: TektonConfig
metadata:
  name: config
spec:
  pipeline:
    options:
      disabled: false
      configMaps:
        config-registry-cert:
          data:
            # your data

Can you please let me know, if something not clear?