-
Notifications
You must be signed in to change notification settings - Fork 880
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
fix: add patch verb to deployment resource #2407
Conversation
Codecov ReportBase: 81.55% // Head: 81.55% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## master #2407 +/- ##
=======================================
Coverage 81.55% 81.55%
=======================================
Files 124 124
Lines 18931 18931
=======================================
Hits 15439 15439
Misses 2702 2702
Partials 790 790 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Dashboard fails with ```failed restoring revision 21: deployments.apps "ourapp" is forbidden: User "system:serviceaccount:argo-rollouts:argo-rollouts-dashboard" cannot patch resource "deployments" in API group "apps" in the namespace "ournamespace"``` when trying to rollback `Rollout` defined using existing `Deployment` and `workloadRef` config. Adding `patch` verb for `deployments` should fix it. Signed-off-by: tukak <[email protected]>
Can you run |
Signed-off-by: tukak <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@zachaller thanks for the hint, it passes now |
* Add patch verb to deployment resource Dashboard fails with ```failed restoring revision 21: deployments.apps "ourapp" is forbidden: User "system:serviceaccount:argo-rollouts:argo-rollouts-dashboard" cannot patch resource "deployments" in API group "apps" in the namespace "ournamespace"``` when trying to rollback `Rollout` defined using existing `Deployment` and `workloadRef` config. Adding `patch` verb for `deployments` should fix it. Signed-off-by: tukak <[email protected]> * Generate dashboard-manifest.yaml Signed-off-by: tukak <[email protected]> Signed-off-by: tukak <[email protected]> Signed-off-by: Dave Sudia <[email protected]>
* Add patch verb to deployment resource Dashboard fails with ```failed restoring revision 21: deployments.apps "ourapp" is forbidden: User "system:serviceaccount:argo-rollouts:argo-rollouts-dashboard" cannot patch resource "deployments" in API group "apps" in the namespace "ournamespace"``` when trying to rollback `Rollout` defined using existing `Deployment` and `workloadRef` config. Adding `patch` verb for `deployments` should fix it. Signed-off-by: tukak <[email protected]> * Generate dashboard-manifest.yaml Signed-off-by: tukak <[email protected]> Signed-off-by: tukak <[email protected]>
* Add patch verb to deployment resource Dashboard fails with ```failed restoring revision 21: deployments.apps "ourapp" is forbidden: User "system:serviceaccount:argo-rollouts:argo-rollouts-dashboard" cannot patch resource "deployments" in API group "apps" in the namespace "ournamespace"``` when trying to rollback `Rollout` defined using existing `Deployment` and `workloadRef` config. Adding `patch` verb for `deployments` should fix it. Signed-off-by: tukak <[email protected]> * Generate dashboard-manifest.yaml Signed-off-by: tukak <[email protected]> Signed-off-by: tukak <[email protected]> Signed-off-by: Gallardot <[email protected]>
Dashboard fails with
failed restoring revision 21: deployments.apps "ourapp" is forbidden: User "system:serviceaccount:argo-rollouts:argo-rollouts-dashboard" cannot patch resource "deployments" in API group "apps" in the namespace "ournamespace"
when trying to rollbackRollout
defined using existingDeployment
andworkloadRef
config. Addingpatch
verb fordeployments
should fix it.Checklist:
"fix(controller): Updates such and such. Fixes #1234"
.