-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Description
Eschewed features
- This issue is not requesting templating, unstuctured edits, build-time side-effects from args or env vars, or any other eschewed feature.
What would you like to have added?
I would like there to be a community accepted logo representing kustomize as a well established tool in the IT world. That is readily available for redistribution, in order to represent the project. That requires its availability in suitable formats, with clear licensing.
Here is a proposal I would like to donate to the project as SVG under the terms of the Apache License 2.0 for the benefits of the kubernetes ecosystem:

Why is this needed?
There apparently is a demand for this demonstrated by #5399, and the fact that there exist some logo of unknown origin and license at kustomize.io.
In Argo CD, we can also use a visual representation for kusotmize (argoproj/argo-cd#23446).
And I am sure there are many others. Not even mentioning the "marketing" benefits it have for the tool propagation, etc.
Can you accomplish the motivating task without this feature, and if so, how?
Not quite. One can use the logo from kustomize.io with unclear licensing. Or various subjects can start sketcihng their own...
What other solutions have you considered?
I made an effort to clear the logo at kustomize.io thorugh the lawyers for OSS use, but was advised not to. The attempts to contact the original contributors at #5399, to retroactively license their logo under an OSS licence met no response.
Anything else we should know?
No response
Feature ownership
- I am interested in contributing this feature myself! 🎉