search

kubernetes / website

Kubernetes website and documentation repo:
https://kubernetes.io
Creative Commons Attribution 4.0 International
4.49k stars 14.43k forks source link

Improvement for k8s.io/docs/tutorials/kubernetes-basics/update/update-intro/ #39493

Closed MAMware closed 8 months ago

MAMware commented 1 year ago

/kind bug /language en Hi @MAMware , any contribution for improvement is welcome, you can raise a PR showing the changes you are proposing

Publicado originalmente por @Ritikaa96 en https://github.com/kubernetes/website/issues/39472#issuecomment-1431734105

@Ritikaa96, first time user here. Below is my proposal, btw in GitHub im both using the app and the web, over android DeX. There might issues in the way im doing ths PR becouse lack of knoledge on both platforms

original

In the previous module we scaled our application to run multiple instances. This is a requirement for performing updates without affecting application availability. By default, the maximum number of Pods that can be unavailable during the update and the maximum number of new Pods that can be created, is one. Both options can be configured to either numbers or percentages (of Pods). In Kubernetes, updates are versioned and any Deployment update can be reverted to a previous (stable) version.

proposed revision

In the previous module we scaled our application to run multiple instances. This is a requirement for performing updates without affecting application availability. By default, the maximum number of Pods that can be unavailable and can be created during the update, is one. Both options can be configured to either a fixed quantity or percentile of Pods. In Kubernetes, updates are versioned and any Deployment update can be reverted to a previous version.

k8s-ci-robot commented 1 year ago

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
sftim commented 1 year ago

/retitle Improvement for k8s.io/docs/tutorials/kubernetes-basics/update/update-intro/

Ritikaa96 commented 1 year ago

Hi @MAMware , by creating PR means cloning the website and making changes . I can understand challenges with first time contribution. Please refer:https://kubernetes.io/docs/contribute/ for raising PR: https://kubernetes.io/docs/contribute/new-content/open-a-pr/#changes-using-github

Biswajit-Mohapatra2 commented 1 year ago

/assign

Ritikaa96 commented 1 year ago

Hi @Biswajit-Mohapatra2 , Even when its been a long since we get any response, It's recommended to ask members if they aren't working on it or not before raising PR. As mentioned earlier by @MAMware , he might be working on the same.

MAMware commented 1 year ago

im not since i understood that a revamp/mods for the site are on its way. is there a timeline?

Ritikaa96 commented 1 year ago

@MAMware it is better to close an issue as soon as you can. if you are busy you can mention that you are pre-occupied and someone else can take it up.

sftim commented 1 year ago

Our no cookie licking policy means that anyone is welcome to open a PR that closes an open issue. It's still friendly to reach out to people who might already be working on the same thing.

See https://www.redhat.com/en/blog/dont-lick-cookie for an explanation of the jargon.

k8s-triage-robot commented 1 year ago

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

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

You can:

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

/lifecycle stale

Ritikaa96 commented 11 months ago

Hi @MAMware , @Biswajit-Mohapatra2 Are you working on this Issue? If not you can close it

MAMware commented 11 months ago

hi, i thought that the website/tutorial was goin to have a complete overhaul, if not i would like to contribute.

Marcos Amado Meneses

Ingeneria en Calidad del Software - UTN Gestion de Empredimientos - Siglo 21 Project Management - ICDA

From: Ritika @.> Sent: Monday, November 20, 2023 12:58:55 AM To: kubernetes/website @.> Cc: Marcos Meneses @.>; Mention @.> Subject: Re: [kubernetes/website] Improvement for k8s.io/docs/tutorials/kubernetes-basics/update/update-intro/ (Issue #39493)

Hi @MAMwarehttps://github.com/MAMware Are you working on this Issue?

— Reply to this email directly, view it on GitHubhttps://github.com/kubernetes/website/issues/39493#issuecomment-1818189693, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQOWOZHUNG262D4R6DK7XX3YFLIP7AVCNFSM6AAAAAAU6HHPSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJYGE4DSNRZGM. You are receiving this because you were mentioned.Message ID: @.***>

k8s-triage-robot commented 9 months ago

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

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

You can:

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

/lifecycle rotten

k8s-triage-robot commented 8 months ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 8 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/website/issues/39493#issuecomment-1951703995): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.