We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We use different image names for runtime-watcher in Dev and Prod registries:
lifecycle-manager/cmd/main.go
Lines 358 to 361 in 2ad71dd
Recently, when adapting build pipelines, we confused things up already. We should align the name and use the same for both registries.
Consistency and less prone to mistakes
runtime-watcher
-skr
No response
The text was updated successfully, but these errors were encountered:
Prio to be discussed. We may need to have it fixed before the next watcher release.
Sorry, something went wrong.
updated pipelines to build the image using the common name
watcher is now uniformely built with runtime-watcher name: https://github.com/kyma-project/runtime-watcher/blob/main/.github/workflows/build-image.yml#L41
updated code to use the image using the common name
implementation at KLM side is: #1868
See the comments wrt. to the issues with e2e tests
verify that it works e2e without -skr suffix
runtime watcher also needs to be updated to pass the new patch. PR for this is here: kyma-project/runtime-watcher#385
c-pius
Successfully merging a pull request may close this issue.
Description
We use different image names for runtime-watcher in Dev and Prod registries:
lifecycle-manager/cmd/main.go
Lines 358 to 361 in 2ad71dd
Recently, when adapting build pipelines, we confused things up already. We should align the name and use the same for both registries.
Reasons
Consistency and less prone to mistakes
Acceptance Criteria
runtime-watcher
(NO-skr
suffix)-skr
suffixFeature Testing
No response
Testing approach
No response
Attachments
No response
The text was updated successfully, but these errors were encountered: