Skip to content
This repository has been archived by the owner on Nov 16, 2020. It is now read-only.

Properly expose and report resource status #641

Open
1 of 3 tasks
berndtj opened this issue Oct 5, 2018 · 0 comments
Open
1 of 3 tasks

Properly expose and report resource status #641

berndtj opened this issue Oct 5, 2018 · 0 comments
Labels

Comments

@berndtj
Copy link
Contributor

berndtj commented Oct 5, 2018

Bug Report

Expected behavior

The Dispatch status field of the API should reflect the current state of the resource. Also, some of the context provided by the underlying k8s object should be reported.

Current behavior

Resources are either INITIALIZED or READY. Error states are not properly reported.

Steps to reproduce

Impact

  • Low - Annoyance, but does not impact business or functionality
  • Medium - Issue can be worked around, but is causing pain
  • High - Blocker

Possible solution

Your Environment

  • Dispatch CLI version (or git commit):
  • Dispatch Chart version (or image[s] tag):
  • Operating System and version:
  • Kubernetes version (and distribution):
  • Etc (any other useful environmental information):
@berndtj berndtj added the Knative label Oct 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant