Please help us with your valuable feedback - forms.gle/E9r3xvTxnLPKz9Hw9
@awssoorinje747
Жыл бұрын
Your teaching style is exceptional, and the visuals you use greatly assist in comprehending the concepts. They make learning much more accessible. It would be greatly beneficial if you could add a separate video on user and service authentication, specifically addressing Role-Based Access Control (RBAC). If possible, please include a theoretical explanation in one video and a practical demonstration in another. This separation would make it easier for us to grasp each aspect thoroughly.
@gurunathpendyala5944
Жыл бұрын
Excellent visual presentation and depth of the knowledge on concept is the main attraction of ur videos.😊
@nareshv7797
Жыл бұрын
Exactly what everyone wants in a simple manner and this makes it very easy
@sahilkeshri5414
Жыл бұрын
Thank you Riya , one of the best explanations.
@DevOps-e2k
Жыл бұрын
Thanks ma'am for your quality videos
@NileshKharat-sp5kx
Жыл бұрын
Nice Explanation Riya, Thanks!
@kkishore025
8 ай бұрын
excellent video . much appreciations
@jalandharbehera99
8 ай бұрын
Wow…really no words for you mam🙏🙏🙏
@abrarsyed7177
Жыл бұрын
Mam iska hi wait tha 😍 please practical le lo is per
@nikhilkhariya8247
6 ай бұрын
Excellent job 💯
@samikshasharma3544
Жыл бұрын
Appreciate your work ❤
@chanchalsoni2374
Жыл бұрын
Nice explaination❤
@girishfury2630
Жыл бұрын
hi .. it was a nice video.. but i am still confused with the logic of how to make mysql-0 as a primary write and how other pods will be synced and will work as read database.... any other sample i can view online or anywhere else to clear my doubt ?
@DevOpsPro
Жыл бұрын
In the context of MySQL (or similar databases), the logic for achieving primary-write and read replicas can be implemented using specific database configurations rather than directly within Kubernetes resources like StatefulSets. Kubernetes StatefulSets provide stable network identities for each pod, but the primary-write and read replica logic usually involves database-specific settings. For MySQL, you can achieve this using a Master-Slave (Primary-Replica) configuration. In such cases, you'll need to set up MySQL in a master-slave configuration, where "mysql-0" will be the master (primary write) and the other pods will be the replicas (read databases).
@nikhilkhariya8247
6 ай бұрын
@@DevOpsPro Can u make a video on this and explain
@pravinsingh8782
Жыл бұрын
Can you explain what will happen if primary pods went down suddenly due node issue ?
@rohita9689
Жыл бұрын
mam please ek video banado kubeadm say aws ec2 instances par cluster setup krna. Please step by step guide bnado I mean kha kha say cheeza search kara and eksa setup kara sabkuch. Master and worker nodes kesa bnaya etc
@DevOpsPro
Жыл бұрын
Check this - kzitem.info/news/bejne/l5Wfl5yOkaiae6w
@gungungumber6450
2 ай бұрын
I have deployed postgres using stateful and using dynamic provisioning i mean i used volume chain templates for postgresql but whatever im creating on postgre-0 . Its not reflecting inside the shell of postgres-1 or 2. how to make them synchronize with each other? or do we need a single pvc for all to make them synchronize?
@DevOpsPro
Ай бұрын
In a StatefulSet, each pod gets its own Persistent Volume Claim (PVC) because they are designed to be independent and maintain their own data. To synchronize data across your PostgreSQL instances (like postgres-0, postgres-1, etc.), you need to set up PostgreSQL replication. Each pod should have its own PVC, but you can configure one pod as the primary (leader) and the others as replicas (followers) using PostgreSQL's built-in replication feature. This setup allows changes on the primary pod to be replicated to the others. A single PVC for all pods is not appropriate because each pod needs its own storage to avoid data conflicts and ensure proper replication.
@olympusbiz9583
7 ай бұрын
We want Liveness and readiness prode video
@DevOpsPro
6 ай бұрын
Noted, will create
@maheshkumarnaik754
10 ай бұрын
scalein and scale out by auto is not possible in stateful set
@ramyapogakula7987
Жыл бұрын
presentation is good. but if you explain in English it might help lots of people who doesn't know Hindi
@DevOpsPro
Жыл бұрын
Very soon we will create content in english too
@rohanrustagi7857
Жыл бұрын
for volumeclaim template to work them as storage class we also have to install ebs driver or not??
@DevOpsPro
Жыл бұрын
No, you don't need to install an EBS driver specifically for using the volumeClaimTemplate in StatefulSets. Kubernetes handles the provisioning of PersistentVolumes (PVs) and PersistentVolumeClaims (PVCs) based on the storage class you specify. If you want to use EBS volumes, you would need to ensure that you have a storage class configured to provision EBS volumes in your Kubernetes cluster. However, the specific installation of an EBS driver is not required for volumeClaimTemplate functionality within StatefulSets.
@rohanrustagi7857
Жыл бұрын
@@DevOpsProso ma'am the yaml u provided we can directly apply on cluster right?
Пікірлер: 29