Report permission issue in MachineDeployment #501
Labels
area/usability
Usability related
kind/enhancement
Enhancement, improvement, extension
lifecycle/stale
Nobody worked on this for 6 months (will further age)
priority/backlog
Issues which needs implementation
What would you like to be added:
If new instances for an existing MachineDeployment cannot be created because of insufficient permissions or unauthorized requests to the cloud provider, then this should be reflected in the MachineDeployment's status.
At the moment the status reports:
Logs:
Why is this needed:
Gardener reports the status to users and thus it gives them a chance to fix the issue w/o support from operations.
The text was updated successfully, but these errors were encountered: