docs: update installation instructions

[fmuyassarov]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

Promote latest (and first) published Helm chart as the primary install method and move the raw manifest to a legacy fallback.

The chart is already in the production registry:

skopeo list-tags docker://registry.k8s.io/networking/dranet
[9:37 AM]skopeo list-tags docker://registry.k8s.io/networking/charts/dranet
{
    "Repository": "[registry.k8s.io/networking/charts/dranet](http://registry.k8s.io/networking/charts/dranet)",
    "Tags": [
        "v1.3.0"
    ]
}

and quick installation test passed to test artifact pulling worked fine

helm install dranet oci://registry.k8s.io/networking/charts/dranet --version v1.3.0
Pulled: [registry.k8s.io/networking/charts/dranet:v1.3.0](http://registry.k8s.io/networking/charts/dranet:v1.3.0)
Digest: sha256:762b9725c1dc45727741372b2c6188ef145f5809785500a1d575c6950891fec3
NAME: dranet
LAST DEPLOYED: Fri May 29 06:38:53 2026
NAMESPACE: default
STATUS: deployed
REVISION: 1
DESCRIPTION: Install complete
TEST SUITE: None

Which issue(s) this PR is related to:

"N/A".

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

[netlify]

✅ Deploy Preview for dranet canceled.

Name	Link
🔨 Latest commit	6ecc357
🔍 Latest deploy log	https://app.netlify.com/projects/dranet/deploys/6a1991ad14eceb0008cd4df9

[fmuyassarov]

/cc @aojea @gauravkghildiyal

[aojea]

I'm a classic man, manifest is simpler and easier, helm adds a dependency that in this case is avoidable

[fmuyassarov]

I'm a classic man, manifest is simpler and easier, helm adds a dependency that in this case is avoidable

Fair enough. Would it makes sense at least to keep the oci based chart path here in the doc?

[aojea]

Fair enough. Would it makes sense at least to keep the oci based chart path here in the doc?

absolutely

[fmuyassarov]

Fair enough. Would it makes sense at least to keep the oci based chart path here in the doc?

absolutely

updated

[gauravkghildiyal]

Thanks @fmuyassarov

@aojea this seems simple enough and your suggestions were addressed. So I'm proceeding with approving

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fmuyassarov, gauravkghildiyal

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [gauravkghildiyal]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment