Init Containers were specified using custom annotations in k8s 1.5. In
k8s 1.6, these annotations were replaced with the
`Pod.Spec.initContainers` collection and the old annotations were
deprecated in 1.6 and no longer supported in 1.8. There's no reason to
clutter the docs with the old annotation syntax.
* This URL is a better link directly to the feature
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
* Convert links to relative links, clean up a conversion comment
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
* Initial blog post draft for kubeadm v1.15
* More edits, and add pictures
* Incorporate changes from review and add hugo metadata
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
* Update logo and some final edits
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
* Some minor fixes, fix the logo and author attribution
* Fix list formatting
* Fix an other list formatting issue
* Update 2019-06-24-kubeadm-ha-v115.md
Removed ambiguous word 'temporarily', as namespace set using that method, is not temporary. It is permanent for a current resource and there is no concept of a temporary namespace in K8s.
Also, for consisteny '--namespace' flag added after the actual command.
* Updates HAProxy Ingress Controller information to point to new controller supported by haproxytech
* Update content/en/docs/concepts/services-networking/ingress-controllers.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
* Added listing for AWS VPC CNI
Added listing for AWS VPC CNI under "How to implement the Kubernetes networking model".
* Added AWS VPC CNI
* Added AWS VPC CNI to Installing a pod network add-on
* Updated tabs to alphabetical order
* Fix formatting in 2019-06-20-Future-of-CRDs-Structural-Schemas.md
Hugo seems to be incompatible with the Github markdown formatting.
* Fix doc link
* Defaulting is alpha
* Adding what's new section to namespace concepts
To learn more about namespaces and give better navigation this section is added.
* Update namespaces.md
There's been a number of questions around the difference between the external.metrics.k8s.io and custom.metrics.k8s.io in #sig-autoscaling referring back to the HPA docs recently. Added links out to the design proposals for each and the relevant sections of the existing walkthrough docs.
We don't need to be the dispatch for all vulns, now that other projects are starting to have their own processes. But we don't want to discourage reports about stuff that isn't directly in k/k either.
Saying that we usually disclose vuln reports in 7 days is just not true. But, I think it's still good to aim for 7 days when we aren't blocked on and coordinating release of patches.
Jesse Glick