ods-jenkins-shared-library icon indicating copy to clipboard operation
ods-jenkins-shared-library copied to clipboard

-cd namespace is not exported by release manager

Open clemensutschig opened this issue 4 years ago • 9 comments

Is your feature request related to a problem? Please describe. Suppose my integration tests (or any other component) need a secret or alike out of the -cd namespace - and for some reason the namespace vanishes, e.g. in a catastrophic failure - then we have no way to recover it based on bitbucket data.

All other components are exported during RM release runs, to ensure we have everything self contained, and restorable from bitbucket.

Describe the solution you'd like as part of the RM release build, -cd namespace exported, so that one can rebuild it from template.ymls

clemensutschig avatar Jan 20 '22 13:01 clemensutschig

@metmajer fyi as discussed

clemensutschig avatar Jan 20 '22 13:01 clemensutschig

I have an idea how it could work, but this work is blocked by a tailor bug (opendevstack/ods-core#1079) that needs to make it to on premise first :)

clemensutschig avatar Jan 20 '22 13:01 clemensutschig

@clemensutschig I think you are referring to the bug you opened yesterday, right? The one regarding exluded resource kinds? That made it into 1.3.4, which is not the version in the linked PR. I need to open a new PR for that new version.

On a side note, personally, I do not recommend to use the export feature more and more. I believe the best approach in general (though I know it does not fit neatly into the current architecture) would be to define the K8s resources upfront in code and evolve this as the CD namespace evolves. This is the direction that ODS pipeline takes (e.g. see the user installation), which is also due to the fact that ODS pipeline only supports Helm, which doesn't have export functionality. Tailor has, but it is very tricky to get "right", and the Tailor functionality has lots of edge cases that luckily do not appear too often, but they are there and will cause issues from time to time. Just throwing in my 2c ;)

michaelsauter avatar Jan 20 '22 14:01 michaelsauter

and you are totally right @michaelsauter - but I want to be rather save than sorry ... (at least for the time being).

ps - we need it in master and 4.x ... (only) 🗡️

clemensutschig avatar Jan 20 '22 14:01 clemensutschig

@clemensutschig Update done in master and 4.x.

michaelsauter avatar Jan 21 '22 07:01 michaelsauter

@s2oBCN / @albertpuente can we get this version(s) in-house on the dev cluster ... I can work with them?

clemensutschig avatar Jan 25 '22 08:01 clemensutschig

If you mean the dev cluster which uses bitbucket-dev, it is updated automatically every hour with the contents from github.

albertpuente avatar Jan 25 '22 09:01 albertpuente

the images as well? (this needs base and jenkins base and all agents then :))

clemensutschig avatar Jan 25 '22 10:01 clemensutschig

No, those need to be updated manually. Will do.

albertpuente avatar Jan 25 '22 10:01 albertpuente