https://linen.dev logo
Join Slack
Powered by
What is required to get a new release for the oper...
# fluent-operator
m
What is required to get a new release for the operator helm chart out?
@Josh Baird @Chengwei Guo thoughts on when we can get the new chart released including new operator version?
j
Haven't had time this week, but I'll take a look tomorrow afternoon.
We just need to sync it over to the charts repo and may need a little help from @Steve Hipwell.
m
ok, no worries. Would be great I think
j
yeh - sorry, just been super busy lately!
It's on my list.
p
@Steve Hipwell has done a load of useful improvements to the CI so it may be slightly different to before but hopefully still straightforward. I can lend a hand too if you need it
💯 1
👍 1
j
I'm still working on the 
fluent-operator-crds
chart. I'm hitting this issue and still digging on potential solutions.
Couple potential options for getting around the 1MB thing: • Split 
fluent-operator-crds
into two separate charts -- one for 
fluentd
CRDs, one for 
fluent-bit
CRDs • Docs that tell users to install two separate releases of 
fluent-operator-crds
-- one with 
fluentbit.enabled=false
and one with 
fluentd.enabled=false
-- this would reduce the size of the Secret Not crazy about either approach, tbh.
m
I'm not sure if I understand the second bullet? could you explain that a little more detailed?
Aaaah I see now on this link https://jkroepke.de/2026/02/handling-large-files-and-crds-in-helm-and-the-1mb-release-limit/. Hence that is why I was pointing at the 2 crds charts earlier and don't do a crds folder.
j
So, something like this:
Copy code
helm install fluent-operator-crds-fluentbit fluent/fluent-operator-crds \
  --set fluentd.enabled=false

helm install fluent-operator-crds-fluentd fluent/fluent-operator-crds \
  --set fluentbit.enabled=false
Same "chart" -- but each release get it's own 
sh.helm.release.v1.$name.v1
secret -- which would be well under 1MB (since each release would only contain either the fluentbit or fluentd CRDs).
m
I actually wanted to do crds with the dependencies and .enable flag per what we enabled fluentbit/fluentd
j
The 
crds/
folder on the main chart is fine -- it's not included in the Secret.
s
Another option would be to remove CRD comments (I wouldn't recommend this), or require Helm 4 which will use server side apply.
m
hmmm then I don't get your bullet 2
helm 4 would be cool
j
These issues/comments/concerns/etc are only about the CRDs chart -- not the main 
fluent-operator
chart (which is fine as-is).
m
aaah, got it now. I get your second bullet
👍 1
presonally I would just make it 2 charts, makes it more clear to users what gets installed without having to do values
but also fine with the other option, which makes it a bit more relying on the user to do the right thing
which could result in users reporting bugs and such if they skip reading the manual
👍 1
j
Should we explore Helmv4?
m
Copy code
Once you have the data, try the structural fix first: move CRDs into a dedicated subchart as this often yields the biggest win with low risk. You should also trim documentation bloat by keeping README.md lean and splitting content into USAGE.md or UPGRADES.md.
This is the advise in practical guidance
in that article you shared
so I'm a bit puzzled we are not affected by that in our main chart with the crds folder
This article says specifically charts using the crds folder are affected 🤔
j
I can actually install 
fluent-operator-crds
locally and don't hit the issue.. but it failed in CI.
m
interesting
are you using helm v4 locally?
j
no, v3 -- I think we're very close to 1MB, but my testing shows we're slightly under it right now.
Let me double check CI again.
m
Can it be the README.md which is generated in CI
also hence this note: ``````
j
yeah - potentially, but the README for the crds chart is tiny
m
can you add that README.md locally and try again?
👍 1
It might be just the small overhead
j
That may be it -- because I think we're only 912bytes < 1MB 😆
m
I would go for splitting the chart in 2 crds charts
then we don't have to tell users to set stuff to false
+ we don't have to do the trickery from that article to keep under the 1MB limit
However I think the problem should also be on the operator-chart itself. The entire article is about crds in the crds folder and about moving them out of there to prevent the limits
j
Yeah -- will have to look at that again, but CI did not fail there. I have also tested locally.
Could you try installing the charts locally on a kind cluster or something perhaps?
m
I can try tomorrow, 19:00 here and kids are waiting for me
j
no rush, thanks!
s
CRDs in the 
crds
dir aren't part of the chart so don't pollute the secret.
d
We could copy what kube-prometheus-stack did for their crds, moving them into a subchart that contains both the crds/ folder and an optional job for automatically updating crds with a helm hook job https://github.com/prometheus-community/helm-charts/issues/3548 https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack/charts/crds
m
Then I don’t get what that entire article is about @Steve Hipwell
d
The article is confusing, but it even states later in at some point that the crds/ folder is not included in the release secret
m
Yeah some contradicting statements in there
s
The chart 
crds
dir isn't in the secret as it's not part of the chart and not tracked as such. From memory: when a chart is installed Helm loops the contents of 
crds
and installs any CRDs that are missing.
j
So, given that information -- I don't really think we need to move `fluent-operator`'s CRDs into a sub-chart. They seem fine as is. The simplest/cleanest approach for CRD-specific charts may then be to split them into 2 separate charts -- one for fluent-bit-crds and one for fluentd-crds?
s
AFAIK once a chart is installed there is no real difference as to where the individual components came from and it all lives in a single secret.
j
@Dylan Jenik @Marco Franssen Any opinions or concerns about the approach I outlined above? (leave 
fluent-operator
chart as-is, split 
fluent-operator-crds
chart into 
fluent-operator-crds-fluent-bit
and 
fluent-operator-crds-fluentd
charts to reduce the size)?
d
Yeah I think that makes sense
👍 1
j
Ok - here is the PR to split the two CRD charts: https://github.com/fluent/fluent-operator/pull/1929
@Marco Franssen Thanks for the review -- I'll work on helm-charts PR's now.
m
👍🏻
j
helm-chart PR's: • https://github.com/fluent/helm-charts/pull/716 • https://github.com/fluent/helm-charts/pull/715 • https://github.com/fluent/helm-charts/pull/711 @Steve Hipwell CI is green, but would appreciate your 👀 when you get a chance. Thanks!
s
Reviewed, approved and commented.
Open in Slack
PreviousNext
Powered by