Add empty experimental ops file for IPv6 enablement #1253
Conversation
|
Info: This 'empty' experimental ops file is intended for the CF component teams like Diego,... to add their component specifics for the IPv6 egress enablement to the ops file. We also want to have just one ops file for the IPv6 egress enablement and not for each cf component a separate one. This should simplify the operators 'life'. |
operations/experimental/README.md
Outdated
| | [`use-mysql-version-8.0.yml`](use-mysql-version-8.0.yml) | Deploys or upgrades Percona 8.0 as the internal database. | ***Deprecated as we now use MySQL version 8.0 by default.*** | **NO** | | ||
| | [`use-trusted-ca-cert-for-apps-cflinuxfs4.yml`](use-trusted-ca-cert-for-apps-cflinuxfs4.yml) | Same as [`use-trusted-ca-cert-for-apps.yml`](../use-trusted-ca-cert-for-apps.yml), but for cflinuxfs4 stack | ***Deprecated as we integrate cflinuxfs4 directly into cf-deployment.yml*** | **NO** | | ||
| | [`use-noble-stemcell.yml`](use-noble-stemcell.yml) | Use the new beta Noble stemcell | This is incompatible with `../use-compiled-releases.yml` | **NO** | | ||
| | [`enable-ipv6-egress.yml`](enable-ipv6-egress.yml) | Use the new beta Noble stemcell | Notes will be updated once all components are ready. | **NO** | |
There was a problem hiding this comment.
Wrong description (copied from Noble ops file).
|
and we should also mention in the docu that the experimental ops file is still WIP as long the contributions from the other teams are missing. |
3 participants
Please take a moment to review the questions before submitting the PR
The PR is pushed to the develop branch.
WHAT is this change about?
This experimental operations file is designed for CF component teams, such as Diego and etc., to incorporate their specific requirements for IPv6 egress enablement. The goal is to maintain a single ops file for IPv6 egress across all components, rather than creating individual files for each CF component. This approach is intended to streamline the process for operators. Once all components have included their IPv6 configurations, we can consolidate the ops file and update the documentation accordingly.
What customer problem is being addressed? Use customer persona to define the problem e.g. Alana is unable to...
Growing need for IPv6 for all customers.
Has a cf-deployment including this change passed cf-acceptance-tests?
Does this PR introduce a breaking change? Please take a moment to read through the examples before answering the question.
How should this change be described in cf-deployment release notes?
This is just an empty OPS file which is going to be populated later.
Does this PR introduce a new BOSH release into the base cf-deployment.yml manifest or any ops-files?
Does this PR make a change to an experimental or GA'd feature/component?
What is the level of urgency for publishing this change?
Tag your pair, your PM, and/or team!
@oliver-heinrich @iaftab-alam