Correct date for assets in 'Kubernetes on MIPS' blog post and update blog URLs (#18663)
Taylor Dolezal
Kubernetes Prow Robot
parent
c3aea9ece8
commit
e4a09aeab3
|
|
@ -19,9 +19,9 @@ For many years, to enrich the ecology of the open-source community, we have been
|
||||||
|
|
||||||
Over the years, we have been actively participating in the Kubernetes community and have rich experience in the using and optimization of Kubernetes technology. Recently, we tried to adapt the MIPS architecture platform for Kubernetes and achieved a new a stage on that journey. The team has completed migration and adaptation of Kubernetes and related components, built not only a stable and highly available MIPS cluster but also completed the conformance test for Kubernetes v1.16.2.
|
Over the years, we have been actively participating in the Kubernetes community and have rich experience in the using and optimization of Kubernetes technology. Recently, we tried to adapt the MIPS architecture platform for Kubernetes and achieved a new a stage on that journey. The team has completed migration and adaptation of Kubernetes and related components, built not only a stable and highly available MIPS cluster but also completed the conformance test for Kubernetes v1.16.2.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
*Figure 1 Kubernetes on MIPS*
|
_Figure 1 Kubernetes on MIPS_
|
||||||
|
|
||||||
## K8S-MIPS component build
|
## K8S-MIPS component build
|
||||||
|
|
||||||
|
|
@ -45,7 +45,7 @@ To build K8S-MIPS components, we used cross-compilation technology. Our process
|
||||||
After successfully building the above components, we use tools such as kubespray and kubeadm to complete kubernetes cluster construction.
|
After successfully building the above components, we use tools such as kubespray and kubeadm to complete kubernetes cluster construction.
|
||||||
|
|
||||||
| Name | Version | MIPS Repository |
|
| Name | Version | MIPS Repository |
|
||||||
|------------------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| ------------------------------ | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||||
| golang on MIPS | 1.12.5 | - |
|
| golang on MIPS | 1.12.5 | - |
|
||||||
| docker-ce on MIPS | 18.09.8 | - |
|
| docker-ce on MIPS | 18.09.8 | - |
|
||||||
| metrics-server for CKE on MIPS | 0.3.2 | `registry.inspurcloud.cn/library/cke/kubernetes/metrics-server-mips64el:v0.3.2` |
|
| metrics-server for CKE on MIPS | 0.3.2 | `registry.inspurcloud.cn/library/cke/kubernetes/metrics-server-mips64el:v0.3.2` |
|
||||||
|
|
@ -57,17 +57,17 @@ After successfully building the above components, we use tools such as kubespray
|
||||||
|
|
||||||
**Note**: CKE is a Kubernetes-based cloud container engine launched by Inspur
|
**Note**: CKE is a Kubernetes-based cloud container engine launched by Inspur
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
*Figure 2 K8S-MIPS Cluster Components*
|
_Figure 2 K8S-MIPS Cluster Components_
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
*Figure 3 CPU Architecture*
|
_Figure 3 CPU Architecture_
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
*Figure 4 Cluster Node Information*
|
_Figure 4 Cluster Node Information_
|
||||||
|
|
||||||
## Run K8S Conformance Test
|
## Run K8S Conformance Test
|
||||||
|
|
||||||
|
|
@ -124,9 +124,9 @@ Here are some of the images we built：
|
||||||
|
|
||||||
Finally, we ran the tests and got the test result, include `e2e.log`, which showed that all test cases passed. Additionally, we submitted our test result to [k8s-conformance](https://github.com/cncf/k8s-conformance) as a [pull request](https://github.com/cncf/k8s-conformance/pull/779).
|
Finally, we ran the tests and got the test result, include `e2e.log`, which showed that all test cases passed. Additionally, we submitted our test result to [k8s-conformance](https://github.com/cncf/k8s-conformance) as a [pull request](https://github.com/cncf/k8s-conformance/pull/779).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
*Figure 5 Pull request for conformance test results*
|
_Figure 5 Pull request for conformance test results_
|
||||||
|
|
||||||
## What's next
|
## What's next
|
||||||
|
|
||||||
|
|
@ -136,8 +136,8 @@ In the future, we plan to actively contribute our experience and achievements to
|
||||||
|
|
||||||
Contribution plan：
|
Contribution plan：
|
||||||
|
|
||||||
* contribute the source of e2e test images for MIPS
|
- contribute the source of e2e test images for MIPS
|
||||||
* contribute the source of hyperkube for MIPS
|
- contribute the source of hyperkube for MIPS
|
||||||
* contribute the source of deploy tools like kubeadm for MIPS
|
- contribute the source of deploy tools like kubeadm for MIPS
|
||||||
|
|
||||||
----
|
---
|
||||||
|
|
|
||||||
|
Before Width: | Height: | Size: 212 KiB After Width: | Height: | Size: 212 KiB |
|
Before Width: | Height: | Size: 38 KiB After Width: | Height: | Size: 38 KiB |
|
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 44 KiB |
|
Before Width: | Height: | Size: 9.9 KiB After Width: | Height: | Size: 9.9 KiB |
|
Before Width: | Height: | Size: 216 KiB After Width: | Height: | Size: 216 KiB |
Loading…
Reference in New Issue