profile
viewpoint
Misty Linville mistyhacks @google @apache San Francisco, CA https://mistyhacks.com/ Tech writer for Kubernetes at Google -- ASF member, HBase PMC chair, Kudu PMC member -- Previously at Docker, Cloudera, Red Hat

issue commentkubernetes/kubectl

kubectl describe hpa not working with v1.13.0

I just ran into this with kubectl and master both at v1.14.7.

tomfotherby

comment created time in 17 days

pull request commentkubernetes/website

Capitalize Pod, style guide edits

/unassign /assign @msau42

bobfuru

comment created time in a month

issue commentkubernetes-sigs/kubebuilder

Docs: Make the QuickStart a little more detailed with a Greeter example.

A quickstart usually focuses on a very specific task. The document you linked above seems more like an end-to-end solution, where you start with nothing and you end up with a completely functional solution. It seems like here, there should be some kind of a flow such as Installation -> Basic setup -> Create a project -> Deploy the project. Maybe the last two could actually be separate, and it could be a staged tutorial.

This is just one perspective without much background. Others will have other info.

erictune

comment created time in a month

push eventmistyhacks/website

Jim Angel

commit sha 111e6d1e57e6c3920384271238fbb3bc6b76bcf2

initial commit

view details

Sandeep Rajan

commit sha 22441ecaee8b26bf6d4372405a7da11285be31f0

