Hacker Newsnew | past | comments | ask | show | jobs | submit | einstand's commentslogin

My favorite presentation about K3s is when Darren Shepherd explains all the black magic (=all the custom patches) which made it possible:

https://www.youtube.com/watch?v=k58WnbKmjdA


this is highly recommended.


ASF rules require a report from the PMC at every third month. There reports are written by the Project Membership Committee, and checked by the Board. (I know that they really read them).

Board reports (including project reports) are open (with 1-2 month delay, they are published only after approval, at the next Board Meeting).

You can find the report of OpenOffice project here: https://whimsy.apache.org/board/minutes/OpenOffice.html

ps: just adding here as an additional source, I couldn't really judge the situation...

ps2: BTW, I think it's very interesting to read these project reports...


Only skimmed it, but that was some sad reading.


For me -- as I am outsider -- it's hard to understand all the non-technical arguments and social dynamics.

From technical point of view, I really like the composition-based/declarative approach of Kustomize.

I am testing different type of bigdata clusters in k8s (Hadoop, Hdfs, Spark, HBase, Hive, Ozone, etc.). I need a method to easily create/install different type of clusters with a set of predefined components. Sometimes I need Spark, sometimes not. Sometimes I need HDFS HA sometimes not. With or without kerberos.

With Helm chart it's almost impossible: all the charts would be full with different conditional branches and which hard to be maintained (and hard to handle dependencies: for example if both hdfs/yarn cluster would like to add something to the core-site.xml configuration).

The composition based approach works better for my use-case, but I found Kustomize very difficult to use. It has strict opinion/limitation how the thing should be defined/worked [1], which are very smart, but sometimes not for my use-case. Also it requires very verbose configuration.

Finally I just created my tool which is more flexible (shameless plug, it's here: [2]) which can do anything with the help of composition and more easy to use.

I respect the Kustomize developers and development and I am very happy that it exists. (And I know that it's way more mature/smart than my tiny tool)

I am just not sure if it it's possible to cover all the use-cases (or majority of the use-cases) with one existing tool (neither with Helm nor with Kustomize). Therefore I would prefer to keep all these tools in separated repo. Personally I would prefer to have more similar tools with new ideas and prefer to have better and better (and more flexible) Kustomize.

But this is just my personal preference.

[1]: https://github.com/kubernetes-sigs/kustomize/blob/master/doc...

[2]: http://github.com/elek/flekszible


Eugenia Cheng: "The Art of Logic: How to Make Sense in a World that Doesn't"

https://www.youtube.com/watch?v=YHZKX0H6cUE

I saw an other version at Scala Exchange but that one requires registration [1] and it's seems to be almost the same talk.

It's very impressive summary of her latest book ("The Art Of Logic") about the importance of abstract logic in every day life and how abstraction can help us to understand each other (together with emotions).

[1]: https://skillsmatter.com/skillscasts/12089-keynote-conveying...


SEEKING WORK - Remote

Location: EU, Hungary

Architecting/Developing/Coding

Primary languages: Java/Scala (Spring Cloud, Akka, Play, Cassandra, Mongo and many more) but familiarity with all the parts of the full stack (Js, other scripting languages, etc.). Strong devops skills.

15+ year experiences: Pragmatic enough to find the shortest path to the MVP but enthusiast enough to maintain the quality.

Github: http://github.com/elek

CV/details: http://anzix.net/elek/cvlk/


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: