Fix blog links after migration from blog.kubernetes.io to kubernetes.io/blog
This commit is contained in:
Claes Mogren
parent
96cd7b1427
commit
7c88effff5
|
|
@ -1649,7 +1649,7 @@
|
|||
* [WIP: Charter FAQ (the "Why"s)](https://github.com/kubernetes/community/pull/1908)
|
||||
* Reminder: [Contributor Summit](https://github.com/kubernetes/community/tree/master/events/2018/05-contributor-summit), 1 May, day before Kubecon
|
||||
* CNCF would like feedback on the draft blog post for 1.10 beta:
|
||||
* [http://blog.kubernetes.io/2018/03/first-beta-version-of-kubernetes-1-10.html](http://blog.kubernetes.io/2018/03/first-beta-version-of-kubernetes-1-10.html)
|
||||
* [https://kubernetes.io/blog/2018/03/first-beta-version-of-kubernetes-1-10/](https://kubernetes.io/blog/2018/03/first-beta-version-of-kubernetes-1-10/)
|
||||
* Please contact [Natasha Woods](mailto:nwoods@linuxfoundation.org) with your feedback
|
||||
* Shoutouts this week
|
||||
* See someone doing something great for the community? Mention them in #shoutouts on slack.
|
||||
|
|
|
|||
|
|
@ -65,7 +65,7 @@ The project is committed to the following (aspirational) [design ideals](princip
|
|||
approach is key to the system’s self-healing and autonomic capabilities.
|
||||
* _Advance the state of the art_. While Kubernetes intends to support non-cloud-native
|
||||
applications, it also aspires to advance the cloud-native and DevOps state of the art, such as
|
||||
in the [participation of applications in their own management](http://blog.kubernetes.io/2016/09/cloud-native-application-interfaces.html).
|
||||
in the [participation of applications in their own management](https://kubernetes.io/blog/2016/09/cloud-native-application-interfaces/).
|
||||
However, in doing
|
||||
so, we strive not to force applications to lock themselves into Kubernetes APIs, which is, for
|
||||
example, why we prefer configuration over convention in the [downward API](https://kubernetes.io/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/#the-downward-api).
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ What form should this configuration take in Kubernetes? The requirements are as
|
|||
|
||||
* In particular, it should be straightforward (but not required) to manage declarative intent under **version control**, which is [standard industry best practice](http://martinfowler.com/bliki/InfrastructureAsCode.html) and what Google does internally. Version control facilitates reproducibility, reversibility, and an audit trail. Unlike generated build artifacts, configuration is primary human-authored, or at least it is desirable to be human-readable, and it is typically changed with a human in the loop, as opposed to fully automated processes, such as autoscaling. Version control enables the use of familiar tools and processes for change control, review, and conflict resolution.
|
||||
|
||||
* Users need the ability to **customize** off-the-shelf configurations and to instantiate multiple **variants**, without crossing the [line into the ecosystem](https://docs.google.com/presentation/d/1oPZ4rznkBe86O4rPwD2CWgqgMuaSXguIBHIE7Y0TKVc/edit#slide=id.g21b1f16809_5_86) of [configuration domain-specific languages, platform as a service, functions as a service](https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/#what-kubernetes-is-not), and so on, though users should be able to [layer such tools/systems on top](http://blog.kubernetes.io/2017/02/caas-the-foundation-for-next-gen-paas.html) of the mechanism, should they choose to do so.
|
||||
* Users need the ability to **customize** off-the-shelf configurations and to instantiate multiple **variants**, without crossing the [line into the ecosystem](https://docs.google.com/presentation/d/1oPZ4rznkBe86O4rPwD2CWgqgMuaSXguIBHIE7Y0TKVc/edit#slide=id.g21b1f16809_5_86) of [configuration domain-specific languages, platform as a service, functions as a service](https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/#what-kubernetes-is-not), and so on, though users should be able to [layer such tools/systems on top](https://kubernetes.io/blog/2017/02/caas-the-foundation-for-next-gen-paas/) of the mechanism, should they choose to do so.
|
||||
|
||||
* We need to develop clear **conventions**, **examples**, and mechanisms that foster **structure**, to help users understand how to combine Kubernetes’s flexible mechanisms in an effective manner.
|
||||
|
||||
|
|
@ -384,7 +384,7 @@ Consider more automation, such as autoscaling, self-configuration, etc. to reduc
|
|||
|
||||
#### What about providing an intentionally restrictive simplified, tailored developer experience to streamline a specific use case, environment, workflow, etc.?
|
||||
|
||||
This is essentially a [DIY PaaS](http://blog.kubernetes.io/2017/02/caas-the-foundation-for-next-gen-paas.html). Write a configuration generator, either client-side or using CRDs ([example](https://github.com/pearsontechnology/environment-operator/blob/dev/User_Guide.md)). The effort involved to document the format, validate it, test it, etc. is similar to building a new API, but I could imagine someone eventually building a SDK to make that easier.
|
||||
This is essentially a [DIY PaaS](https://kubernetes.io/blog/2017/02/caas-the-foundation-for-next-gen-paas/). Write a configuration generator, either client-side or using CRDs ([example](https://github.com/pearsontechnology/environment-operator/blob/dev/User_Guide.md)). The effort involved to document the format, validate it, test it, etc. is similar to building a new API, but I could imagine someone eventually building a SDK to make that easier.
|
||||
|
||||
#### What about more sophisticated deployment orchestration?
|
||||
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ status:
|
|||
|
||||
API groups may be exposed as a unified API surface while being served by distinct [servers](https://kubernetes.io/docs/tasks/access-kubernetes-api/setup-extension-api-server/) using [**aggregation**](https://kubernetes.io/docs/concepts/api-extension/apiserver-aggregation/), which is particularly useful for APIs with special storage needs. However, Kubernetes also supports [**custom resources**](https://kubernetes.io/docs/concepts/api-extension/custom-resources/) (CRDs), which enables users to define new types that fit the standard API conventions without needing to build and run another server. CRDs can be used to make systems declaratively and dynamically configurable in a Kubernetes-compatible manner, without needing another storage system.
|
||||
|
||||
Each API server supports a custom [discovery API](https://github.com/kubernetes/client-go/blob/master/discovery/discovery_client.go) to enable clients to discover available API groups, versions, and types, and also [OpenAPI](http://blog.kubernetes.io/2016/12/kubernetes-supports-openapi.html), which can be used to extract documentation and validation information about the resource types.
|
||||
Each API server supports a custom [discovery API](https://github.com/kubernetes/client-go/blob/master/discovery/discovery_client.go) to enable clients to discover available API groups, versions, and types, and also [OpenAPI](https://kubernetes.io/blog/2016/12/kubernetes-supports-openapi/), which can be used to extract documentation and validation information about the resource types.
|
||||
|
||||
See the [Kubernetes API conventions](https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md ) for more details.
|
||||
|
||||
|
|
|
|||
|
|
@ -761,7 +761,7 @@ therefore wouldn’t be considered to be part of Kubernetes.
|
|||
applications, but not for specific applications.
|
||||
|
||||
* Platform as a Service: Kubernetes [provides a
|
||||
foundation](http://blog.kubernetes.io/2017/02/caas-the-foundation-for-next-gen-paas.html)
|
||||
foundation](https://kubernetes.io/blog/2017/02/caas-the-foundation-for-next-gen-paas/)
|
||||
for a multitude of focused, opinionated PaaSes, including DIY
|
||||
ones.
|
||||
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ The old, pre-CRI Docker integration was removed in 1.7.
|
|||
|
||||
## Specifications, design documents and proposals
|
||||
|
||||
The Kubernetes 1.5 [blog post on CRI](http://blog.kubernetes.io/2016/12/container-runtime-interface-cri-in-kubernetes.html)
|
||||
The Kubernetes 1.5 [blog post on CRI](https://kubernetes.io/blog/2016/12/container-runtime-interface-cri-in-kubernetes/)
|
||||
serves as a general introduction.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -710,7 +710,7 @@ system to 30,50,100 pods per/node and measures the different characteristics of
|
|||
the system, such as throughput, api-latency, etc.
|
||||
|
||||
For a good overview of how we analyze performance data, please read the
|
||||
following [post](http://blog.kubernetes.io/2015/09/kubernetes-performance-measurements-and.html)
|
||||
following [post](https://kubernetes.io/blog/2015/09/kubernetes-performance-measurements-and/)
|
||||
|
||||
For developers who are interested in doing their own performance analysis, we
|
||||
recommend setting up [prometheus](http://prometheus.io/) for data collection,
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ If you believe you are a Member of Standing, please fill out [this form](https:/
|
|||
## DECISION
|
||||
The newly elected body will be announced in the weekly Kubernetes Community Meeting on October 5, 2017 at 10:00am US Pacific Time. [Please join us](https://groups.google.com/forum/#!forum/kubernetes-community-video-chat).
|
||||
|
||||
Following the meeting, the raw voting results and winners will be published on the [Kubernetes Blog](http://blog.kubernetes.io/).
|
||||
Following the meeting, the raw voting results and winners will be published on the [Kubernetes Blog](https://kubernetes.io/blog/).
|
||||
|
||||
For more information, definitions, and/or detailed election process, see full [steering committee charter](https://github.com/kubernetes/steering/blob/master/charter.md).
|
||||
|
||||
|
|
|
|||
|
|
@ -151,5 +151,5 @@ Name | Organization/Company | GitHub
|
|||
[2017 candidate bios]: https://github.com/kubernetes/community/tree/master/events/elections/2017
|
||||
[election officers]: https://github.com/kubernetes/community/tree/master/events/elections#election-officers
|
||||
[Kubernetes Community Meeting]: https://github.com/kubernetes/community/blob/master/events/community-meeting.md
|
||||
[Kubernetes Blog]: http://blog.kubernetes.io/
|
||||
[Kubernetes Blog]: https://kubernetes.io/blog/
|
||||
[eligible voters]: https://github.com/kubernetes/community/blob/master/events/elections/2018/voters.md
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
- Michelle Noorali gave an introduction and overview of the agenda
|
||||
- Janet Kuo gave an overview of Deployment features
|
||||
- See her [blog post](http://blog.kubernetes.io/2016/04/using-deployment-objects-with.html )
|
||||
- See her [blog post](https://kubernetes.io/blog/2016/04/using-deployment-objects-with/)
|
||||
- See used [minikube](https://github.com/kubernetes/minikube) for the local cluster set up during her demo
|
||||
- Saad Ali gave an overview of Volume features and things to look forward to around Volumes
|
||||
- Check out his [presentation](https://docs.google.com/presentation/d/17w7GqwGE8kO9WPNAO1qC8NyS7dRw_oLBwqKznD9WqUs)
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ _by Shyam JVS, Google Inc_
|
|||
|
||||
## Introduction
|
||||
|
||||
Scalability is a very crucial aspect of kubernetes and has allowed many customers to adopt it with confidence. K8s [started scaling to 5000](http://blog.kubernetes.io/2017/03/scalability-updates-in-kubernetes-1.6.html) nodes beginning from release 1.6. Building and maintaining a performant and scalable system needs conscious efforts from the whole developer community. Lack of solid measures have caused problems (both scalability and release-related) in the past - for e.g during [release-1.7](https://github.com/kubernetes/kubernetes/issues/47344), [release-1.8](https://github.com/kubernetes/kubernetes/issues/53255) and [in general](https://github.com/kubernetes/kubernetes/issues/56062). We need them to ensure that the effort is well-streamlined with proper checks and balances in place. Of course they may evolve over time to suit the community/project’s needs better.
|
||||
Scalability is a very crucial aspect of kubernetes and has allowed many customers to adopt it with confidence. K8s [started scaling to 5000](https://kubernetes.io/blog/2017/03/scalability-updates-in-kubernetes-1.6) nodes beginning from release 1.6. Building and maintaining a performant and scalable system needs conscious efforts from the whole developer community. Lack of solid measures have caused problems (both scalability and release-related) in the past - for e.g during [release-1.7](https://github.com/kubernetes/kubernetes/issues/47344), [release-1.8](https://github.com/kubernetes/kubernetes/issues/53255) and [in general](https://github.com/kubernetes/kubernetes/issues/56062). We need them to ensure that the effort is well-streamlined with proper checks and balances in place. Of course they may evolve over time to suit the community/project’s needs better.
|
||||
|
||||
## Goal
|
||||
|
||||
|
|
|
|||
|
|
@ -8,10 +8,10 @@ We recommend the following presentations, docs, and videos to help get familiar
|
|||
| 2018 May 03 | SIG Storage Intro | [Video](https://www.youtube.com/watch?v=GvrTl2T-Tts&list=PLj6h78yzYM2N8GdbjmhVU65KYm_68qBmo&index=164&t=0s) | An overview of SIG Storage By Saad Ali at Kubecon EU 2018. |
|
||||
| 2018 May 04 | Kubernetes Storage Lingo 101 | [Video](https://www.youtube.com/watch?v=uSxlgK1bCuA&t=0s&index=300&list=PLj6h78yzYM2N8GdbjmhVU65KYm_68qBmo) | An overview of various terms used in Kubernetes storage and what they mean by Saad Ali at Kubecon EU 2018.|
|
||||
| 2017 May 18 | Storage Classes & Dynamic Provisioning in Kubernetes |[Video](https://youtu.be/qktFhjJmFhg)| Intro to the basic Kubernetes storage concepts for users (direct volume reference, PV/PVC, and dynamic provisioning). |
|
||||
| 2017 March 29 | Dynamic Provisioning and Storage Classes in Kubernetes |[Blog post](http://blog.kubernetes.io/2017/03/dynamic-provisioning-and-storage-classes-kubernetes.html)| Overview of Dynamic Provisioning and Storage Classes in Kubernetes at GA. |
|
||||
| 2017 March 29 | Dynamic Provisioning and Storage Classes in Kubernetes |[Blog post](https://kubernetes.io/blog/2017/03/dynamic-provisioning-and-storage-classes-kubernetes/)| Overview of Dynamic Provisioning and Storage Classes in Kubernetes at GA. |
|
||||
| 2017 March 29 | How Kubernetes Storage Works | [Slides](https://docs.google.com/presentation/d/1Yl5JKifcncn0gSZf3e1dWspd8iFaWObLm9LxCaXZJIk/edit?usp=sharing) | Overview for developers on how Kubernetes storage works for KubeCon EU 2017 by Saad Ali
|
||||
| 2017 February 17 | Overview of Dynamic Provisioning for SIG Apps | [Video](https://youtu.be/NXUHmxXytUQ?t=10m33s) | Overview of Storage Classes and Dynamic Provisioning for SIG Apps
|
||||
| 2016 October 7 | Dynamic Provisioning and Storage Classes in Kubernetes |[Blog post](http://blog.kubernetes.io/2016/10/dynamic-provisioning-and-storage-in-kubernetes.html)| Overview of Dynamic Provisioning and Storage Classes in Kubernetes at Beta. |
|
||||
| 2016 October 7 | Dynamic Provisioning and Storage Classes in Kubernetes |[Blog post](https://kubernetes.io/blog/2016/10/dynamic-provisioning-and-storage-in-kubernetes/)| Overview of Dynamic Provisioning and Storage Classes in Kubernetes at Beta. |
|
||||
| 2016 July 26 | Overview of Basic Volume for SIG Apps | [Video](https://youtu.be/DrLGxkFdDNc?t=11m19s) | Overview of Basic Volume for SIG Apps
|
||||
| 2016 March 25 | The State of State | [Video](https://www.youtube.com/watch?v=jsTQ24CLRhI&index=6&list=PLosInM-8doqcBy3BirmLM4S_pmox6qTw3) | The State of State at KubeCon EU 2016 by Matthew Bates
|
||||
| 2016 March 25 | Kubernetes Storage 101 | [Video](https://www.youtube.com/watch?v=ZqTHe6Xj0Ek&list=PLosInM-8doqcBy3BirmLM4S_pmox6qTw3&index=38) | Kubernetes Storage 101 at KubeCon EU 2016 by Erin Boyd
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ Container Storage Interface (CSI) is a standardized mechanism for Container Orch
|
|||
|
||||
For more information about CSI, see:
|
||||
|
||||
* http://blog.kubernetes.io/2018/01/introducing-container-storage-interface.html
|
||||
* https://kubernetes.io/blog/2018/01/introducing-container-storage-interface/
|
||||
* [kubernetes-csi.github.io/docs](http://kubernetes-csi.github.io/docs)
|
||||
|
||||
**What are the limitations of CSI?**
|
||||
|
|
|
|||
Loading…
Reference in New Issue