-
Notifications
You must be signed in to change notification settings - Fork 723
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
Make helm charts consistent with how fields in spec
are handled. (kibana only)
#8192
Conversation
Signed-off-by: Michael Montgomery <[email protected]>
I think your approach is reasonable. I think it is key that we don't have breaking changes. I don't think there is any tolerance on the user side for breaking changes in Helm charts. |
Signed-off-by: Michael Montgomery <[email protected]>
Since this is the case, I'll mark this as ready for review to get additional feedback. ty. |
spec
are handled. (kibana only)spec
are handled. (kibana only)
@@ -13,25 +13,24 @@ labels: {} | |||
annotations: {} | |||
# key: value | |||
|
|||
spec: |
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.
should we add a comment saying this spec. is deprecated and config. is the preferred way to set these configs. Not sure what the right place is to add this comment
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.
@kvalliyurnatt I adjusted this in f7b341c. Let me know if the wording works for you. Thanks.
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.
Thanks, LGTM.
Add link to kibana config. Adjust comments. Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
We probably also want to refactor deploy/eck-stack/examples/kibana/. |
great catch! will.do |
|
Sorry, hit the wrong button and closed this.... |
Signed-off-by: Michael Montgomery <[email protected]>
@thbkrkr this has been fixed. |
Co-authored-by: Thibault Richard <[email protected]>
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.
LGTM
Add kibana monitoring rendering tests. Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
…ibana only) (elastic#8192) * Make helm charts consistent with how .spec is handled. --------- Signed-off-by: Michael Montgomery <[email protected]> Co-authored-by: Thibault Richard <[email protected]> (cherry picked from commit a79db96) Signed-off-by: Michael Montgomery <[email protected]>
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
related: #8184
Details of suggested change
It was pointed out in the above PR that the helm charts aren't consistent in how they implement values that end up within the
spec
field of the associated resource. Unfortunately the changes in 8184 are not backwards compatible, and are a breaking change. I went down the path of determining what a non-breaking change would look like, and just implemented this in theeck-kibana
chart.The question I have:
(The intent is to do this for all inconsistent charts; just wanted to make the initial review/discussions easier)
Implementation Note
.spec.field
in the values take precedence over justfield
in the values.spec.http.something
, and also settinghttp.somethingElse
)