search

artemiscloud / activemq-artemis-operator

Apache License 2.0
69 stars 63 forks source link

[#934] suppress deprecated warnings from the api server as we know we… #935

Closed gtully closed 5 months ago

gtully commented 5 months ago

… need to work with deprecated crs

gaohoward commented 5 months ago

The downside of this is that there are no warnings at all....

gtully commented 5 months ago

The downside of this is that there are no warnings at all....

only in the operator logs, for the client that the operator uses to chat to the api server.

end users of kubectl will have their own client will see the warning in the normal way.

Also for the kube client in the test suite. That will still process the warnings as per the defaults.

gtully commented 5 months ago 
    - --zap-log-level=2

2024-05-29T09:52:42.665Z LEVEL(-2) The ActiveMQArtemisAddress CRD is deprecated. Use the spec.brokerProperties attribute in the ActiveMQArtemis CR to create addresses and queues instead {"code": 299, "agent": "-"}

gtully commented 5 months ago

The downside of this is that there are no warnings at all....

only in the operator logs, for the client that the operator uses to chat to the api server.

end users of kubectl will have their own client will see the warning in the normal way.

Also for the kube client in the test suite. That will still process the warnings as per the defaults.

it makes sense to log at level 2, thanks for the review