python icon indicating copy to clipboard operation
python copied to clipboard
verified publisher icon kubernetes-client

Errouneous link for [object] type in V1RollingUpdateDeployment and V1HTTPGetAction pages

Open FabienZouaoui opened this issue 1 year ago • 8 comments

Link to the issue (please include a link to the specific documentation or example): https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/V1RollingUpdateDeployment.md https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/V1HTTPGetAction.md

Description of the issue (please include outputs or screenshots if possible): Object type link point to https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/.md which returns a 404

FabienZouaoui avatar Feb 23 '24 10:02 FabienZouaoui

The documentation is generated from upstream k/k openapi spec. This needs to be fixed in the upstream

roycaihw avatar Feb 26 '24 17:02 roycaihw

Hi, is this issue still open. Can I have the opportunity to work on this issue.

sharsha315 avatar Mar 30 '24 14:03 sharsha315

Hi, is this issue still open. Can I have the opportunity to work on this issue.

Yes please feel free to assign this issue to yourself. /assign @sharsha315

roycaihw avatar Apr 01 '24 16:04 roycaihw

Hi @roycaihw , does this issue appear to stem from the swagger.json file? Additionally, I've noticed similar problems in several other files beyond those mentioned earlier. Could you please provide clarification on how to resolve this issue and offer guidance for handling similar occurrences in the future? Thank you for your support!

sharsha315 avatar Apr 15 '24 14:04 sharsha315

Yes this documentation is generated based on the upstream openapi spec: https://github.com/kubernetes/kubernetes/tree/master/api/openapi-spec. Could you verify if the upstream has the proper type defined for the fields (not an object)?

roycaihw avatar Apr 22 '24 17:04 roycaihw

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jul 21 '24 17:07 k8s-triage-robot

/remove-lifecycle stale

sharsha315 avatar Jul 22 '24 08:07 sharsha315