Skip to content

proxy: Remove proxylib support#40757

Closed
sayboras wants to merge 1 commit intomainfrom
pr/tammach/remove-proxylib
Closed

proxy: Remove proxylib support#40757
sayboras wants to merge 1 commit intomainfrom
pr/tammach/remove-proxylib

Conversation

@sayboras
Copy link
Copy Markdown
Member

@sayboras sayboras commented Jul 27, 2025

Fixes: #38224

@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jul 27, 2025
@github-actions github-actions bot added the sig/policy Impacts whether traffic is allowed or denied based on user-defined policies. label Jul 27, 2025
@sayboras sayboras added the release-note/minor This PR changes functionality that users may find relevant to operating Cilium. label Jul 27, 2025
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jul 27, 2025
@sayboras
Copy link
Copy Markdown
Member Author

/test

@sayboras sayboras force-pushed the pr/tammach/remove-proxylib branch from 3547511 to cb5517a Compare July 28, 2025 02:00
@sayboras
Copy link
Copy Markdown
Member Author

/test

@sayboras sayboras force-pushed the pr/tammach/remove-proxylib branch 2 times, most recently from 2c0303c to 726ae31 Compare July 28, 2025 05:27
@sayboras
Copy link
Copy Markdown
Member Author

/test

@sayboras sayboras force-pushed the pr/tammach/remove-proxylib branch from 726ae31 to 2ab41c3 Compare July 28, 2025 15:00
@sayboras sayboras marked this pull request as ready for review July 28, 2025 15:00
@sayboras sayboras requested review from a team as code owners July 28, 2025 15:00
Copy link
Copy Markdown
Member

@jrajahalme jrajahalme left a comment

Choose a reason for hiding this comment

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

Looks right, hopefully there is no residual fallout from this!

@sayboras
Copy link
Copy Markdown
Member Author

/test

@sayboras
Copy link
Copy Markdown
Member Author

Looks right, hopefully there is no residual fallout from this!

The libcilium.so file is removed from Docker image, so hopefully we can catch issue if any, at least in embedded mode. IMO, it's better to perform the cleanup in early dev cycle rather than later.

Copy link
Copy Markdown
Member

@qmonnet qmonnet left a comment

Choose a reason for hiding this comment

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

  • The Issue link in your commit description is broken, trailing g: Relates: https://github.com/cilium/cilium/issues/38224g
  • The proxylib removal probably warrants a mention in the upgrade notes?

@qmonnet qmonnet added the upgrade-impact This PR has potential upgrade or downgrade impact. label Jul 29, 2025
@squeed
Copy link
Copy Markdown
Contributor

squeed commented Jul 29, 2025

I don't think we can do this yet.

I didn't see any deprecation warning for Kafka policies. Given that an end-user has no idea what proxylib is, but does know what Kafka policies are, we needed to add the warning there.

So, I think we can't remove kafka until v1.20.

@squeed squeed added the dont-merge/discussion A discussion is ongoing and should be resolved before merging, regardless of reviews & tests status. label Jul 29, 2025
@squeed
Copy link
Copy Markdown
Contributor

squeed commented Jul 29, 2025

@jrajahalme observes that the Kafka protocol version we support is very outdated, so it is unlikely to be in use. I'm still not comfortable deprecating something without proper notice, but perhaps this may be an exception. @joestringer, thoughts?

@joestringer
Copy link
Copy Markdown
Member

We should go through the standard deprecation cycle. It's a pity we didn't consider this just a few days earlier or we could have included this in the v1.18 release announcement. We'd better deprecate in v1.19 and remove in v1.20.

@sayboras
Copy link
Copy Markdown
Member Author

Thanks all for chime in and highlight the gaps, I should have added the note in v1.18.,

Agreed that we should delay the removal in 1.20, will send another PR to add deprecation note.

@sayboras sayboras closed this Jul 30, 2025
sayboras added a commit that referenced this pull request Aug 6, 2025
sayboras added a commit that referenced this pull request Aug 6, 2025
sayboras added a commit that referenced this pull request Aug 6, 2025
github-merge-queue bot pushed a commit that referenced this pull request Aug 7, 2025
rabelmervin pushed a commit to rabelmervin/cilium that referenced this pull request Aug 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dont-merge/discussion A discussion is ongoing and should be resolved before merging, regardless of reviews & tests status. release-note/minor This PR changes functionality that users may find relevant to operating Cilium. sig/policy Impacts whether traffic is allowed or denied based on user-defined policies. upgrade-impact This PR has potential upgrade or downgrade impact.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CFP: Deprecate Cilium Envoy Go extension

7 participants