K8S Mediaserver Operator

Abstract

1. Introduction

I am so happy to announce the first release of the k8s-mediaserver-operator, a project that mixes up some of the mainstream tools for your media needs.

With this value saved in the top level directory of this repo, running the below will add the resources to your cluster, under the helm release name k8s-mediaserver

I started working on this project because I was tired of using the 'containerized' version with docker/podman-compose, and I wanted to experiment a bit both with helm and operators.

2. Objective

Repository for k8s Mediaserver Operator project

This project demonstrates how Makefile can be applied to a real-world Blockchain & Cloud Computing problem.

4. Technology Stack

5. System Requirements

General requirements for this technology stack — check the README for exact versions.

• See the project README for exact requirements
• Git (to clone the repository)

6. Installation & Setup

git clone https://github.com/kubealex/k8s-mediaserver-operator.git
cd k8s-mediaserver-operator

1. A namespace where you want to put your Custom Resource and all the pods that will spawn
2. Being able to provision an RWX PV where to store configurations, downloads, and all related stuff (suggested > 200GB).
3. First install the CRD and the operator:
4. Install the custom resource with the default values:
5. (Optional) Use custom values:
6. Copy the default values files cp ./helm-charts/k8s-mediaserver/values.yaml my-values.yaml
7. Make all the changes you want in the new file ./helm-charts/k8s-mediaserver/my-values.yaml

kubectl apply -f k8s-mediaserver-operator.yml

kubectl apply -f k8s-mediaserver-operator-arm64.yml

kubectl apply -f k8s-mediaserver.yml

helm install -f my-values.yaml k8s-mediaserver ./helm-charts/k8s-mediaserver/

Full setup instructions are in the project README.

7. Future Enhancements

Suggested extensions you can add to make this your own project.

• Add a CI/CD pipeline with GitHub Actions
• Deploy to a public test network or cloud free tier
• Add monitoring and cost alerts

8. Viva / Review Questions

Common questions examiners ask for projects in this domain.

1. Why does this problem need a blockchain or cloud-native design?
2. Explain the smart contract / infrastructure components and how they interact.
3. How are gas costs or cloud costs kept under control?
4. How is the system secured (keys, IAM, access control)?
5. How would the solution scale to many more users?

9. Source Code & License

This project is developed by kubealex and published on GitHub under the MIT License. Please follow the license terms and credit the original author when you use or modify this code.