[Journey] $1.2 Million/year revenue within an 18 month period... Sharing the tech ;) you decide where it fits in your method.

Screenshot 2021-10-10 19:53:29.png
Screenshot 2021-10-10 20:16:04.png
Screenshot 2021-10-10 19:58:11.png

Screenshot 2021-10-10 19:58:41.png

Screenshot 2021-10-10 19:59:42.png

Networking - Wonder Why You Need An Orchestrator?
Screenshot 2021-10-10 20:00:21.png

Screenshot 2021-10-10 20:03:49.png

Help Is On The Way...
Screenshot 2021-10-10 20:05:37.png

AFAIK important point: IPs are shared by the pod, not the container (unless you have only one app per pod)

Screenshot 2021-10-10 20:14:30.png

Screenshot 2021-10-10 20:15:19.png
 
Last edited:
So how do you tell Kubernetes the way you want things to be, your desired state?
You declare this is what I want, in JSON or YAML, pass it to the API server on the master node, in the form of a Manifest.
Screenshot 2021-10-10 20:28:26.png

Screenshot 2021-10-10 20:28:50.png
I want 3 web servers (nginx)
Screenshot 2021-10-10 20:29:44.png

Joila!
Screenshot 2021-10-10 20:31:20.png
 
But like I said, the container Enterprise is an ephemerally designed system. So things are designed to deal with downage and other disasters...
Screenshot 2021-10-10 20:40:44.png
You're running fine and a pod crashes... so you throw another one up (in a different pod)
Screenshot 2021-10-10 20:34:36.png
Screenshot 2021-10-10 20:41:48.png
The system is now back to desired state, with 3x Nginx running smoothly. This is noticed in ms and usually corrected in a sec or two.


This is the bane and also the beauty of this system. The bane because you have to plan for disaster and not just avoiding it, and beautiful because once you do, you are resilient and scalable (both forward and back).

You don't SFTP in and drop a tarball anymore to install and you don't have to fix the pod, just let it die and open another (being said it is not because of a common pod issue).

Like the post before, cattle not pets.

Its all package/dependency management and auto redundancy, which was what the Internet was designed for.
 
Last edited:
A Closer Look At The Kubernetes API
Kubernetes API Objects​
Screenshot 2021-10-10 20:50:58.png

The atomic unit the scheduler talks to in Kubernetes is the pod. For a VM it is usually the OS, and Docker does not wrap containers into pods, so the container is the atomic unit...
Screenshot 2021-10-10 20:55:35.png
Screenshot 2021-10-10 21:09:55.png

Screenshot 2021-10-10 20:56:24.png

But dont just jam containers into random pods... logically add related needs together...
Screenshot 2021-10-10 20:57:56.png

Screenshot 2021-10-10 20:59:32.png
Screenshot 2021-10-10 20:59:50.png

Use reason... The shit on the right won't scale.
Screenshot 2021-10-10 21:01:23.png


Here is a good example of makes sense... a web server and log scraper. Notice a hierarchy. You have a main container and a sidecar, or add on feature container. You will come across the term sidecar in help forums and docs often.
Screenshot 2021-10-10 21:02:31.png
 
Last edited:
Each pod has a lifecycle..
Screenshot 2021-10-10 21:11:57.png
Screenshot 2021-10-10 21:15:16.png

Screenshot 2021-10-10 21:12:19.png
Inter-pod communication
Screenshot 2021-10-10 21:13:45.png
Intra-pod communication
Screenshot 2021-10-10 21:14:37.png
 
Just a recap on Leader/Agent basics...
Screenshot 2021-10-10 21:23:35.png

and the basic objects in the Kubernetes API that it interacts.
Screenshot 2021-10-10 21:25:38.png
We've already discussed some about pods...
 
5.controllers.png

7.deployments2.png


3.services.png
 

Attachments

  • 7.deployments2.png
    7.deployments2.png
    427.9 KB · Views: 3
Last edited:
4.services2.png
1.pods-continued.png

That's about it. That's Kubernetes.

I will be building containers and containerServices based on the software (more or less, ad some, replace or remove others) I have listed in my mind map... and using Kubernetes to manage them.
Base Build Images.png

I think everyone knows what Kubernetes is now... so I'll stop with the picvomit...

The main Apps I want to get up and running in the back of the house to handle email and ingest data is ManifoldCF,
(What is ManifoldCF) [short answer, a multi-format autodownloader on steriods]
and iRedMail.

The main front of the house app I feel is imperative is the Drupal framework.
(What is Drupal)

In turn, which needs a database Yugabytedb (will have to modify some things),

The PHP programming language

and a web server (Nginx) (instead of Apache httpd).

Pretty much everything else is in between (other than network wraps etc. that supersede ) the apps above. From data shipments coming into the sausage factory to content going out...

Gitlab CE is the first sausage factory app to focus on... It is central to everything sausage. It offers support for the whole development & operations environment (DevOps)
sausage-factory.png
 
Last edited:
Well I'm going to go watch a movie with the fam
then retire..
g'nite BHW
 
whats your niche, tim?
That's 5... saved the thread from death... still need 5 more people to ask the niche before I reveal however.
Here's another clue... the guy in the film entered the same field at one point...
 
Last edited:
Boring as hell, but even if you think you know the docs by heart... add all software and important doc etc.. links. Seems like a waste of time for many...

But simply adding connections (like how to use OpenPolicyAgent together with Kafka) visually like below, can make even the messiest sausage into a coherent plan of action, complete with instructions to follow...

And if you think you're a super smarty pants... Put your big boy pants back on... This is for your team, your bots, your flows etc... Get over yourself and document your documentation...
boring-doc-sort-connect.png

Screenshot 2021-10-11 13:44:30.png
 
Last edited:
What seems tedious is sometimes actually a time saver...
Screenshot 2021-10-11 14:04:32.png
Screenshot 2021-10-11 14:17:19.png

;) grab it in one cut from the docs site and paste the index right in...
 
Last edited:
i still dont understand anything of this after reading all again :) can you explain this in easy English?
I am building an IM system built on containers managed by Kubernetes. It's virtual hardware base is a cluster of four Virtual Private Servers, one that acts as a Kubernetes manager, and the other three run software (containers)...

Right now I am making documentation handy by putting the links to info into a mindmap. Sometimes I put ideas into LibreOffice Draw to share... and to also link in the mindmap when appropriate ;)

After I put all of the docs in, then I will go back (using the docs right there if needed) to add a list of input filetypes and output filetypes that are native out of the box for each app, giving me a Native ETL imports/exports map...

I will then use the filetype info to make ETL connector and workflow design moving forward much easier and semi-normalized.

If you want to know what the tech does, Google is your friend... If you want to know what my niche is... you have to ask. There are a few hints above... they are meant to be mildly cryptic.
 
Nikispot said:
i still dont understand anything of this after reading all again :) can you explain this in easy English?

The end goal is a Drupal CMS project,
AI/ML personalized/GEO specific content,
An integrated CRM and ERP,
A heavily integrated permissions/sec/policy/logging system,
and real-time financial reporting required by a few major compliance agencies in my niche..

I am designing this like a Larg"ish" Enterprise, but most of the employee tasks are bots.

I hope that helps.
 
Back
Top