upgraded tools in makefile

[AndrewChubatiuk]

updated all tools in makefile
replaced Deprecated: prefixed comments with custom deprecated markers that are rendered as shown below

@makasim @vrutkovs what do you think about adding the same +released marker to inform about release since which parameter is available?

---

Summary by cubic

Upgraded build tools and improved API/CRD docs by switching to custom deprecated markers and a pinned crd-ref-docs fork. Also increased doc render depth and regenerated client/informer code to v0.35 with context-aware watch support.

• Refactors

  • Replaced “Deprecated:” comments with +deprecated markers (with values) and updated the doc template to render deprecation notes.
  • Updated docs generation: added --max-depth=60, set Kubernetes version to 1.35, regenerated CRDs (controller-gen v0.20.0) and docs.
  • Regenerated clients/informers/listers to v0.35: moved to cache.ToListWatcherWithWatchListSemantics, added context-aware List/Watch, updated fake client to pass ListOptions and declare unsupported WatchList semantics, and simplified setConfigDefaults.

• Dependencies

  • Bumped tool versions: kustomize, controller-tools, envtest, golangci-lint, codegenerator, kind, OLM, operator-sdk, OPM, yq, ginkgo.
  • Switched crd-ref-docs to github.com/AndrewChubatiuk/crd-ref-docs and pinned.
  • CI: install libgpgme-dev in GitHub Actions before tests.

^{Written for commit f67f1c2. Summary will update on new commits.}

[cubic-dev-ai]

2 issues found across 11 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="api/operator/v1beta1/vmauth_types.go">

<violation number="1" location="api/operator/v1beta1/vmauth_types.go:226">
P2: Validation ignores src_headers. A URL map that only sets src_headers will still fail the “at least one must be defined” check because SrcHeaders isn’t included in the condition. Include SrcHeaders in the empty check to match the error message and intended behavior.</violation>
</file>

<file name="docs/templates/api/type.tpl">

<violation number="1" location="docs/templates/api/type.tpl:37">
P3: Use a valid HTML line break tag instead of `</br>`; `<br/>` is the correct void element syntax.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[makasim]

@makasim @vrutkovs what do you think about adding the same +released marker to inform about release since which parameter is available?

It's reasanoble to have it in general. Though I might not know all the specifics of the operator repository development process

[vrutkovs]

what do you think about adding the same +released marker to inform about release since which parameter is available?

That seems to duplicate CHANGELOG functionality. Also, our docs are for the latest released version only, so this tag is useless for docs too. What other purposes for this tag do you see?

[AndrewChubatiuk]

That seems to duplicate CHANGELOG functionality. Also, our docs are for the latest released version only, so this tag is useless for docs too. What other purposes for this tag do you see?

• people may use not up to date docs for opertor/k8s-stack installation, where operator may lack properties described in API.
• those who already uses k8s-stack/operator of old version and would like to enable some functionality on CR using property

it's hard to check changelog each time you need to enable a new property