jiebi/CodeConvo huggingface dataset:
Change:
date: 2021-04-06 slug: podsecuritypolicy-deprecation-past-present-and-future --- **Author:** Tabitha Sable (Kubernetes SIG Security) <ins> {{% pageinfo color="primary" %}} **Update:** *With the release of Kubernetes v1.25, PodSecurityPolicy has been removed.* *You can read more information about the removal of PodSecurityPolicy in the [Kubernetes 1.25 release notes](/blog/2022/08/23/kubernetes-v1-25-release/#pod-security-changes).* {{% /pageinfo %}} </ins> PodSecurityPolicy (PSP) is being deprecated in Kubernetes 1.21, to be released later this week. This starts the countdown to its removal, but doesn’t change anything else. PodSecurityPolicy will continue to be fully functional for several more releases before being removed completely. In the meantime, we are developing a replacement for PSP that covers key use cases more easily and sustainably. What are Pod Security Policies? Why did we need them? Why are they going away, and what’s next? How does this affect you? These key questions come to mind as we prepare to say goodbye to PSP, so let’s walk through them together. We’ll start with an overview of how features get removed from Kubernetes.

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update (but check with the author, before you do) Make it obvious that your change is an update to an existing article. Hyperlink to Why is this needed PodSecurityPolicy is no longer deprecated; it is actually removed. It helps to amplify that story. Comments /area blog Follows on from
/language en
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 label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/retitle Update PSP deprecation blog article to link to v1.25 release blog
/assign
Any suggestion from your end?
??
This seems like a good idea. Perhaps add something like this, up at the top of the document?
Change:
1. Get a shell into the restarted Container: <del> kubectl exec -it redis -- /bin/bash </del> <ins> kubectl exec -it redis -- /bin/bash </ins> 1. In your shell, goto `/data/redis`, and verify that `test-file` is still there.

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: This page has extra spaces before the commands: I am not sure it's a more systemic problem, but this causes commands to not to show up on the bash history (undesirable). Proposed Solution: Page to Update: /assign
A cursory look through the rest of the docs under Configure Pods and Containers showed that one out of four docs also had this issue. I'll make this change as I update the callouts.
Change:
{{< feature-state for_k8s_version="v1.12" state="beta" >}} <!-- steps --> The KMS encryption provider uses an envelope encryption scheme to encrypt data in etcd. The data is encrypted using a data encryption key (DEK); a new DEK is generated for each encryption. The DEKs are encrypted with a key encryption key (KEK) that is stored and managed in a remote KMS. The KMS provider uses gRPC to communicate with a specific KMS

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: There are indentation errors in the yaml files of EncryptionConfiguration. For example in the following yaml, lines after "- secrets" should indent two to the right. ! Proposed Solution: Correct the indentation errors. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Is it right to have in the fixed page?
I checked the preview page, and it's still wrong. I've close my PR.
It should looks like this or "secrets" is the subcontent of the second "resources", and "providers" is with the same level of the second "resources". Although I modified the markdown, the rendered webpage is still wrong.
/priority backlog /language en /help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /priority backlog /language en /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/remove-lifecycle rotten /assign
Change:
/docs/setup/turnkey/aws/     /docs/setup/production-environment/turnkey/aws/   301 /docs/setup/turnkey/alibaba-cloud/     /docs/setup/production-environment/turnkey/alibaba-cloud/   301 /docs/setup/turnkey/azure/     /docs/setup/production-environment/turnkey/azure/   301 <del> /docs/setup/turnkey/clc/     /docs/setup/production-environment/turnkey/clc/   301 </del> /docs/setup/turnkey/gce/     /docs/setup/production-environment/turnkey/gce/   301 /docs/setup/turnkey/icp/     /docs/setup/production-environment/turnkey/icp/   301 /docs/setup/on-premises-vm/cloudstack/     /docs/setup/production-environment/on-premises-vm/cloudstack/   301

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: is very dated; it talks about “minions” rather than nodes, which means that Kubernetes has moved on quite a lot since that page was last accurate. Proposed Solution: Either: delete the page, and justify that deletion review the page and update it to be current. Page to Update: Notes: “3rd party content in documentation” may be relevant here. /kind cleanup /language en /priority backlog
Hello I shall work on this issue and submit the PR for the same. Thanks
:ok_hand:
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Still needs fixing. /remove-lifecycle stale
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Let's remove based on
/remove-lifecycle stale
Change:
* `MinAge`: the minimum age at which the kubelet can garbage collect a container. Disable by setting to `0`. <del> * `MaxPerPodContainer`: the maximum number of dead containers each Pod pair </del> <ins> * `MaxPerPodContainer`: the maximum number of dead containers each Pod </ins> can have. Disable by setting to less than `0`. * `MaxContainers`: the maximum number of dead containers the cluster can have. Disable by setting to less than `0`.

Discussion:
The description of under mentions without explaining what it means: I suspect that this is a typo and should be removed.
/sig docs /language en
/kind documentation
/assign
/retitle Confusing word (pod pair) in Garbage collection page.
/triage accepted
Change:
You can have multiple paragraphs and block-level elements inside an admonition. <del> | Or | a | table | </del> <ins> You can also add tables to organize and highlight key information. | Header 1 | Header 2 | Header 3 | | -------- | -------- | -------- | | Data 1   | Data A   | Info X   | | Data 2   | Data B   | Info Y   | </ins> {{< /note >}} {{< caution >}}

Discussion:
Problem: ! Proposed Solution: I have no idea because I have never used Hugo Page to Update:
/area web-development /triage accepted
Can I take care of it?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
It is not clear what is the next step to take this issue to closure. I see tried a number of things in Is the issue that the table "borders" are not rendered correctly in the Note admonition? It seems Hugo is not able to render the borders of the table when it is inside a Note admonition block. In this case it should be reported as a bug to Hugo, right? In the meanwhile, I propose we remove the part of having support for a table inside a Note from the Propose to remove from the below section. !
I have raised a for support in the Hugo forums.
There is an answer on the Hugo forum stating that this is not a Hugo issue. The suggestion is to fix the CSS. Any pointers?
Change:
```powershell # Example <del> .Install-Containerd.ps1 -ContainerDVersion v1.4.1 </del> <ins> .Install-Containerd.ps1 -ContainerDVersion 1.4.1 </ins> ``` {{< /note >}}

Discussion:
Install containerd with powershell do not work with .Install-Containerd.ps1 -ContainerDVersion v1.4.1. The download url is ''. So ".Install-Containerd.ps1 -ContainerDVersion 1.4.1." will work the command.
I think this might be a bug in rather than in the Kubernetes documentation. If so, you could report this via
/triage accepted /assign /sig windows
See
Change:
Hopefully I can do some more posts about advanced Kubernetes topics such as changing the cluster size and number of Node.js web server replicas, using different environments (dev, staging, prod) on the same cluster, and doing rolling updates. Thanks to [Mark Mandel](https://medium.com/@markmandel), [Aja Hammerly](https://medium.com/@thagomizer), and [Jack Wilber](https://medium.com/@jack.g.wilber). [Some rights reserved](http://creativecommons.org/licenses/by/4.0/) by the author.

Discussion:
NodeJS 0.10 is going into security-only release mode very soon. The first version of 0.10 was released in March 2013, so it's over 3 years old. It would be great if we could update the tutorial/dockerfile to list the latest (or at least a newer) nodejs version.
Resolved by, thanks to
Change:
Deployment 是管理 Pod 创建和扩展的推荐方法。 <!-- <del> 1. Katacoda environment only: At the top of the terminal pane, click the plus sign, and then click open a new terminal. </del> <ins> 1. Katacoda environment only: At the top of the terminal pane, click the plus sign, and then **Open New Terminal**. </ins> --> <del> 1. 仅 Katacoda 环境：在终端窗格的顶部，点击加号，然后点击 **Open a new terminal**。 </del> <ins> 1. 仅 Katacoda 环境：在终端窗格的顶部，点击加号，然后点击 **Open New Terminal**。 </ins> <!-- 1. Use the `kubectl create` command to create a Deployment that manages a Pod. The

Discussion:
Numbers in the following list may be not up to date. Please run again before working on each of them.
/language zh /triage accepted /help
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /language zh /triage accepted /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
Change:
The responsibilities of each role are described below. - [Contact](#contact) <ins> - [Security Embargo Policy](#security-embargo-policy) </ins> - [Handbooks](#handbooks) - [Release Managers](#release-managers) - [Becoming a Release Manager](#becoming-a-release-manager)

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Mention the within , or link to it. Why is this needed Readers might have an interest in knowing how security fixes are planned and communicated. Comments /sig release /sig security /language en /kind feature
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 label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign I can work on this.
Hi Please suggest which option from the following I will go with In this, we will have to make a page for embargo policy(security-embargo-) as we do not mention the link directly. 1) Copy the whole content from the to security-embargo- which seems redudant as it already mention in kubernete/security. 2) Mention the below text and then the link to for more details like:
I can clarify: this issue is about explaining that some information about upcoming releases is subject to embago, and that there is a defined policy about how those embargos are set. I don't see a need to mention how to join the mailing list for distributors within If someone is maintaining a Kubernetes distribution, I hope they're able to follow hyperlinks well enough to work that out. We have readers who might not think to look there. That's why we should refer to it (a hyperlink could be OK).
Thanks for suggestion. will create a pr for it soon.
fixed it here:
Change:
<a href= "https://events.linuxfoundation.org/kubecon-cloudnativecon-open-source-summit-ai-dev-china/register/?utm_source=kubernetes&utm_medium=all&utm_campaign=kubeconcn24&utm_content=slim-banner"> Buy your ticket now! 21 - 23 August | Hong Kong </a> <ins> - name: KubeCon 2024 NA startTime: 2024-09-30T00:00:00  #Added in https://github.com/kubernetes/website/pull/48086 endTime: 2024-11-15T18:00:00 style: >- background: linear-gradient(90deg, rgba(64,66,169,1) 60%, rgba(0,81,181,1) 100%); color: #fffff; title: | <img src ="/images/announcements/kccnc-na-2024-white.svg" style="float: right; height: 100px;" /> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/">KubeCon + CloudNativeCon 2024</a> message: | Join us for three days of incredible opportunities to collaborate, learn and share with the cloud native community.<br/> <a href= "https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/register/?utm_source=kubernetes&utm_medium=homepage&utm_campaign=KubeCon-NA-2024&utm_content=top-banner"> Buy your ticket now! 12 - 15 November | Salt Lake City </a> </ins>

Discussion:
This is a Feature Request What would you like to be Set a banner to announce KubeCon 2024 NA Why is this needed We usually turn on a banner for the upcoming KubeCon about 4 weeks ahead of the event. Logos are available from: (Note: be sure to copy the logo into this repo) should help with text. Also see the config from a last year's KubeCon. Comments This change will need approval. I would like to set the banner to start on the ~Oct 14, 2024~ Sep 30 and to end on Nov 15, 2024 at 1800 CET (UTC+1). edit: We've been asked if we can do a 6 week banner rather than a 4 week run. /priority important-soon
/triage accepted
/assign
/assign
Change:
Setup | [All heading and subheading URLs](/docs/setup/) Tutorials | [Kubernetes Basics](/docs/tutorials/kubernetes-basics/), [Hello Minikube](/docs/tutorials/hello-minikube/) Site strings | [All site strings](#Site-strings-in-i18n) in a new localized TOML file <ins> Releases | [All heading and subheading URLs](/releases) </ins> Translated documents must reside in their own `content/**/` subdirectory, but otherwise follow the same URL path as the English source. For example, to prepare the [Kubernetes Basics](/docs/tutorials/kubernetes-basics/) tutorial for translation into German, create a subfolder under the `content/de/` folder and copy the English source:

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be I propose that should include Why is this needed The releases page (just the front page, and not requiring any pages within it) is a key document to make available to readers. The shortcode this page uses already has localization support. I think we should localize this page. Comments If we accept this issue, we should also open one issue per downstream localization, about making sure that that localization team works on and localizes for their target localization. Link each of those issues back to this one, which then becomes an umbrella issue.
PS. The localization is on this one, and shows an example of what success looks like. There's one paragraph in the shortcode that doesn't yet localize; if you look at the rendered page you'll see that it's marked as English. Fixing that would be a separate issue.
/triage accepted
/language en /help
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /language en /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Hi if the issue is still open, can I work on it?
/assign Sure
do you have any questions about how to get started? You're very welcome to open a pull request.
Hey I made the PR, if you can review it that would be great!
Change:
The output displays that the Deployment was created: ``` <del> NAME         READY   UP-TO-DATE   AVAILABLE   AGE redis-master 1/1     1            1           55s </del> <ins> NAME    READY   UP-TO-DATE   AVAILABLE   AGE mongo   1/1     1            1           2m21s </ins> ``` The Deployment automatically manages a ReplicaSet.

Discussion:
uses manifests However, these files were removed in . The new example is using mongodb instead of redis, and so, the document needs to be updated overall. The page to update:
/language en
/kind bug /language en /priority backlog /triage accepted /help Thanks
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /kind bug /language en /priority backlog /triage accepted </details
/assign

On Forward a local port to a port on the Pod section this should be
/triage needs-information
Could you please link the page
This page
/triage accepted /kind bug /help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /triage accepted /kind bug /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/remove-triage needs-information
/assign
Change:
Annotations:         <none> Selector:            run=my-nginx Type:                ClusterIP <ins> IP Family Policy:    SingleStack IP Families:         IPv4 </ins> IP:                  10.0.162.149 <ins> IPs:                 10.0.162.149 </ins> Port:                <unset> 80/TCP <ins> TargetPort:          80/TCP </ins> Endpoints:           10.244.2.5:80,10.244.3.4:80 Session Affinity:    None Events:              <none>

Discussion:
Would be good to include the new fields in the output such as ,, and . These are related to dual stack deployments but since the same IPv4 address appear twice in a single stack output I think it is worth updating the sample outputs.
/retitle Stale output in Connecting Applications with Services URL of tutorial is ( it's definitely helpful if you include that detail) /language en /kind bug
/triage accepted
/sig network
/assign
I will update output with latest one
Change:
<ins> apiVersion: v1 kind: Pod metadata: name: volume-test spec: containers: - name: container-test image: busybox volumeMounts: - name: all-in-one mountPath: "/projected-volume" readOnly: true volumes: - name: all-in-one projected: sources: - secret: name: mysecret items: - key: username path: my-group/my-username - downwardAPI: items: - path: "labels" fieldRef: fieldPath: metadata.labels - path: "cpu_limit" resourceFieldRef: containerName: container-test resource: limits.cpu - configMap: name: myconfigmap items: - key: config path: my-group/my-config </ins>

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Translate into Japanese. Why is this needed This page has not been translated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted
Change:
- title: Other Resources section: <del> - title: Known Issues path: /docs/user-guide/known-issues/ </del> - title: Kubernetes Issue Tracker on GitHub path: https://github.com/kubernetes/kubernetes/issues/ - title: Report a Security Vulnerability

Discussion:
This page is woefully out of date: docs/user-guide/known-issues/ We should move the content to the 1.0 release notes and delete the page. cc
already contains this info. I'll delete the file.
cc I can't see how to delete a file using this new edit-in-place interface. Maybe it's a permission issue?
These items are all in flight - But I have no power to assign or merge anything.
Nice work, David. :)