OSAC-1430: osac-operator Helm chart: wrong env var name + missing RBAC for publicipattachments

[osac-jira-ai-issue-solver]

Resolves OSAC-1430

Summary

OSAC-1430: Add Helm charts to main branch and fix env var + RBAC drift

The osac-operator Helm charts existed only on release tags (v0.0.1–v0.0.8), not on main. This PR brings them to main, synced with main's current operator state:

• Env var fix: The original chart used OSAC_ENABLE_CLUSTER_ORDER_CONTROLLER; this uses the correct OSAC_ENABLE_CLUSTER_CONTROLLER matching cmd/main.go
• RBAC sync: Helm ClusterRole now exactly matches kustomize config/rbac/role.yaml
• Deployment sync: Env vars match only the controllers on main (cluster, compute, tenant, networking)
• Binary path: Fixed to /manager matching main's Containerfile
• CRD sync: Helm CRD templates match config/crd/bases/
• Removed release-only features: ExternalIP*, PublicIPAttachment, BareMetalInstance, Storage controller, and console-proxy templates that aren't on main

Test plan

• helm template renders operator chart without errors
• helm lint passes for both operator and operator-crds charts
• Rendered ClusterRole matches kustomize config/rbac/role.yaml (diff is empty)
• Rendered deployment uses correct OSAC_ENABLE_CLUSTER_CONTROLLER env var
• Deploy via Helm to a cluster and confirm all four controllers start without RBAC errors
• Compare against kustomize deployment to verify functional parity

[openshift-ci-robot]

@osac-jira-ai-issue-solver[bot]: This pull request references OSAC-1430 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Resolves OSAC-1430

Summary

OSAC-1430: Add Helm charts to main branch and fix env var + RBAC drift

The osac-operator Helm charts existed only on release tags (v0.0.1–v0.0.8), not on main. This PR brings them to main, synced with main's current operator state:

• Env var fix: The original chart used OSAC_ENABLE_CLUSTER_ORDER_CONTROLLER; this uses the correct OSAC_ENABLE_CLUSTER_CONTROLLER matching cmd/main.go
• RBAC sync: Helm ClusterRole now exactly matches kustomize config/rbac/role.yaml
• Deployment sync: Env vars match only the controllers on main (cluster, compute, tenant, networking)
• Binary path: Fixed to /manager matching main's Containerfile
• CRD sync: Helm CRD templates match config/crd/bases/
• Removed release-only features: ExternalIP*, PublicIPAttachment, BareMetalInstance, Storage controller, and console-proxy templates that aren't on main

Test plan

• helm template renders operator chart without errors
• helm lint passes for both operator and operator-crds charts
• Rendered ClusterRole matches kustomize config/rbac/role.yaml (diff is empty)
• Rendered deployment uses correct OSAC_ENABLE_CLUSTER_CONTROLLER env var
• Deploy via Helm to a cluster and confirm all four controllers start without RBAC errors
• Compare against kustomize deployment to verify functional parity

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: osac-jira-ai-issue-solver[bot]
Once this PR has been reviewed and has the lgtm label, please assign akshaynadkarni for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[osac-jira-ai-issue-solver]

AI Session Costs

Session	Cost
New ticket	$7.20
Feedback (1) retry 1 (error)	$1.56
Feedback (1) retry 2 (no changes)	$0.84
Feedback (1) retry 2 (no changes)	$1.29
Feedback (1) retry 1 (no changes)	$1.13
Feedback (1) retry 1 (no changes)	$1.19
Feedback (1) retry 1 (no changes)	$1.00
Merge conflict resolution	$1.70
Feedback (1) (no changes)	$1.68
Feedback (1) retry 1 (no changes)	$1.16
Feedback (1) retry 2 (no changes)	$1.68
Feedback (1) retry 3 (unable)	$1.08
Feedback (2) (no changes)	$1.04
Merge conflict resolution	$0.69
Total	$23.24

[openshift-ci]

Hi @osac-jira-ai-issue-solver[bot]. Thanks for your PR.

I'm waiting for a osac-project member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[eranco74]

PR needs rebase.

[osac-jira-ai-issue-solver]

CI failures addressed in no-changes.

[osac-jira-ai-issue-solver]

In comment, @eranco74 said:

PR needs rebase.

I was unable to produce code changes to address this comment after multiple attempts.

[osac-jira-ai-issue-solver]

CI failures addressed in no-changes.

[osac-jira-ai-issue-solver]

CI failures addressed in no-changes.

[openshift-ci]

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.