Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agent permissions is actually breaking (you cannot patch .status of any CR with sub-resource) #8013

Closed
alexec opened this issue Feb 25, 2022 · 2 comments · Fixed by #8015
Closed

Comments

@alexec
Copy link
Contributor

alexec commented Feb 25, 2022

I made a mistake here, and learnt something.

Once you introduce a status sub-resource, you can no longer patch the whole resource, for example:

kubectl patch wfts template-executor-jfmfn -p '{"status": {"nodes": {"template-executor-jfmfn": {"message": "ok"}}}}' --type merge
workflowtaskset.argoproj.io/template-executor-jfmfn patched (no change)

See that there was "no change".

That means that changing to use workflowtaskset/status is a breaking change.

For users that are impacted by this, there is an espace hatch - do not install new manifests. This is a bad solution.

@terrytangyuan
Copy link
Member

This hasn't been released yet though, right? #7987

Should we try to cover this in tests and make sure we can always patch the resource?

@alexec alexec added the v3.4 label Feb 25, 2022
@alexec
Copy link
Contributor Author

alexec commented Feb 25, 2022

It's not fixable. And I don't want to fix it. We could delay #7987 to v3.4.

alexec added a commit to alexec/argo-workflows that referenced this issue Feb 25, 2022
Signed-off-by: Alex Collins <alex_collins@intuit.com>
alexec added a commit that referenced this issue Feb 25, 2022
Signed-off-by: Alex Collins <alex_collins@intuit.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants