github/awesome-kubernetes
1
0
Fork 0
mirror of https://github.com/nubenetes/awesome-kubernetes.git synced 2026-05-14 21:27:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

reorg

Browse Source
This commit is contained in:
Inaki Fernandez
2020-05-19 11:08:35 +02:00
parent 45b5ae4d17
commit 161cebc9f0
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/openshift.md
View File

@@ -245,13 +245,13 @@ Industry momentum has aligned behind Kubernetes as the orchestration platform fo
#### New Technical Components
- **[New Installer](https://cloud.redhat.com/openshift/install):**
- [try.openshift.com/](https://try.openshift.com/)
- [try.openshift.com](https://try.openshift.com/)
- [github.com/openshift/installer](https://github.com/openshift/installer)
- **Storage:** Cloud integrated storage capability used by default via [OCS Operator](https://github.com/openshift/ocs-operator) (Red Hat)
- There are a number of persistent storage options available to you through the OperatorHub / Storage vendors that don’t involve Red Hat, NFS or Gluster.
- Kubernetes-native persistent storage technologies available (non-RedHat solutions):
- [Rook-Ceph](https://operatorhub.io/operator/rook-ceph): [Rook-Ceph storage Operator now on OperatorHub.io](https://www.redhat.com/en/blog/rook-ceph-storage-operator-now-operatorhubio)
- [Robin Storage Operator](https://operatorhub.io/operator/robin-operator): [get.robin.io/](https://get.robin.io/)
- [Robin Storage Operator](https://operatorhub.io/operator/robin-operator): [get.robin.io](https://get.robin.io/)
- **Operators End-To-End!:** responsible for reconciling the system to the desired state
- Cluster configuration kept as API objects that ease its maintenance (“everything-as-code” approach):
- Every component is configured with [Custom Resources (CR)](https://docs.openshift.com/container-platform/4.4/operators/crds/crd-managing-resources-from-crds.html) that are processed by operators.
@@ -292,6 +292,7 @@ Industry momentum has aligned behind Kubernetes as the orchestration platform fo
- The whole process can be done in one command and requires minimal infrastructure knowledge (IPI): ```openshift-install create cluster```
![OCP IPI](images/ocp-ipi.png)
![OCP IPI UPI](images/ocp_ipi_upi.png)
##### IPI & UPI
@@ -299,8 +300,10 @@ Industry momentum has aligned behind Kubernetes as the orchestration platform fo
1. **Installer Provisioned Infrastructure (IPI):** On supported platforms, the installer is capable of provisioning the underlying infrastructure for the cluster. The installer programmatically creates all portions of the networking, machines, and operating systems required to support the cluster. Think of it as best-practice reference architecture implemented in code.  It is recommended that most users make use of this functionality to avoid having to provision their own infrastructure.  The installer will create and destroy the infrastructure components it needs to be successful over the life of the cluster.
2. **User Provisioned Infrastructure (UPI):** For other platforms or in scenarios where installer provisioned infrastructure would be incompatible, the installer can stop short of creating the infrastructure, and allow the platform administrator to provision their own using the cluster assets generated by the install tool. Once the infrastructure has been created, OpenShift 4 is installed, maintaining its ability to support automated operations and over-the-air platform updates.
![OCP IPI2](images/ocp_ipi2.png)|![OCP UPI](images/ocp_upi.png)
:----:|:----:
![OCP IPI2](images/ocp_ipi2.png)
![OCP UPI](images/ocp_upi.png)
#### Cluster Autoscaler Operator
- Adjusts the size of an OpenShift Container Platform cluster to meet its current deployment needs. It uses declarative, Kubernetes-style arguments