You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a humiocluster and humiorepository manifest is deployed at the same time the operator puts the humiorepository object in ConfigError status because the managed cluster does not exist. The operator does not reevaluate the status of a object in consideration that dependencies may "sort out" over time. I believe the same issue occurs for parser and view objects. When a referenced object is not known rather than give up the operator should periodically re-evaluate conditions
The text was updated successfully, but these errors were encountered:
Follow up if a HumioIngestToken is created before operator has reconciled the Repo and Parser records the token is set to Exists without actually creating it
When a humiocluster and humiorepository manifest is deployed at the same time the operator puts the humiorepository object in ConfigError status because the managed cluster does not exist. The operator does not reevaluate the status of a object in consideration that dependencies may "sort out" over time. I believe the same issue occurs for parser and view objects. When a referenced object is not known rather than give up the operator should periodically re-evaluate conditions
The text was updated successfully, but these errors were encountered: