Disable the statusoptional linter

[JoelSpeed]

This is legacy advice that doesn't apply well to types with status subresource, so I'd rather we disable it

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci]

Hello @JoelSpeed! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[coderabbitai]

Walkthrough

The golangci-lint configuration file is updated to explicitly disable the statusoptional check under kubeapilinter settings. This modifies the effective set of enabled linters without altering codebase logic.

Changes

Cohort / File(s)	Change Summary
Linter Configuration \.golangci\.yaml	Added disable list under kubeapilinter settings to explicitly disable statusoptional check

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 816f2d7 and 71ef3c0.

📒 Files selected for processing (1)

• .golangci.yaml (1 hunks)

🔇 Additional comments (1)

.golangci.yaml (1)

20-21: LGTM! Configuration change is correctly structured.

The addition of the disable: section with statusoptional is properly formatted with correct YAML indentation and aligns with the PR objective. The explanatory comment clearly documents the rationale for disabling this legacy kubeapilinter check.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[everettraven]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven

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 [everettraven]

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

[openshift-ci]

@JoelSpeed: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.