lyft / lyft/flinkk8soperator

Question: is savepointing required?

Open
#57 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
581
Forks
153
PR merge metrics
No merged PRs in 30d

Description

Thank you for developing and open-sourcing this operator! Maintaining Flink jobs with state on Kubernetes without it has been error prone. Quick question: I'd also like to use this operator for Flink jobs without a persistent state requirement. Is it possible to deploy a new version of a job without restoring from a savepoint when state doesn't matter?

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start by tracing how the operator upgrades Flink jobs and handles savepoint restoration, then determine the expected behavior for jobs without persistent state. Done means the supported behavior is clearly defined and covered by appropriate tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.