feat: Implement rollout status command. Fixes #596

[ThisIsFroggie]

Closes #596

This replicates the kubectl rollout status deployment [--watch] <name> command, but for Rollouts.

This is implemented as:

# Returns Rollout status: Healthy, Progressing, Degraded, etc
kubectl argo rollouts status --watch=false <name>

# Waits until status is Healthy or Degraded (default behaviour without flags)
kubectl argo rollouts status --watch <name>

The flags and defaults for them replicate the kubectl rollout status deployment <name> command. As in it, --watch is default and the default timeout is 5 minutes.

---

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
  • (a) See [Feature Request] rollout status #596
• The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed my commits with DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My builds are green. Try syncing with master if they are not.
• My organization is added to USERS.md.

[codecov-io]

Codecov Report

Merging #1001 (3f754e8) into master (dff1f22) will increase coverage by 0.09%.
The diff coverage is 93.54%.

@@            Coverage Diff             @@
##           master    #1001      +/-   ##
==========================================
+ Coverage   80.90%   81.00%   +0.09%     
==========================================
  Files         102      103       +1     
  Lines        9080     9159      +79     
==========================================
+ Hits         7346     7419      +73     
- Misses       1240     1245       +5     
- Partials      494      495       +1     

Impacted Files	Coverage Δ
pkg/kubectl-argo-rollouts/cmd/status/status.go	93.44% <93.44%> (ø)
pkg/kubectl-argo-rollouts/cmd/cmd.go	100.00% <100.00%> (ø)
utils/evaluate/evaluate.go	60.74% <0.00%> (-0.73%)	⬇️
pkg/kubectl-argo-rollouts/cmd/create/create.go	65.42% <0.00%> (-0.60%)	⬇️
metricproviders/wavefront/wavefront.go	95.45% <0.00%> (-0.06%)	⬇️
analysis/analysis.go	83.80% <0.00%> (+0.09%)	⬆️
.../apis/rollouts/validation/validation_references.go	74.28% <0.00%> (+1.01%)	⬆️
rollout/service.go	78.94% <0.00%> (+4.66%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dff1f22...3f754e8. Read the comment docs.

[jsoref]

With this, I think this is the best I can offer as feedback. Someone more core should be responsible for a code review & approval

[keithmattix]

Is there anything preventing this from being merged? This would be huge for my organization's CD pipeline

[jessesuen]

The flags and defaults for them replicate the kubectl rollout status deployment command. As in it, --watch is default and the default timeout is 5 minutes.

It seems that kubectl defaults to at timeout of 0s (never). Instead of defaulting to 5m, can we replicate kubectl behavior?

$ kubectl rollout status --help
...
      --timeout=0s: The length of time to wait before ending watch, zero means never. Any other values should contain a
corresponding time unit (e.g. 1s, 2m, 3h).

[ThisIsFroggie]

It seems that kubectl defaults to at timeout of 0s (never). Instead of defaulting to 5m, can we replicate kubectl behavior?

I must have misread when I saw the timeout default. I'll update it to replicate that default.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

No Coverage information
16.8% Duplication

[ThisIsFroggie]

Fixed the timeout to match the official one in kubectl itself.

[jessesuen]

Great work!

[shahafy-ma]

When will it be available for use?