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.

Sign up for GitHub

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

Jump to bottom

Improved transparency on reconcilation problems #1155

Open
a-thaler opened this issue Jun 7, 2024 · 3 comments
Open

Improved transparency on reconcilation problems #1155

a-thaler opened this issue Jun 7, 2024 · 3 comments
Labels
area/manager Manager or module changes good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@a-thaler
Copy link
Collaborator

a-thaler commented Jun 7, 2024

Description
If the reconcilation of a collector is blocked by some restrictions on the cluster like an OPA gatekeeper policy, then the status of the pipeline indicates that the deployment is not ready, nothing more. As the problem is known in the manager (indicated by the logs), a dedicated message could be shown in the status indicating the actual problem. Or at least a generic message saying: The reconcilation of the deployment failed, please have a look into the manager logs.

Criterias

  • in case the reconcilation is blocked by some webhooks, a more detailed status is available indicating the conflicting resource with some reason
@a-thaler a-thaler added kind/feature Categorizes issue or PR as related to a new feature. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. area/manager Manager or module changes labels Jun 7, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Aug 7, 2024

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 7, 2024
@github-actions GitHub Actions
Copy link

This issue has been automatically closed due to the lack of recent activity.
/lifecycle rotten

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 14, 2024
@kyma-bot kyma-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 14, 2024
@a-thaler a-thaler reopened this Aug 19, 2024
@a-thaler a-thaler removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 19, 2024
@github-actions GitHub Actions
Copy link

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 19, 2024
@a-thaler a-thaler removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/manager Manager or module changes good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@a-thaler @kyma-bot