You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now our OKD bundles have cert validity is only 30days but on OCP side we now have 1 year after patching KCMO/KAO images and generating a new release on quay.io . We should do same for OKD side, need to check with OKD community how those releases generated and try to create same script which we have for OCP to extend the cert with patched images.
The text was updated successfully, but these errors were encountered:
As per internal discussion with community member looks like OKD bits are completely generated from the CI ( no brew/koji involved) so to we have to generate those patched images locally and push it. we can discuss it here if there is some better solution for it.
As per internal discussion with community member looks like OKD bits are completely generated from the CI ( no brew/koji involved) so to we have to generate those patched images locally and push it.
Not sure what you mean by "locally", but the patched images could be built directly on quay, or through a github action, or even on brew/koji if we want to. They don't have to be built on a local machine and pushed.
Right now our OKD bundles have cert validity is only 30days but on OCP side we now have 1 year after patching KCMO/KAO images and generating a new release on quay.io . We should do same for OKD side, need to check with OKD community how those releases generated and try to create same script which we have for OCP to extend the cert with patched images.
The text was updated successfully, but these errors were encountered: