Comments (1)
Slack thread for reference
Suggested Enhancement:
And this was my suggestion in the thread, for reference.
Not quite as a receiver function, but this function does already exist:
argo-workflows/workflow/util/util.go
Line 1059 in b1c3768
It's just not in the same place as
GeneratePodName
or some other functions.
Coincidentally, I had been looking into lots of pod name issues yesterday and today, so am pretty familiar with this now. In particular, a root cause fix for this would be to refactor according to #12964's "Future Work" section -- then getTemplateName
would always be called within GeneratedPodName
same as the UI
Possible Cause:
Also can confirm that this is the cause now, you were spot-on.
from argo-workflows.
Related Issues (20)
- Ability to override pod GC strategy on a per-template basis HOT 1
- workflows.argoproj.io/completed is false when output set for resource creation HOT 2
- Argo controller cannot find completed pod after seeing the pod as completed, reports workflow as an Error HOT 1
- option to not auto-add tolerations HOT 3
- reduce pod definition size HOT 3
- 3.5 Pagination in workflow list page not working HOT 5
- Dependency between CronWorkflows HOT 5
- 3.5.6+ `items.status.nodes` disappeared from `/api/v1/workflows` endpoint for completed Workflows HOT 5
- Specify external artifacts repo with azure blob HOT 1
- DOM text reinterpreted as HTML in `workflow-logs-viewer.tsx` HOT 2
- Fix incorrect conversion between integer types in `parametrizable.go` HOT 1
- Possible clear-text logging of sensitive information in CLI `token.go` HOT 2
- Archived workflows deletion with GC stopped working after move to namespace install HOT 6
- Devcontainer `Permission denied` error during `chown`
- Unable to run Controller locally on Arm mac M1 HOT 1
- UI: Open custom `links` in new tab or with router navigation depending on address HOT 1
- `MetricsError`: custom metrics at Workflow-level unable to resolve output variables HOT 1
- support `retryPolicy` combination HOT 3
- `podSpecPatch` not applied when configured in `workflowDefaults` and workflow is submitted from template HOT 1
- `podSpecPatch` doesn't evaluate `retries` when defined at workflow spec HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from argo-workflows.