-
Notifications
You must be signed in to change notification settings - Fork 724
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
Init container updates for persisting kibana plugins. #8389
Conversation
Signed-off-by: Michael Montgomery <[email protected]>
updating unit tests. Signed-off-by: Michael Montgomery <[email protected]>
Should we reuse the existing init container for this? What is the overhead of adding another container? |
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
The problem with using the existing init container is that the |
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Ok, I've verified that this is working as intended by:
I'm going to now see about adding this functionality to the existing init container, and not adding a 2nd.... |
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Logs from recent commit showing init container that does both plugins initialization/copy, and config init.
Also keystore init container logs:
|
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Always include plugins copying. Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
buildkite test this -f E2E_TAGS=kb -m p=gke,p=ocp |
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 (a few small nits)
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[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! 👍
Let's maybe not forget to include something in the release notes to mention that this change is going to restart Kibana Pods for which hardened security is supported.
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
@@ -32,6 +32,8 @@ securityContext: | |||
readOnlyRootFilesystem: true | |||
---- | |||
|
|||
Also note that this change will cause the Kibana pod(s) to be restarted as this change is applied during the upgrade. |
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 think I would expect this in docs/release-notes/highlights-2.16.1.asciidoc
?
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'll get this updated. My apologies. ☕
Actually, this change is perfectly valid as this change in 2.16.0 (with security context added, and additional volumes added) will most certainly cause a restart of the Kibana pods. I'm going to not add any 2.16.1 additions to this PR, and create them separately in an additional PR to include highlights/release notes/etc.
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
* Init container for persisting kibana plugins. --------- Signed-off-by: Michael Montgomery <[email protected]> (cherry picked from commit 0efeb94)
* Init container for persisting kibana plugins. --------- Signed-off-by: Michael Montgomery <[email protected]> (cherry picked from commit 0efeb94)
resolves: #8388
With the recent changes in #7787 we broke users being able to install custom Kibana plugins. This updates the existing init container for Kibana configuration, and adds the ability to copy plugins to an
emptyDir
volume, and then mount this to/usr/share/kibana/plugins
in the primary Kibana container. (effectively mirroring what we do with Elasticsearch)Review Notes
Changes
settings
package to avoid import cycles.Testing