I see Changes to DO and AS3 GitHub pages have been updated with these notices:
"
AS OF FEBRUARY 2026, THIS GITHUB REPOSITORY WILL NO LONGER BE MONITORED OR UPDATED.
This repository will remain available, at least temporarily. You can find the latest RPMs and other files on MyF5 Downloads. Refer to ‘Filing Issues and Getting Help’ for additional details.
"
I’m also seeing [Deprecated] notices on some VS Code extensions, which may or may not be related.
I haven’t been able to find any larger announcements regarding these.
I have not been able to find any additional detail.
Does anyone know if we are about to see a a large shift (or loss) of tooling around BIG-IP?
I’m in no direct position to provide guidance (no secret insight here), but from what I hear and suspect is this likely is more of a sign of added maturity (bringing AS3 , DO, and others closer) than anything else. Probably some ‘benefits’ of being more in-house in the development pipeline and having more ‘formal’ releases rather than what we have had in the past.
If so, hopefully this ends up overall good for these APIs/Tooling longevity, even if some processes might have to change in the short term. I will miss the easy access to create GitHub tickets / search through old issues (I personally always found that easier than trying to search through bug reports / active tickets for something else like bigip).
Still, I look forward to a more formal public update/announcement from F5 regarding this to better plan for the future.
I do not like this change. My current pipelines are downloading the RPM’s from GitHub. With the move to <a href://my.f5.com>MyF5</a> Downloads that would not be possible anymore.
I vote for a possibility to download files from <a href://my.f5.com>MyF5</a> without going through the current login process. This would be also great for other files like Attack Signatures.
Yeah, you’re not the only one reading into this; it does feel like a quiet shift rather than a clearly announced change. From what’s visible, AS3 and DO have already been moving toward a more “maintenance/LTS” style lifecycle for a while, with fewer feature updates and more compatibility-focused releases . So the GitHub “no longer monitored” notice seems less like a sudden kill switch and more like F5 formalizing what was already happening behind the scenes.
I wouldn’t expect an immediate break in existing setups; these tools are still widely used and should continue working; but it’s a pretty strong signal to start planning around newer approaches (Central Manager, BIG-IP Next, or API-driven automation). The lack of a big announcement is frustrating, but historically F5 has been shifting direction gradually rather than making hard deprecation calls upfront. Here is another discussion where you can add value:
Already noticing some disruption in usage, the old way of obtaining updated Schema file , and using it to validate against files offline no longer works.
This old link is now out of date, only covers up to v1.47 of DO, not the updated v1.48 that is available from downloads.f5.com :
I understand right this moment this is minimal impact (from what I can tell, only a small bugfix in v1.48) but this problem will compound.
If anyone at F5 can provide an alternative way to obtain updated schema files (or even update documentation pages over at clouddocs.f5.com which also still only show v1.47) I am all ears.
Good morning, Folks, I am the PM who implemented the changes on behalf of leadership. Let me address the changes.
No—this is not a signal that BIG-IP tooling is going away. These changes are part of aligning the Automation Toolchain with the broader BIG-IP Tools initiative. Moving images, RPMs, and related software to <a href://my.f5.com>MyF5</a> Downloads aligns with how F5 distributes its products today and helps ensure that F5 software is available in a single, centralized location rather than spread across multiple sites. This improves consistency and supports security and governance requirements.
Similarly, removing the GitHub Issues tab is intended to reduce shadow support and route issue resolution through the appropriate support and engineering channels. Having PMs solely manage GitHub issues did not scale well and was not the right long-term model for timely, well-supported resolution. The goal is to connect customers with the engineering resources and formal support processes needed to address issues more effectively.
Overall, the change is better understood as consolidation and operational maturity, not a broader loss of BIG-IP tooling. We are also rolling out the next generation of APIs on BIG-IP that address the challenges introduced with AS3. The deprecation notices you are seeing may be related to the same effort to streamline distribution, support, and lifecycle management across the BIG-IP Tools portfolio. Please don’t hesitate to reach out for a call and roadmap review.
many thanks for the detailed response on this topic. Moving the ATC to a central place makes sense to me. It would have been nice to have been given some advance notice, though.
First issue that should be addressed:
This change breaks my workflow for deploying this packages on my F5’s. Let me illustrate that:
Before:
New AS3 Version was released by F5
Get the download links from the release page
I update the URL in my central GitLab repository that has a pipeline to install this packages on my F5’s.
Pipeline installs new Version
You see, it is a simple and straight forward process.
Now:
New AS3 Version was released by F5
Got to the Download Site
Login with Credentials and second Factor
Download the AS3 RPM
Create the sha256 checksum file
Upload both to a local webserver
I update the URL in my central GitLab repository that has a pipeline to install this packages on my F5’s.
Pipeline installs new Version
You see, it does not make fun with this change.
A second issue that must be fixed:
I could not find a new URL for the schema file. I use in my all declarations:
This provides autocompletion and validation in VSCode. Where can I now point this declaration or where can I download the schema definition?
Third issue:
No overview of open bugs and feature requests for the ATC. I liked the issues view on GitHub and I regularly used it to search for known problems with AS3. New categories in the Bug Tracker could solve this issue. I hope you migrated all the GitHub issues.
Please don’t hesitate to reach out for a call and roadmap review.
I’ve already suggested an MVP call on this topic. I have already seen a roadmap for the new declarative API. It should be an alpha version in 21.1. right? Where is the documentation? I am willing to explore this new declarative approach in an early stage. Is there an EA program?
Thanks for clarification, looking forward to new declarative API and the way it will be sustained. But please, do not make a mistake again and do not plan to close access to imperative API. This is and will be needed not only by your tools like Insight etc, but also by our tools Thanks and good luck
We’ve been keeping an eye on the recent changes around F5’s GitHub repos and we get the direction — moving distribution to <a href://my.f5.com>MyF5</a> Downloads, routing support through official channels, that all makes sense. We also noticed the CIS container image is now being published to the Red Hat Container Registry, which is mentioned in the repo’s README.
What we can’t figure out is what’s happening with the Helm chart.
Most of us deploy CIS through Helm, and the chart sitting in the repo (f5-bigip-ctlr v0.0.35) hasn’t been touched since August 2025. On top of that, it still points to Docker Hub as the default image source — which now conflicts with the README telling people to go to the Red Hat registry. So right now, anyone deploying with default Helm values is pulling from a place F5 seems to be moving away from.
A few things we’d love clarity on:
- Is the Helm chart part of this migration at all? And if so, where will it end up — <a href://my.f5.com>MyF5</a>, ArtifactHub, somewhere else?
- Will there be an updated chart that reflects the Red Hat registry as the image source?
- If Helm isn’t going to be supported going forward, what’s the recommended way to deploy CIS — raw manifests, any other alternative?
We’re trying to get our pipelines aligned with where F5 is heading, but the Helm side feels like it got left behind in the transition. Would really appreciate any visibility on this.
AS3 3.57.0 silently appeared on the download site.
But
Where is the Changelog?
Where was this release announced?
Where is the updated schema file?
Forgive me, but I understand somewhat different under “Overall, the change is better understood as consolidation and operational maturity”. Or do I miss anything?
Thanks and good luck