Update content on kube-dns to coredns configmap translation (#13826) Updates and corrects the part of configmap for CoreDNS

view details

noctarius aka Christoph Engelbert

commit sha 99ae92bdf9dbf87bc873604cc69e60cb543c2b4a

Readded the link to Instana and Sysdig, which seem to have gone missing due to a merge error or anything like that during preparationg of the 1.14 release. (#14184) original pull request: https://github.com/kubernetes/website/pull/12977 Signed-off-by: noctarius <me@noctarius.com>

view details

Marek Counts

commit sha a1f811d8524e6e9dd8682927244252ed0e1a064b

Updated self-hosting documentation (#13866) * updated self-hosting documentation * removed more referances * updated wording * updated self-hosting warning to be more clear about the effects of pivot has on your cluster * Update content/en/docs/setup/independent/self-hosting.md Co-Authored-By: Klaven <mcounts@suse.com>

view details

Neville George

commit sha e2f8ae097e99b3f0196f162f659b165818d98090

Fixing the output of jsonpath (#14387) Items is an array and the [ ] are missing in the jsonpath

view details

Rajesh Deshpande

commit sha bacd21d2b82b5a68a6e8dd14161b2c93014f0b1b

Correcting sequence of tasks for manage cluster daemon (#14383) * Correcting order of display for daemon set tasks Correcting order of display for daemon set tasks * Correcting display order of daemon set task Correcting display order of daemon set task

view details

Aaron Sun

commit sha 2029b9b9d596ef63cba0f0ce83943c83c41b45be

Updated DaemonSet page to include SignalFx Agent. (#14385)

view details

Wojciech Tyczynski

commit sha c7c55c58834e13beb78a225d8ce5e467fc06cffc

Watch bookmarks documentation (#14379)

view details

Karen Bradshaw

commit sha 110f5e1d5f8552880174350de0a6ef74f6be3ead

move obj mgmt files to tasks (#14374) * move obj mgmt files to tasks * add redirects for moved files

view details

Ashish Thakur

commit sha f7fc6cebc3151aa15634a9ca26310491cb8189ec

Fixing grammatical error (#14389)

view details

Rajesh Deshpande

commit sha ea7af96d5de2a95ecfd82024f6f85e7df9b65d70

Correcting example to avoid ambiguity (#14354) Both local and pod port number are same i.e. 6379 which causes confusion to first time reader. This can be easily avoided by using two different port number.

view details

Raj Vaibhav Dubey

commit sha 6930b2167f198e80564f7f37b0488fd3fcf185bd

Changed the redisslave version from v1 to v3. (#14276)

view details

Rajakavitha1

commit sha d21ffb4c633567321575eb9bf8b19a3ef69e3986

Refractor _index.md (#14163)

view details

Chazzledazzle1

commit sha a7e4e00d515222aec7bc0e545b32120222f94682

Updated Linux Academy courses (#14303) * Updated Linux Academy courses * Apply suggestions from code review Co-Authored-By: Tim Bannister <tim@scalefactory.com> * Fix link syntax * Update overview.md

view details

Rajesh Deshpande

commit sha d135d566b192a970596ee44e12b5045a4fb2f32e

Correcting minikube quickstart steps (#14355) * Correcting minikube quickstart steps In minikube quickstart section , it was difficult to differentiate between command and its output. Also, There was no details given for each steps and its expected output. This PR fixes these issues. * Correcting number formatting Correcting number formatting * Correcting numbering Correcting numbering * Update content/en/docs/setup/minikube.md Co-Authored-By: Franklin Yu <franklinyu@hotmail.com> * Update content/en/docs/setup/minikube.md Co-Authored-By: Franklin Yu <franklinyu@hotmail.com> * Update content/en/docs/setup/minikube.md Co-Authored-By: Franklin Yu <franklinyu@hotmail.com> * Corrected formatting Corrected formatting * Correcting number sequence Correcting number sequence

view details

Jaice Singer DuMars

commit sha 3c7cae7b9d17ab411267efb1389f3f0adce2dfbf

Create blog post draft (#14384) * Create blog post draft * Fixed comma problem and updated Cloud

view details

Zach Corleissen

commit sha 3a44233bcf0299c5f548dcc94e03f7b50066e483

Edits for clarity (#14423)

view details

Meenakshi Kaushik

commit sha 0d471c4fc885c21bb52ebab64612fef67096529d

pick-right-solution.md (#14434) Added Cisco Container Platform under "On-Premises turnkey cloud solutions"

view details

Suhwan Cha

commit sha 6be86407785257b174d1deaf35d6f2cad12ac3d1

Fix link (#14438) * Update imperative-command.md * Update imperative-command.md

view details

Himanshu Pandey

commit sha 7aed682a896f14742ad5e26dad2c277a51d77c13

removed the junk character (#14430)

view details

push time in a month

pull request commentkubernetes/website

Remove mistyhacks@ from OWNERS_ALIASES

/assign @zacharysarah

mistyhacks

comment created time in a month

PR opened kubernetes/website

Remove mistyhacks@ from OWNERS_ALIASES

New role in day job means my ability to participate will be limited. It's been a privilege!

+0 -2

0 comment

1 changed file

pr created time in a month

create barnchmistyhacks/website

branch : remove_me

created branch time in a month

Pull request review commentkubernetes/website

Fixed few issues with Storage concepts section.

 A cluster administrator creates a number of PVs. They carry the details of the r #### Dynamic When none of the static PVs the administrator created matches a user's `PersistentVolumeClaim`, the cluster may try to dynamically provision a volume specially for the PVC.-This provisioning is based on `StorageClasses`: the PVC must request a+This provisioning is based on `StorageClass` objects: the PVC must request a [storage class](/docs/concepts/storage/storage-classes/) and the administrator must have created and configured that class in order for dynamic provisioning to occur. Claims that request the class `""` effectively disable dynamic provisioning for themselves. -To enable dynamic storage provisioning based on storage class, the cluster administrator+To enable dynamic storage provisioning based on *storage class*, the cluster administrator

Please use the Kubernetes object names. I added relevant links to the style guide in a previous comment.

draghuram

comment created time in 2 months

Pull request review commentkubernetes/website

Fixed few issues with Storage concepts section.

 weight: 20  {{% capture overview %}} -This document describes the current state of `PersistentVolumes` in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/) is suggested.+This document describes the current state of *persistent volumes* in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/) is suggested.

Marking up objects is covered here: https://kubernetes.io/docs/contribute/style/style-guide/#use-camel-case-for-api-objects (use camel-case, a bit further down it says not to split it into separate words like "Persistent Volume Claim")

I struggled to find where we explicitly say that we don't use mono text for object kinds, but I couldn't. I did find instances of it in the style guide itself, and I consider that somewhat definitive. For example: https://kubernetes.io/docs/contribute/style/style-guide/#use-simple-and-direct-language

We don't seem to have any stance about pluralizing, but as far as I know it's normal in Kubernetes to say, for instance, Ingresses. @steveperry-53 @Bradamant3 Do you have thoughts or more background?

I did notice that the PVC page does use mono text for the object kinds, so I guess you can leave yours in because the rest of the page could be cleaned up as part of a broader automated sweep. I was being more picky on this CL because it's good to ensure style adherence when a big new block of text is introduced.

draghuram

comment created time in 2 months

Pull request review commentkubernetes/website

Fixed few issues with Storage concepts section.

 Currently, only NFS and HostPath support recycling. AWS EBS, GCE PD, Azure Disk,  ### Mount Options -A Kubernetes administrator can specify additional mount options for when a Persistent Volume is mounted on a node.+A Kubernetes administrator can specify additional mount options for when a `PersistentVolume` is mounted on a node.  {{< note >}}-Not all Persistent volume types support mount options.+Not all persistent volume types support mount options.

Which do? Maybe "Only <foo> support mount options: <list>"

draghuram

comment created time in 2 months

Pull request review commentkubernetes/website

Fixed few issues with Storage concepts section.

 Currently, only NFS and HostPath support recycling. AWS EBS, GCE PD, Azure Disk,  ### Mount Options -A Kubernetes administrator can specify additional mount options for when a Persistent Volume is mounted on a node.+A Kubernetes administrator can specify additional mount options for when a `PersistentVolume` is mounted on a node.

Replace with just "You can". We use second person singular, to speak to the user directly, as much as possible. Do a sweep throughout the topic.

draghuram

comment created time in 2 months

Pull request review commentkubernetes/website

Fixed few issues with Storage concepts section.

 Currently, storage size is the only resource that can be set or requested.  Futu  {{< feature-state for_k8s_version="v1.13" state="beta" >}} -Prior to Kubernetes 1.9, all volume plugins created a filesystem on the persistent volume.+Prior to Kubernetes 1.9, all volume plugins created a filesystem on the `PersistentVolume`. Now, you can set the value of `volumeMode` to `block` to use a raw block device, or `filesystem`

I don't think you need to talk about how things were before in an unsupported version. Please rephrase.

draghuram

comment created time in 2 months

Pull request review commentkubernetes/website

Fixed few issues with Storage concepts section.

 Currently, storage size is the only resource that can be set or requested.  Futu  {{< feature-state for_k8s_version="v1.13" state="beta" >}} -Prior to Kubernetes 1.9, all volume plugins created a filesystem on the persistent volume.+Prior to Kubernetes 1.9, all volume plugins created a filesystem on the `PersistentVolume`.

Remove -- this version has been out of the support window for some time.

draghuram

comment created time in 2 months

Pull request review commentkubernetes/website

Fixed few issues with Storage concepts section.

 Pods use claims as volumes. The cluster inspects the claim to find the bound vol Once a user has a claim and that claim is bound, the bound PV belongs to the user for as long as they need it. Users schedule Pods and access their claimed PVs by including a `persistentVolumeClaim` in their Pod's volumes block. [See below for syntax details](#claims-as-volumes).  ### Storage Object in Use Protection-The purpose of the Storage Object in Use Protection feature is to ensure that Persistent Volume Claims (PVCs) in active use by a pod and Persistent Volume (PVs) that are bound to PVCs are not removed from the system as this may result in data loss.+The purpose of the *Storage Object in Use Protection* feature is to ensure that Persistent Volume Claims (PVCs) in active use by a pod and Persistent Volumes (PVs) that are bound to PVCs are not removed from the system as this may result in data loss.

Why not simplify: "Storage Object in Use Protection prevents PVCs and PVs from being removed while they are being used by Pods, to protect against data loss."

draghuram

comment created time in 2 months

Pull request review commentkubernetes/website

Fixed few issues with Storage concepts section.

 A cluster administrator creates a number of PVs. They carry the details of the r #### Dynamic When none of the static PVs the administrator created matches a user's `PersistentVolumeClaim`, the cluster may try to dynamically provision a volume specially for the PVC.-This provisioning is based on `StorageClasses`: the PVC must request a+This provisioning is based on `StorageClass` objects: the PVC must request a [storage class](/docs/concepts/storage/storage-classes/) and the administrator must have created and configured that class in order for dynamic provisioning to occur. Claims that request the class `""` effectively disable dynamic provisioning for themselves. -To enable dynamic storage provisioning based on storage class, the cluster administrator+To enable dynamic storage provisioning based on `StorageClass`, the cluster administrator

This reads like a prerequisite and should be introduced earlier. "You must enable.... before enabling...."

draghuram

comment created time in 2 months

Pull request review commentkubernetes/website

Fixed few issues with Storage concepts section.

 A cluster administrator creates a number of PVs. They carry the details of the r #### Dynamic When none of the static PVs the administrator created matches a user's `PersistentVolumeClaim`, the cluster may try to dynamically provision a volume specially for the PVC.-This provisioning is based on `StorageClasses`: the PVC must request a+This provisioning is based on `StorageClass` objects: the PVC must request a

How about removing "This...objects:" and rephraing the next part:

The <link>storage class</link> must exist before you try to dynamically provision storage."

draghuram

comment created time in 2 months

Pull request review commentkubernetes/website

Fixed few issues with Storage concepts section.

 This document describes the current state of `PersistentVolumes` in Kubernetes.  ## Introduction -Managing storage is a distinct problem from managing compute. The `PersistentVolume` subsystem provides an API for users and administrators that abstracts details of how storage is provided from how it is consumed. To do this we introduce two new API resources:  `PersistentVolume` and `PersistentVolumeClaim`.+Managing storage is a distinct problem from managing compute. The `PersistentVolume` subsystem provides an API for users and administrators that abstracts details of how storage is provided and how it is consumed. To do this we introduce two new API resources:  `PersistentVolume` and `PersistentVolumeClaim`.  A `PersistentVolume` (PV) is a piece of storage in the cluster that has been provisioned by an administrator or dynamically provisioned using [Storage Classes](/docs/concepts/storage/storage-classes/). It is a resource in the cluster just like a node is a cluster resource. PVs are volume plugins like Volumes, but have a lifecycle independent of any individual pod that uses the PV. This API object captures the details of the implementation of the storage, be that NFS, iSCSI, or a cloud-provider-specific storage system.  A `PersistentVolumeClaim` (PVC) is a request for storage by a user. It is similar to a pod. Pods consume node resources and PVCs consume PV resources. Pods can request specific levels of resources (CPU and Memory).  Claims can request specific size and access modes (e.g., can be mounted once read/write or many times read-only). -While `PersistentVolumeClaims` allow a user to consume abstract storage-resources, it is common that users need `PersistentVolumes` with varying-properties, such as performance, for different problems. Cluster administrators-need to be able to offer a variety of `PersistentVolumes` that differ in more+While *persistent volume claims* allow a user to consume abstract storage

Again, please remove this extra formatting.

draghuram

comment created time in 2 months

Pull request review commentkubernetes/website

Fixed few issues with Storage concepts section.

 This document describes the current state of `PersistentVolumes` in Kubernetes.  ## Introduction -Managing storage is a distinct problem from managing compute. The `PersistentVolume` subsystem provides an API for users and administrators that abstracts details of how storage is provided from how it is consumed. To do this we introduce two new API resources:  `PersistentVolume` and `PersistentVolumeClaim`.+Managing storage is a distinct problem from managing compute. The `PersistentVolume` subsystem provides an API for users and administrators that abstracts details of how storage is provided and how it is consumed. To do this we introduce two new API resources:  `PersistentVolume` and `PersistentVolumeClaim`.

Please remove "for users and administrators"

"is provided and consumed", please remove the extra words.

suggest "To configure storage, you create a PersistentVolume and PersistentVolumeClaim."

draghuram

comment created time in 2 months

Pull request review commentkubernetes/website

Fixed few issues with Storage concepts section.

 weight: 20  {{% capture overview %}} -This document describes the current state of `PersistentVolumes` in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/) is suggested.+This document describes the current state of *persistent volumes* in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/) is suggested.

It's not a special word. Please remove the formatting. Thank you. :)

draghuram

comment created time in 2 months

pull request commentkubernetes/website

Fix doc about promote AWS-NLB Support from alpha to beta

/approve /lgtm

M00nF1sh

comment created time in 2 months

pull request commentkubernetes/website

Typo in 1.16 Release Blog Post

/assign @kbarnard10

sethmccombs

comment created time in 2 months

more