Changes to DO and AS3 GitHub - no longer monitored

Hey everyone,

We've been keeping an eye on the recent changes around F5's GitHub repos and we get the direction — moving distribution to MyF5 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 — MyF5, 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.

Thanks in advance

I now tried the schema files from the rpm itself. The structure is not the same and it unfortunately does not work in my setup.

My declarations look like:

{
    "$schema": "https://raw.githubusercontent.com/F5Networks/f5-appsvcs-extension/main/schema/latest/as3-schema.json",
    "class": "AS3",
    "action": "deploy",
    "persist": true,
    "declaration": {
        "class": "ADC",
        "schemaVersion": "3.55.0",
        "tenant": {
        }
    }
}

In the rpm there are 4 schema files:

1. adc-schema.json
2. app-schema.json
3. as3-request-schema.json
4. settings-schema.json

But validation and autocompletion don't work with any of these. It seems the published schema on GitHub is some sort of combination of all of this files?

I opened a ticket for this.