https://linen.dev logo
Join Slack
Powered by
# fluent-operator
  • m
    FYI: the 
    image:
    structure PR is a breaking change, meaning we probably need to do a major bump and somehow capture that in a CHANGELOG/Release note
    👍 1
    j
    • 2
    • 2
  • m
    For the operator dependencies bump I think that is just a minor release
    j
    • 2
    • 1
  • m
    I think for now we are good to go with a new release. Whenever I see room for improvements and such we can do that in future releases
  • f
    Hi folks, I'm a first time contributor and I've opened a few PRs for the operator repo. As a third party contributor, I'm unable to request reviewers, and none were assigned on the PRs. Is simply filing PR senough for them to be triaged, or is there something more that I should do to make them more visible to reviewers?
    c
    j
    • 3
    • 4
  • f
    Where should I report security vulnerabilities with the operator? There is a supply chain vulnerability that gives anybody who can create branches in the https://github.com/fluent/fluent-operator repo (presumably everybody in the fluent GitHub org) the ability to execute arbitrary code in many customer/user environments that the operator is deployed in. It looks like it has existed for several weeks without anybody noticing.
    j
    p
    • 3
    • 3
  • m
    Small improvement to CI so we can fix the problem and prevent this from happening in future https://github.com/fluent/fluent-operator/pull/1570
  • m
    https://github.com/fluent/fluent-operator/pull/1571 small improvement removing the duplication between ci and makefile as well getting rid of some hacks by using 
    go install
    instead of 
    go get
    to install the tools
    🎉 1
  • m
    Both PRs are related see the comments and PR descriptions.
  • m
    I think these will fix the problems introduced in earlier PRs
    👍 1
  • m
    from here I can rework the controller-runtime upgrade and will this time also see if I can then add some e2e test to cover the problem introduced earlier.
  • j
    @Marco Franssen @Chengwei Guo Can the three of us get together and figure out exactly what we need to get Renovate up and working? I don't think we need to install the Renovate application since we're running Renovate self-hosted in CI. I think we just need credentials. Sound right?
    m
    c
    • 3
    • 13
  • m
    I opened 2 small PRs to cleanup dependabot
  • m
  • m
  • m
  • m
    Another small PR to ensure helm tests are executed when changes to the chart happen https://github.com/fluent/fluent-operator/pull/1597
  • m
    👀 1
    j
    • 2
    • 2
  • m
    What would be required to cut a new release?
    j
    • 2
    • 5
  • m
    https://github.com/fluent/fluent-operator/pull/1605 small PR to fixup the crds (descriptions only)
  • m
    https://github.com/fluent/helm-charts/pull/602/files prepared the release for the helm-chart. On the operator repo all PRs are merged. @Benjamin Huo @Chengwei Guo could you have a look to get the release out?
    🥳 2
    • 1
    • 1
  • j
    @Marco Franssen I think we need to attach the 
    setup.yaml
    to the release.
    m
    • 2
    • 9
  • m
    @Chengwei Guo @Benjamin Huo @Wanjun Lei @Josh Baird what is required to get the helm-chart PR merged? https://github.com/fluent/helm-charts/pull/602/files
    j
    • 2
    • 3
  • o
    Hi! can i get help here with clusterfilters / clusterparsers?
    j
    c
    • 3
    • 8
  • m
  • j
    I wonder if we don't need a maintainer+community meeting to talk about our release process. It could use some attention. 🙂
  • s
    Hi there We are using fluent-operator and the ClusterOutput CRD to define the Splunk Output Plugin. Is there a way to dynamically set eventIndex, eventSource and eventSourcetype (except using os env)?
  • m
    https://github.com/fluent/fluent-operator/pull/1623 think this is what is required to patch up the entire chart release
    j
    • 2
    • 1
  • a
    Hey @Marco Franssen @Josh Baird, you should now both have access to fluent helm charts repository
    j
    • 2
    • 2
  • j
    @Marco Franssen @Chengwei Guo re: the Helm chart.. do you find it confusing that we maintain a "local" copy of the chart in the fluent-operator repo and then have to manually sync to helm-charts to release?
    m
    p
    • 3
    • 7
  • v
    Hi team! When I tried to run ghcr.io/fluent/fluent-bit:4.0.3 I run into trouble not having any of my config actually properly propagated despite the fact that I can observe it being mounted. Afterwards, I switched to ghcr.io/fluent/fluent-bit:4.0.3-debug where I can see entrypoint being
    Copy code
    root           1  0.0  0.0  85760 14480 ?        Ssl  10:08   0:00 /fluent-bit/bin/fluent-bit -c /fluent-bit/etc/fluent-bit.conf
    Whereas my config is landed at
    Copy code
    /fluent-bit/config
    Is it a bug of 3.4.0 version of an operator, or intended, or there's some other thing I have completely forgotten to configure by any chance?
    • 1
    • 2