Raise Icinga Web version to 2.12.1 and Always pull image
#41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is required to have `Icinga Kubernetes Web` and a recent version of `Icinga Director`.
Although the `Icinga Web` image tags are coupled to release tags, several modules are included. We rebuild the image using the same latest release tag when modules get new release, so the image needs to be pulled again in such cases. Updates to the base image (OS) are also pushed using the same tags. This does not only apply to this image, so the pull policy for all other images should also be reconsidered.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The version raise is required to have
Icinga Kubernetes Webanda recent version of
Icinga Director.In addition, pull policy is changed to
Always:Although the Icinga Web image tags are coupled to release tags,
several modules are included. We rebuild the image using the same latest
release tag when modules get new release, so the image needs to be
pulled again in such cases. Updates to the base image (OS) are also
pushed using the same tags. This does not only apply to this image, so
the pull policy for all other images should also be reconsidered.