Mariusz O艂ownia
02/11/2025, 9:18 AMGyula F贸ra
02/11/2025, 9:55 AMdavid radley
02/11/2025, 2:30 PMThomas Cooper
02/11/2025, 2:31 PMdavid radley
02/11/2025, 3:19 PMThomas Cooper
02/11/2025, 3:20 PMdavid radley
02/11/2025, 3:21 PMTony Garrard
02/11/2025, 3:36 PMdavid radley
02/11/2025, 3:40 PMdavid radley
02/12/2025, 11:33 AMThomas Cooper
02/12/2025, 11:36 AMTony Garrard
02/12/2025, 11:40 AMThomas Cooper
02/12/2025, 11:41 AMTony Garrard
02/12/2025, 11:42 AMThomas Cooper
02/12/2025, 11:43 AMThomas Cooper
02/12/2025, 11:44 AMTony Garrard
02/12/2025, 11:45 AMThomas Cooper
02/12/2025, 4:15 PMThomas Cooper
02/12/2025, 4:26 PMThomas Cooper
02/12/2025, 4:27 PMdavid radley
02/12/2025, 5:58 PMJames Busche
02/12/2025, 6:00 PMJames Busche
02/12/2025, 10:17 PMTony Garrard
02/13/2025, 2:09 PMoperator-sdk generate bundle .Thomas Cooper
02/13/2025, 2:11 PMThomas Cooper
02/13/2025, 2:11 PMTony Garrard
02/13/2025, 2:13 PMJames Busche
02/14/2025, 7:57 AMJames Busche
02/14/2025, 8:01 AMTony Garrard
02/14/2025, 10:54 AMThomas Cooper
02/14/2025, 11:02 AMJames Busche
02/19/2025, 1:08 AM*flink*statesnapshots but the flinkdeployments and sessionjobs look ok on my 4.17.9 FIPS cluster.
oc get pods,flinkdep,sessionjob
NAME READY STATUS RESTARTS AGE
pod/basic-example-d9d69498f-dfwrw 1/1 Running 0 5m46s
pod/basic-example-taskmanager-1-1 1/1 Running 0 5m28s
pod/basic-session-deployment-only-example-765cfdb959-pbdvs 1/1 Running 0 79s
pod/basic-session-deployment-only-example-taskmanager-1-1 1/1 Running 0 39s
pod/basic-session-deployment-only-example-taskmanager-1-2 1/1 Running 0 39s
NAME JOB STATUS LIFECYCLE STATE
flinkdeployment.flink.apache.org/basic-example RUNNING STABLE
flinkdeployment.flink.apache.org/basic-session-deployment-only-example STABLE
NAME JOB STATUS LIFECYCLE STATE
flinksessionjob.flink.apache.org/basic-session-job-only-example RUNNING STABLEJames Busche
02/19/2025, 1:08 AMJames Busche
02/19/2025, 1:09 AMThomas Cooper
02/19/2025, 11:22 AMdavid radley
02/19/2025, 11:48 AMThomas Cooper
02/19/2025, 11:52 AMtools/olm directory then we should probably have those changes merged upstream before we do the PR to the operator hub?david radley
02/19/2025, 5:10 PMtools/olm directory with the up to date steps and scripts. Let us know how we can help.James Busche
03/21/2025, 8:30 PMJames Busche
03/21/2025, 8:31 PMTony Garrard
03/21/2025, 9:07 PMThomas Cooper
03/24/2025, 8:43 AMtools/olm folder, wither in the README.md or in a new RELEASE.md or similar. If you could put a PR up with those (with any IBM specific steps removed) that would let the community review it and we could work towards automating the release process as much as possible upstream.