Hi Gyula, Tom I appreciate that the details are a bit wooly – but what class of incompatibility problems were you envisioning?
My first guess Is it that the operator maybe might start to put annotations/labels etc on resources that then conflict with the native integration? That said – our reasons for upgrading are to support kube 1.33 – which I realise means we have to upgrade both; it’s not worth having an operator on 1.33 that deploys a Flink native that won’t work! Thanks, Nic On 2025/07/08 16:06:19 Gyula Fóra wrote: > Hi David! > > I think we should definitely pick up the latest version if possible, we > have to make sure that this is compatible with how Flink uses the client > for native integration though. > > Cheers > Gyula > > On Tue, Jul 8, 2025 at 6:02 PM David Radley > <da...@uk.ibm.com<mailto:da...@uk.ibm.com>> wrote: > > > Hi, > > I can see that the Flink operator uses the 6.13.2 Kubenetes client . We > > are looking to move up to use 7.20 to pick up security fixes. I see > > https://github.com/fabric8io/kubernetes-client/blob/main/doc/MIGRATION-v7.md > > . > > > > Any thoughts on the impact and whether there is a community support for > > this upgrade? > > Kind regards, David. > > > > > > Unless otherwise stated above: > > > > IBM United Kingdom Limited > > Registered in England and Wales with number 741598 > > Registered office: Building C, IBM Hursley Office, Hursley Park Road, > > Winchester, Hampshire SO21 2JN > > > -- Nic Townsend IBM Event Processing Architect / Senior Engineer Slack: @nictownsend Bluesky: @nict0wnsend.bsky.social Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN
