openshift-docs
rook
openshift-docs | rook | |
---|---|---|
10 | 51 | |
727 | 11,949 | |
0.3% | 0.6% | |
10.0 | 9.9 | |
4 days ago | 2 days ago | |
HTML | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
openshift-docs
- Any good tutorials?
-
[TechStory]: Migrating services and databases from an OpenShift (or K8s) cluster to another
My first experience with OpenShift was with a task which was kind of a heavy task, I didn't know anything about OpenShift or K8s! but I was in charge of migrating resources from a cluster to one another! (twice!)
-
DevOps Tooling Landscape
OpenShift is a container platform from Red Hat that's built on top of Kubernetes. It offers additional features like built-in CI/CD pipelines, enhanced security, and support for multiple programming languages and frameworks.
-
Collecting Security Logs
Openshift documentation can be hard to find, and installing an cluster without it can be hard. 🤗
- How to keep OpenShift clusters running?
-
OCP Logging
For whatever reason, the PRs for adding CloudWatch and Loki/Vector to the docs haven't merged yet.
-
My director is mad that I accepted another internal position for a 26% raise when he was told he could only give me a 10%
At your own pace, jump into orchestration using a Kubernetes distribution out there; but really, only do that fairly late in the game (e.g. OpenShift). Sadly, it's quite a jump from containers to orchestration, and there is no "smooth" in-between. Maybe as a prelude, you can look into etcd configuration clusters and Ceph storage clusters first, e.g. using a bunch of VMs on your machine, or a few Raspberry Pis. There are plenty of occasions to pinch your fingers with those, and thus valuable lessons to be learned :-)
-
OpenShift in a disconnected environment using vCenter - starting from nothing
Part of my job is to help document and assist with getting environment running offline, including OpenShift. While I don't use vSphere the general process is the same, while individual platforms may require different commands the concepts are all the same. Using docs.openshift.com you can find comprehensive guides in how you setup each platform Openshift supports "disconnected". But do realize that not all organizations agree on the exact definition of what disconnected means so you may need to adjust based on what you need. Some allow "sneaker net", others requires you to use old fashioned DVDs to bring all data onsite etc.
-
Best documentation/discovery process and/or tool for an existing Openshift environment?
You want to be able to rebuild your clusters in case of a disaster, so, any time you install anything, export the yaml. And read https://docs.openshift.com/ for every new version.
-
October 12th updates
- We are adding CNV docs to OKD
rook
-
Ceph: A Journey to 1 TiB/s
I have some experience with Ceph, both for work, and with homelab-y stuff.
First, bear in mind that Ceph is a distributed storage system - so the idea is that you will have multiple nodes.
For learning, you can definitely virtualise it all on a single box - but you'll have a better time with discrete physical machines.
Also, Ceph does prefer physical access to disks (similar to ZFS).
And you do need decent networking connectivity - I think that's the main thing people think of, when they think of high hardware requirements for Ceph. Ideally 10Gbe at the minimum - although more if you want higher performance - there can be a lot of network traffic, particularly with things like backfill. (25Gbps if you can find that gear cheap for homelab - 50Gbps is a technological dead-end. 100Gbps works well).
But honestly, for a homelab, a cheap mini PC or NUC with 10Gbe will work fine, and you should get acceptable performance, and it'll be good for learning.
You can install Ceph directly on bare-metal, or if you want to do the homelab k8s route, you can use Rook (https://rook.io/).
Hope this helps, and good luck! Let me know if you have any other questions.
-
Running stateful workloads on Kubernetes with Rook Ceph
Another option is to leverage a Kubernetes-native distributed storage solution such as Rook Ceph as the storage backend for stateful components running on Kubernetes. This has the benefit of simplifying application configuration while addressing business requirements for data backup and recovery such as the ability to take volume snapshots at a regular interval and perform application-level data recovery in case of a disaster.
-
People who run Nextcloud in Docker: Where do you store your data/files? In a Docker volume, or on a remote server/NAS?
This is beyond your question but might help someone else: I switch from docker-compose to kubernetes for my home lab a while ago. The storage solution I've settled on is Rook. It was a bit of up-front work learning how to get it up but now that it's done my storage is automatically managed by Ceph. I can swap out drives and Ceph basically takes care of everything itself.
-
Rook/Ceph with VM nodes on research cluster?
The stumbling point I am at is I want to use rook.io(Ceph) as my storage solution for the cluster. The Ceph prerequisites are one of the following:
-
Asking for recommendation on remote Kubernetes storage for a small cluster and databases
Have you looked at Rook?
-
Want advice on planned evolution: k3os/Longhorn --> Talos/Ceph, plus Consul and Vault
I've briefly run ceph in an external mode, you can actually use a rook deployment to manage it (sort of). Here is the documentation for doing that. For me it didn't pass my testing phase because I need better networking equipment before I can try that.
-
ATARI is still alive: Atari Partition of Fear
This article explains the data corruption issue happened in Rook in 2021. The root cause lies in an unexpected place and can also occurs in all Ceph environment. It's interesting that Rook had started to encounter this problem recently even though this problem has existed for a long time. It's due to a series of coincidences. I wrote this article because the word "Atari" used in a non-historical context in 2021.
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 2/2
Rook (this is a nice article for Rook NFS)
-
Running on-premise k8s with a small team: possible or potential nightmare?
Storage: Favor any distributed storage you know to start with for Persistent Volumes: Ceph maybe via rook.io, Longhorn if you go rancher etc
-
My completely automated Homelab featuring Kubernetes
I've dealt with a lot of issues that are very close to just unplugging a node. Unfortunately on node lost, my stateful workloads using rook-ceph block storage won't migrate over to another node automatically due to an issue with rook. Stateless apps (ingress nginx, etc..) not using rook-ceph block failover to another node just fine. I've kind of accepted this for now and I know Longhorn has a feature that makes this work but I find rook-ceph to be more stable for my workloads.
What are some alternatives?
vector - A high-performance observability data pipeline.
longhorn - Cloud-Native distributed storage built on and for Kubernetes
hyperconverged-cluster-operator - Operator pattern for managing multi-operator products
ceph-csi - CSI driver for Ceph
okd.io - Source files used to build the https://www.okd.io site.
velero - Backup and migrate Kubernetes applications and their persistent volumes
home-assistant.io - :blue_book: Home Assistant User documentation
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
assisted-installer
Ceph - Ceph is a distributed object, block, and file storage platform
etcd - Distributed reliable key-value store for the most critical data of a distributed system
hub-feedback - Feedback and bug reports for the Docker Hub