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.

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(validation-reconciler): correct output and flow status report #1920

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

csatib02
Copy link
Member

@csatib02 csatib02 commented Jan 21, 2025

Fixes: #1140
Fixes: #700

@csatib02 csatib02 requested a review from pepov January 21, 2025 11:16
@csatib02 csatib02 self-assigned this Jan 21, 2025
@csatib02 csatib02 force-pushed the fix/output-flow-status branch from c24a595 to 83b8e20 Compare January 22, 2025 18:03
@csatib02 csatib02 requested a review from OverOrion January 23, 2025 06:50
@csatib02 csatib02 force-pushed the fix/output-flow-status branch 4 times, most recently from c159a1e to f99ad35 Compare January 23, 2025 12:22
@csatib02 csatib02 requested review from pepov and removed request for OverOrion January 23, 2025 12:22
@@ -10,7 +10,7 @@ LoggingSpec defines the desired state of Logging

### allowClusterResourcesFromAllNamespaces (bool, optional) {#loggingspec-allowclusterresourcesfromallnamespaces}

Allow configuration of cluster resources from any namespace. Mutually exclusive with ControlNamespace restriction of Cluster resources
Allow configuration of cluster resources from any namespace. Mutually exclusive with ControlNamespace restriction of Cluster resources WARNING: Becareful when turning this on and off as it can result in some resources being orphaned.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still valid with the immutable constraint being present?

Copy link
Member Author

@csatib02 csatib02 Jan 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If a cluster output gets selected by a single logging, because of this flag being turned on, then its status will be filled out. If we turn this off the cluster output will not be selected, but its status will indicate that it is still active. So yeah users can make resources stuck if they turn this on and off.

@csatib02 csatib02 force-pushed the fix/output-flow-status branch from f99ad35 to 3ca364b Compare January 26, 2025 06:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants