feat(helm): hubble-relay readOnlyRootFilesystem#43653
Conversation
|
looks like |
91a3029 to
1458502
Compare
|
Ran it, squashed, and pushed. |
|
documentation check is failing, |
1458502 to
946c8ce
Compare
|
In theory this is updated. |
946c8ce to
109d1a2
Compare
install/kubernetes/cilium/templates/hubble-relay/deployment.yaml
Outdated
Show resolved
Hide resolved
109d1a2 to
4d6f5f7
Compare
4d6f5f7 to
e2f5690
Compare
e2f5690 to
a039598
Compare
|
I think I've got everything addressed. |
This comment was marked as outdated.
This comment was marked as outdated.
|
@jcpunk The Conformance Cluster Mesh failures persist so could you try to rebase on latest main and we'll see if that fixes it? I don't see how it could be related to your changes. |
By redirecting ENV GOPS_CONFIG_DIR to `/tmp` the hubble-relay container can be mounted with readOnlyRootFilesystem and an emptyDir. Signed-off-by: Pat Riehecky <riehecky@fnal.gov>
Head branch was pushed to by a user without write access
a039598 to
25ce8a9
Compare
|
rebased off head |
|
Any guesses why this is sad? |
|
@cilium/sig-hubble any chance one of you could help shepherd this PR forward? We briefly looked through this PR during the community meeting today and concretely it seems to be (a) missing review from @cilium/sig-hubble , and (b) hitting CI failures that do not immediately appear to be related. That said if we think that something in the way Hubble runs could cause these failures, you would be the best ones to know. |
devodev
left a comment
There was a problem hiding this comment.
The overall change LGTM. I agree that CI failures don't seem related to the change.
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXXline if the commit addresses a particularGitHub issue.
Fixes: <commit-id>tag, thenplease add the commit author[s] as reviewer[s] to this issue.
By redirecting ENV GOPS_CONFIG_DIR to
/tmpthe hubble-relay container can be mounted with readOnlyRootFilesystem and a small emptyDir. This is recommended for further hardening the container against any unexpected writes by the trivvy scanner.My cilium 1.18.5 cluster ran with this for 3 days without issue.