Vasily Yanov
Vasily Yanov
No. Since the last version I can choose only from labels list but I can't set "custname" for example. Previous version wasn't affected with this bug
it useful. we have something like this: someapp someapp-backoffice someapp-backoffice-front and I want to filter everything what is related to "someapp" or we have several pods which is providing streaming...
I think both points can be reached if you return the same behavior as it was in previous version: label field could be custom and cross-section and search field reset...
> While the underlying issue is yet to be fixed, CCM v0.1.17 supports a workaround: users may specify a custom hostname and point a corresponding DNS record to the external...
is it just matter of DB and PV size? May it could be implemented as an option?
may be DB rows could be aggregated after 1 month of detailed stat?
same for me. if some replication finished with error it will never retry until kubernetes replicator will be restarted.
> > > Yes it's a resolvable CNAME. > > > > > > Out of curiosity: Can you make it an A / AAAA record? Just wanna see if...
same issue for us: no errors but no notification in slack. BTW: is it possible to disable debug to decrease ci/cd output?