Skip to content

Conversation

@jochenehret
Copy link

  • and add some general information on IPv6 support

* and add some general information on IPv6 support
@jochenehret
Copy link
Author

Note: The mentioned capi-release v1.212.0 is not yet shipped. Please wait for the new release before merging this PR.

@anita-flegg anita-flegg marked this pull request as draft July 7, 2025 13:10
@anita-flegg
Copy link
Contributor

@ameowlia , @Gerg , what TPCF branches should include this change?
Thanks!


ASGs define **allow** rules, and their order of evaluation is unimportant when multiple ASGs apply to the same space or deployment. The platform sets up rules to filter and log outbound network traffic
from app and task instances. ASGs apply to both buildpack-based and Docker-based apps and tasks.
from app and task instances. ASGs apply to both buildpack-based and Docker-based apps and tasks. Since capi-release v1.212.0, IPv6 is supported in ASGs.
Copy link
Member

@ameowlia ameowlia Jul 10, 2025

Choose a reason for hiding this comment

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

Suggested change
from app and task instances. ASGs apply to both buildpack-based and Docker-based apps and tasks. Since capi-release v1.212.0, IPv6 is supported in ASGs.
from app and task instances. ASGs apply to both buildpack-based and Docker-based apps and tasks. Since capi-release v1.212.0, IPv6 is supported in ASGs.

Really? I assume you will also need some cf-networking changes for this to work, which are not merged yet. We should wait until all of the code is released and the docs should references all of the versions of different releases required.

Copy link
Member

Choose a reason for hiding this comment

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

Is meanwhile everything merged?

cf-networking-release v3.74.0 mentions IPv6 improvements and I don't see open PRs anymore.

@ameowlia
Copy link
Member

@ameowlia , @Gerg , what TPCF branches should include this change? Thanks!

When this change lands it probably will not be backported. I don't think it will be included even in 10.3, so I would keep it just on "master".

@stephanme stephanme marked this pull request as ready for review August 26, 2025 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants