-
Notifications
You must be signed in to change notification settings - Fork 15.3k
Description
This is a...
- Feature Request
- Bug Report
Problem:
There is inconsistency in the docs around the examples K8s manifest yaml files.
Proposed Solution:
In order to divide and conquer this issue will be used as a master tracking list for the TASK topic only.
Configure pods and containers
- https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
- https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/
Administer a Cluster
- https://kubernetes.io/docs/tasks/administer-cluster/dns-horizontal-autoscaling/
- https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
- https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/ - split the kubectl get from create
- https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy/
- https://kubernetes.io/docs/tasks/administer-cluster/ip-masq-agent/ => move "more docs sentence under agent guide"
- https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/
- https://kubernetes.io/docs/tasks/administer-cluster/limit-storage-consumption/
- https://kubernetes.io/docs/tasks/administer-cluster/namespaces-walkthrough/ => move to yaml instead of json
- https://kubernetes.io/docs/tasks/administer-cluster/namespaces/ => move yo yaml vs json
- https://kubernetes.io/docs/tasks/administer-cluster/static-pod/ => wget the spec file rather than EOF
- https://kubernetes.io/docs/tasks/administer-cluster/storage-object-in-use-protection/
Inject Data Into Application
- https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/
- https://kubernetes.io/docs/tasks/inject-data-application/podpreset/
Run Applications
- https://kubernetes.io/docs/tasks/run-application/run-replicated-stateful-application/ => move the kubectl after the spec
change
In addition, the controller assigns each Pod a unique, stable name of the form -. In this case, that results in Pods named mysql-0, mysql-1, and mysql-2.
to
In addition, the controller assigns each Pod a unique, stable name of the form - which results in Pods named mysql-0, mysql-1, and mysql-2.
- https://kubernetes.io/docs/tasks/run-application/rolling-update-replication-controller/
- https://kubernetes.io/docs/tasks/run-application/configure-pdb/
Run Jobs
- https://kubernetes.io/docs/tasks/job/automated-tasks-with-cron-jobs/
- https://kubernetes.io/docs/tasks/job/parallel-processing-expansion/
- https://kubernetes.io/docs/tasks/job/coarse-parallel-processing-work-queue/
- https://kubernetes.io/docs/tasks/job/fine-parallel-processing-work-queue/
remove the section about
If you are working from the website source tree, you can go to the following directory and start a temporary Pod running Redis and a service so we can find it.
End user doesn't work from git repo
Access Applications in a Cluster
-
https://kubernetes.io/docs/tasks/access-application-cluster/connecting-frontend-backend/ => add full url to nginx.conf same like Issue with k8s.io/docs/tasks/access-application-cluster/connecting-frontend-backend/ #12554 - https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/ => change it to yaml definition
- https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/
- https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/#yaml => fix this page, there are few things in
Monitor, Log, and debug => fix the title, remove the comma before and -> done
- https://kubernetes.io/docs/tasks/debug-application-cluster/audit/
- https://kubernetes.io/docs/tasks/debug-application-cluster/debug-pod-replication-controller/
change
kubectl get nodes -o yaml | grep '\sname|cpu|memory'
to
kubectl get nodes -o yaml | egrep '\sname:|cpu:|memory:'
- https://kubernetes.io/docs/tasks/debug-application-cluster/debug-service/ => add note header. Fix the convention by removing
Ifand turn it into a bullet box
also turn each q on its own line
Is the port you are trying to access in spec.ports[]? Is the targetPort correct for your Pods (many Pods choose to use a different port than the Service)? If you meant it to be a numeric port, is it a number (9376) or a string “9376”? If you meant it to be a named port, do your Pods expose a port with the same name? Is the port’s protocol the same as the Pod’s?
- https://kubernetes.io/docs/tasks/debug-application-cluster/crictl/ => can we move to yaml spec rather than json ?
- https://kubernetes.io/docs/tasks/debug-application-cluster/debug-cluster/ => add the log file path inside `` to improve visibility
Extend K8
- https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/ => add urls/ move files into examples dir etc
- https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definition-versioning/
TLS
- https://kubernetes.io/docs/tasks/tls/managing-tls-in-a-cluster/ -> moves files into examples dir