Skip to content

[V2] Add App events#7296

Closed
machichima wants to merge 8 commits intoflyteorg:v2from
machichima:app-events
Closed

[V2] Add App events#7296
machichima wants to merge 8 commits intoflyteorg:v2from
machichima:app-events

Conversation

@machichima
Copy link
Copy Markdown
Member

@machichima machichima commented Apr 28, 2026

Tracking issue

Why are the changes needed?

Show APP events

What changes were proposed in this pull request?

  • Add app_conditions table in DB to store conditions (events) for app
  • Append conditions to DB when informer cache watch event triggered

How was this patch tested?

  • Serve app through devbox and check if we can see events
image

Labels

Please add one or more of the following labels to categorize your PR:

  • added: For new features.
  • changed: For changes in existing functionality.
  • deprecated: For soon-to-be-removed features.
  • removed: For features being removed.
  • fixed: For any bug fixed.
  • security: In case of vulnerabilities

This is important to improve the readability of release notes.

Setup process

Screenshots

Check all the applicable boxes

  • I updated the documentation accordingly.
  • All new and existing tests passed.
  • All commits are signed-off.

Related PRs

Docs link


// RunMigrations applies all pending app migrations.
func RunMigrations(ctx context.Context, db *sqlx.DB) error {
return database.Migrate(ctx, db, "app", migrationFS)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We intentionally don’t use the database in the app service for simplicity. Could we directly get the events from the CRD when watching the events

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

In this case we will miss historical conditions as k8s conditions will only store the latest state

  Conditions:
    Last Transition Time:        2026-04-28T07:41:44Z
    Status:                      True
    Type:                        ConfigurationsReady
    Last Transition Time:        2026-04-28T07:41:44Z
    Status:                      True
    Type:                        Ready
    Last Transition Time:        2026-04-28T07:41:44Z
    Status:                      True
    Type:                        RoutesReady

Copy link
Copy Markdown
Member

@pingsutw pingsutw Apr 28, 2026

Choose a reason for hiding this comment

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

we will miss historical conditions

that's okay

@pingsutw pingsutw added this to the V2 GA milestone Apr 28, 2026
@pingsutw pingsutw closed this Apr 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants