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.
New issue
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
feat:An ability to override Kibana image URL in DA #345
base: main
Are you sure you want to change the base?
feat:An ability to override Kibana image URL in DA #345
Changes from 2 commits
e0afd6d
f7020fd
52680ff
c1b72fa
2cafdb4
22e9715
8a33912
3d19ed9
b01dee5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really am not a fan of this variable name. It should be consistent with the
kibana_image_reference
input, and namekibana_image_version
- thoughts @Ak-sky ?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right @ocofaigh, as this is specific to Kibana, and a user may confuse it with
elasticsearch_version
variable-terraform-ibm-icd-elasticsearch/solutions/standard/variables.tf
Line 49 in 15af9b4
@aatreyee2506, please rename
elasticsearch_full_version
tokibana_elasticsearch_full_version
and add this below URL -https://github.com/elastic/kibana?tab=readme-ov-file#version-compatibility-with-elasticsearch
to the
kibana_elasticsearch_full_version
variable description for the user as a reference.@ocofaigh, we had same previous discussions on this topic before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you end it with
_full_version
? The version here is the kibana image version (image tag). I know it has to match the Ealsticsearch version, but its I dont think it needs the word elasticsearch in it?If we are consistent with
kibana_image_reference
we should call itkibana_image_version
IMHOThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can use
kibana_image_version
, but below are the reasons why I added-_full_version
- because we needmajor.minor.patch
version number and not justmajor.minor
. Kibana and Elasticsearch versions must match exactly for major, minor, and patch versions to avoid runtime errors.elasticsearch
- because to get the full version of the deployed database (elastic search) which is required to deploy Kibana.Here is a reference which says-
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Ak-sky But kibana don't release image tags with
major.minor
format. All their tags aremajor.minor.patch
format:Also its actually a better practise to lock into a digest instead of a tag version (as they may not be static), so we need to support that too.
So if we breakdown what an image reference looks like with correct terminology, it looks like this:
[registry-url]/[namespace]/[image][:tag|@digest]
. So for kibana, that would be:docker.elastic.co
kibana
kibana
:8.15.4
OR
@sha256:0ba5cab0b781c3b2a242ef8b5f2544638fa9741fad03c218c58798c06c2bb175
With all this in mind, I think we should have 2 variables:
kibana_registry_namespace_image
with a default value ofdocker.elastic.co/kibana/kibana
kibana_image_digest
with a default value ofnull
. The variable description should say this:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is better and even if the user is going to use private registery, they can replace
kibana_registry_namespace_image
value.But from security review aspect we will ask the user to input the registry url as you suggested? then no need to set the default values?