Is your feature request related to a problem? Please describe.
Logs are shown in UTC. IT is frustrating when trying to troubleshoot an issue and need to keep converting timestamps to determine which logs are relevant.

**Describe the sol

Both successful workflows and stopped workflows are generating similar kind of events with 'reason' as 'WorkflowSucceeded'. There is no way to differentiate successful vs stopped events to trigger different down streams based on the status.

What change needs making?
Would like to see reason as 'workflowStopped' for stopped workflows.

Use Cases

We are using [Argo events](https://argoproj

Description

We have created a udev rule similar to below on few nodes, where ndm i

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna

While struggling around with ingress (#2546) I figured out some inconsistencies. For most k8s services it is possible to override args or configs. But for ingress this doesn't work.

It should be possible to customize enable.{my-service} and {my-service}.yaml by having a local copy in:
/var/snap/microk8s/current/microk8s-resources/

But this doesn't seem to work.

Link to the issue (please include a link to the specific documentation or example):
https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/V1ServicePort.md

Description of the issue (please include outputs or screenshots if possible):
The documentation of the V1ServicePort defines target_port type as object. The link on the word object links is broken so the audience c

Expected Behaviour

Change the default cron spec in --etcd-snapshot-schedule-cron (default: "0 */12 * * *"):

--k3s-extra-args '--etcd-snapshot-schedule-cron * * * * *'

Hi,

It seems like naming a remote is subject to certain limitations as groupadd is executed (potentially 32chars?).

Example

apiVersion: gitkube.sh/v1alpha1
kind: Remote
metadata:
  name: app-remote
  namespace: my-really-really-really-long-ns

k logs po/gitkub

Hi,
This is a useful tool for any DevOps/SRE teams managing K8S clusters and apps.
One question though, will this be able to detect changes to Secrets stored in an external store like the GoDday one or the HashiCorp Vault.
thanks,
KK

Use case

Polyaxon tracking can be used to automatically log all information generated by Ludwig.

We should probably think about adding support for Polyaxon's tracking module in Ludwig contrib.

Can we support Linux brew? I'm not sure what that would involve...

Thanks!

Found a strange behavior on netclient and found the following codes in netclient/wireguard/common.go

		if keepAliveString == "0" {
			keepAliveString = "15"
		}

Anyone knows why we are doing this?
IMO, Netclient should not decide what the value is, but follow the instructions from the server (otherwise what is the propose to having a server).

Also I found the keepalive value in

Expected Behaviour

Add the build status from GitHub Actions to the set of README badgets

Current Behaviour

I removed it because it was pointing at Travis, which we no