-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for resource level annotations #553
Comments
I would prefer if we used Also, do you think that we should expose the annotation itself or a property describes the intent, e.g. |
@iocanel , I initially thought about using specific k8s resource kind, then wondering if we are complicating :( .. so thought to make it general as annotations. |
That sounds like a good idea too |
I have been pondering for a solution around this and TBH, I haven't been able to find an elegant technical soluton. The best thing that pops to my mind, is to modify @Label and @annotation in order to include a field say This way one could @KubernetesApplication(name="myapp", labels=@Label(name="foo", value="bar", rerourceKinds=["Service", "Ingress"]) or in properties;
I think that this is pretty close to what @kameshsampath needs and it should also be compatible with what have in downstream projects. @geoand wdyt? |
I like the idea! |
It will be good to have resource level annotations configurable via properties. E.g. let us say we have a
dekorate.kubernetes.expose=true
, then doing something likeShould add the annotations to expose related resources such as ingress
The text was updated successfully, but these errors were encountered: