Q 1. Is it possible to put this annotation on a namespace or a deploymentconfig? At this time we are not using deployments very much, but deployment configs. I know some of the other annotations now work on deployment configs and most of them have worked on the namespace in the past.
Q2. The problem I have now though is we already use this annotation:
ca.broadcom.com/autoattach.java.attach.overrides: autoattach.java.proactiveMode.agent.load.delay=60
We had used this to try to reduce the time it takes for a UMA attached agent to start reporting to DX SaaS. Perhaps this isn’t needed anymore but when we try to add the annotation for the memory, it conflicts.
oc annotate ns coolapp ca.broadcom.com/autoattach.java.attach.overrides=autoattach.free.memory.threshold=20
error: --overwrite is false but found the following declared annotation(s): 'ca.broadcom.com/autoattach.java.attach.overrides' already has a value (autoattach.java.proactiveMode.agent.load.delay=60)
It appears you can only have one annotation for 'ca.broadcom.com/autoattach.java.attach.overrides'
Maybe we don’t need the load.delay one anymore as it seems to be getting faster, but it is unfortunate that we might need 2 annotations and only one is available as the conflict with each other.
Q1. Yes
Q2.
If running it through the command line,do like the below. So it sets both properties.
oc annotate ns coolapp ca.broadcom.com/autoattach.