This message was deleted.
# general
s
This message was deleted.
d
The SN operators are under a community license.
Are some components licensed in ASF and some not?
k
Actually an interesting question. 🤔 I also thought that it was under Apache 2.0. If not, it should definitely be reflected on GitHub.
👍 1
d
Thanks for the feedback. The resource and function mesh operators are both ASF-licensed. As stated in the GitHub repo, the pulsar operators are under the community license.
👍 1
k
@David K Thank you for the response. At first glance, it wasn’t clear that the pulsar-operator is not the same as any of the pulsar-resources-operator. Operator here, operator there… 🙂 Maybe not necessary, but would be nice to have some notion with bold font that it’s not the same things and licenses are different. @Michał Cukierman what do you think?
m
I think it’s proper legally, but I needed to ask, so may be unclear for others too. KAAP is open source, so probably it should be considered as default/recommended way of installing Pulsar?
I wonder if there is any outgoing work on providing Pulsar/K8S support l. There is only Helm which was recently marked as “not recommended”. Maybe it’s possible to fork KAAP and make it a part od Pulsar?
⁉️ 1
k
> KAAP is open source, so probably it should be considered as default/recommended way of installing Pulsar? I would probably wait for several battle-tested reviews first, before considering it default/recommended.
m
Kaap could be a starter. It’s widely used already. Would be good to have a community driven k8s deployment mechanism for pulsar, which is cloud native.
Its java based, so probably could be ported to use https://github.com/quarkiverse/quarkus-operator-sdk to leverage graalvm
d
Rather than fork Kaap you could ask DataStax to contribute it. Many of the DS developers are also on the Apache Pulsar PMC. @Nicoló Boschi ?
n
As Dave said, KAAP (https://github.com/datastax/kaap) is open source and Apache 2.0 licensed. No need to fork, let's help to build the community instead. Donating to the Pulsar community would be nice - in the future, even thought the process is not straightforward and it requires a relevant effort. I'd be happy to discuss about that if there's interest.
Its java based, so probably could be ported to use https://github.com/quarkiverse/quarkus-operator-sdk to leverage graalvm
👍
m
@Nicoló Boschi Thanks for the clarification. We will use KAAP as the default option due to licensing. We also use Quarkus/SmallRye/GraalVM in our product, and we have a plan to create operator for our application. Soon we should have skills to contribute (we need to learn the framework).
n
That would be great, feel free to ping me directly on DM for getting help and discuss about improvements