This is a Bug Report
Problem:
Under https://kubernetes.io/docs the order of elements in most sample yaml files are like
apiVersion: <version>
kind: <resource>
metadata:
name: <resource name>
spec:
...
but the orders of some sample files are different like:
kind: <resource>
apiVersion: <version>
metadata:
name: <resource name>
spec:
...
or
apiVersion: <version>
metadata:
name: <resource name>
spec:
...
kind: <resource>
and that lets readers a little confused.
Proposed Solution:
Nice to make these orders consistent in whole doc.
Page to Update:
https://kubernetes.io/docs/concepts/configuration/secret/#creating-a-secret-manually is one of examples. (See the sample of keyword YXBpVXJsOiAiaHR0cHM6Ly9teS)
The list of files we need to check under k8s.io/website/content/en/docs
working on this issue..would be a good start.
/kind bug
@Vageesha17 i see your PR #13875 was merged. Were you planning to create more PRs as part of this issue ?
I am checking whole files which contain yaml format.
@oomichi thanks for working on tidy up all this.
QQ - are you working on a particular order or you pick random pages ? -ie - you planning to finish concepts first before moving to tasks ?
/language en
@DanyC97
QQ - are you working on a particular order or you pick random pages ? -ie - you planning to finish concepts first before moving to tasks
I am working on the order from top to bottom on this Issue message at the above.
That means yes, I am concentrating on concepts pages now, then setup, tasks would be next action items.
If I can find another volunteers, they will work for setup or tasks before I finish concepts.
I've already pushed all PRs for concepts today :-)
I can work to following item.
tasks/administer-cluster/*
I checked some files. these files are no problem.
Sorry. I did not tell you exactly. The following files are no problem.
authentication.md is also good.
I've already pushed all PRs for
conceptstoday :-)
yeah, i keep an eye on it ;)
@DanyC97
yeah, i keep an eye on it ;)
Thank you so much :-)
@s-ito-ts
I can work to following item.
tasks/administer-cluster/*
Thanks :-)
I did put your name on the above list.
@k-toyoda-pi
I checked some files. these files are no problem.
Thanks for checking these files.
Your list you mentioned doesn't contain the following file under setup
Does it mean these files contain this issue and you will fix them, right ? :-)
Cool, we have done under reference today.
@oomichi
Does it mean these files contain this issue and you will fix them, right ? :-)
OK. I will fix "setup/multiple-zones.md".
But "setup/release/notes.md" may have no problem as scope of this issue, because a part like yaml is bullet points actually. I think that converting to bullet point is strange.
https://kubernetes.io/docs/setup/release/notes/#other-notable-changes-2
I can work to
@s-ito-ts Your latest PR fixes tasks/administer-cluster/reconfigure-kubelet.md only under tasks/administer-cluster/. Don't the other files under tasks/administer-cluster/ contain this problem?
I'd like to update the status for each file based on your input.
My working items in this issue has been done :-)
@oomichi
Your latest PR fixes tasks/administer-cluster/reconfigure-kubelet.md only under tasks/administer-cluster/. Don't the other files under tasks/administer-cluster/ contain this problem?
I'd like to update the status for each file based on your input.
I had finished fixes of this problem under tasks/administer-cluster/.
Some yaml were created from files under the examples/admin/.
So, I fixed the files under examples/admin/ instead of the files under tasks/administer-cluster/.
@s-ito-ts
I had finished fixes of this problem under tasks/administer-cluster/.
Some yaml were created from files under the examples/admin/.
Thanks for your confirmation. I have marked these items as done on the above list.
@k-toyoda-pi
The last piece is tasks/access-application-cluster/ which you are assigned.
Is it possible to make it?
re: concepts/overview/object-management-kubectl/kustomization.md (TODO: need to check kubectl kustomize ./ output)
I tried to run kustomize and the output like
$ kubectl kustomize ./
apiVersion: v1
data:
application.properties: |
FOO=Bar
kind: ConfigMap
metadata:
name: example-configmap-1-8mbdf7882g
$
That is the same as current doc, so I keep current doc for avoiding readers' confusion.
https://github.com/kubernetes/website/pull/14246 fixed the remaining things.
So we have finished this issue, thank you everyone so much :-)
great collaboration and self-organization @oomichi @s-ito-ts @k-toyoda-pi
馃啋 馃挴
@DanyC97 Thank you so much :-)
Most helpful comment
great collaboration and self-organization @oomichi @s-ito-ts @k-toyoda-pi
馃啋 馃挴