Summary

Environment

• Latest argo-workflows from master installed from https://raw.githubusercontent.com/argoproj/argo-workflows/master/manifests/quick-start-postgres.yaml
• Kubernetes version: v1.22.2
• Minikube version: v1.23.2
• Mac OS X 11.6

Given the instructions defined here https://github.com/argoproj/argo-workflows/blob/master/docs/variables.md I expect that vari

Description

It is not an actual bug but in the documentation here -> https://docs.prefect.io/orchestration/concepts/api.html#queries
flow_run actually needs to be flow_runs.
Otherwise it does not work for me.

Expected Behavior

Documentation should be updated.

Reproduction

Is your feature request related to a problem? Please describe.
There is an optional config for namespace called "sampled retention days" that can be specified when create a namespace. It was created long ago as workaround for long retentions before long term archival was available.

Describe the solution you'd like
We should get rid of the sampled retention.

**Describe alternatives

Is your feature request related to a problem? Please describe.

If I want to use an replicated and sharded elasticsearch setup for the exporter I need to be able to configure the replication and shards for the exporter indices.

Describe the solution you'd like

Have a elasticsearch exporter configuration available which allows me to set the replication and shards. I think for the f

As reported by @jonalv , it can be confusing what is happening when if the globber pattern does not catch any files.

The suggestion is to:

• Log when the globber starts, with the pattern used
• Issue a warning if the globber doesn't match any files at all

Summary

What change needs making?
Example script on how to use created secret successfully.
I have tried myself using the following code from test
It creates a secret successfully but fails to echo the secrets value.

Use Cases

When would you use this?
when I n

We should have a group support to handle permissions access from a LDAP, SSO, ...

allowed_resolvers_groups on templates for example.
admin_groups on configuration for example.

Describe the bug
Deploying a new job, then pulling logs via the CLI results in a panic (SIGSEGV).

To Reproduce

1. odin deploy -f test.job.yaml
2. odin log -i {job_id}

vagrant@vagrant:~/odin$ odin log -i dea194794589
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x79c764]

goroutine