Loading video...

Video Failed to Load

Go Home

🔥 Preparing for DevOps interviews? Presenting DevOps Terminal 📚 150+ DevOps Questions for: • Docker/K8s • CI/CD • Cloud • IaC • Monitoring • Security + much more! Level up your DevOps interview game! 🚀 #DevOps #Jobs #Careers #DevOpsCommunity

11 Comments

Bhavishya Aggarwal's profile picture
Bhavishya Aggarwal1 year ago

One feature request that I would like to see is the Blog section in which viewers will be able to access the latest blog posts and announcements in the DevOps area, Just as like the Tldr website

Rohit Ghumare | That #DevOps Guy✍️'s profile picture
Rohit Ghumare | That #DevOps Guy✍️1 year ago

Feel free to create issues or submit PR: Community website: Interview: Community:

SecurityPal's profile picture
SecurityPal2 years ago

In this episode of the 'In Security' Podcast, coming to you from the Himalayas, @WilHarm3, Operating Partner and CISO at @craft_ventures, and Josh Mullis, Head of Information Security at @productiv_inc, share thoughts on the evolving role of a CISO. 🔗:

Achhaya Pathak's profile picture
Achhaya Pathak1 year ago

great work Rohit

Rohit Ghumare | That #DevOps Guy✍️'s profile picture
Rohit Ghumare | That #DevOps Guy✍️1 year ago

Thank you!!

Suraj Pokharkar's profile picture
Suraj Pokharkar1 year ago

Great work man! 👏🏻

Rohit Ghumare | That #DevOps Guy✍️'s profile picture
Rohit Ghumare | That #DevOps Guy✍️1 year ago

Thanks!!

SIRIUS Yadow's profile picture
SIRIUS Yadow1 year ago

Nice

Rohit Ghumare | That #DevOps Guy✍️'s profile picture
Rohit Ghumare | That #DevOps Guy✍️1 year ago

Thanks

Jay Bhuke's profile picture
Jay Bhuke1 year ago

I love the effort you put into sharing these resources! It’s rare to find such helpful, well-curated content. Thank you for making things easier for all of us!

Rohit Ghumare | That #DevOps Guy✍️'s profile picture
Rohit Ghumare | That #DevOps Guy✍️1 year ago

Thanks

Related Videos

JWT in 60 Seconds 👇 What is JWT ? JWT = JSON Web Token A compact, URL-safe token used for: - Authentication - Authorization - Secure API communication - Identity sharing between services It is digitally signed, so it can be verified and trusted. 🟢 Why JWT exists Typical flow without JWT: User → Application → Database (Session Store) - Server stores sessions - Requires memory/storage - Hard to scale in microservices - More infrastructure complexity - Needs sticky sessions behind Load Balancer - This doesn’t scale well in distributed systems. 🟢 JWT comes into the picture - JWT is stateless authentication. New flow: User → Application → JWT → Client → API - No session stored on server - Token carries user identity & claims - Server only verifies signature - Perfect for scalable systems. 🟢 Complete JWT request flow 1️⃣ User logs in with credentials 2️⃣ Server validates user 3️⃣ Server generates JWT (Header + Payload + Signature) 4️⃣ Client stores JWT (usually in browser/app) 5️⃣ Client sends JWT in Authorization header 6️⃣ Server verifies signature 7️⃣ If valid → Access granted No database lookup for session needed. 🟢 Where JWT is used in real systems? - REST APIs - Microservices authentication - OAuth2 / SSO - API Gateways - Kubernetes dashboards - CI/CD tools - Mobile & SPA applications - Almost every modern cloud-native app uses JWT. 🟢 JWT in DevOps & System Design : As a DevOps engineer, JWT knowledge is used in: - Designing stateless applications - Scaling apps behind Load Balancers - Implementing API security - Working with IAM & OAuth providers - Securing microservices communication - Reducing session storage dependency Stateless auth = Better scalability + Simpler infrastructure Thanks for reading. Happy Learning !

Nandkishor

27,917 views • 7 months ago

HERMES AGENT IS NOW IN THE CLOUD. NO VPS. NO TERMINAL. NO SETUP. PICK A MODEL. PICK A SERVER SIZE. AGENT IS LIVE IN 60 SECONDS. Nous Portal just launched hosted Hermes Agent. two clicks. one minute. done. Nous Research WHAT THIS MEANS: before today: install Hermes on a VPS or your laptop. configure providers. set up gateway. manage updates. run hermes setup. edit config.yaml. great for power users. friction for everyone else. now: go to pick a model. pick a server size. your agent is live and reachable in 60 seconds. no terminal. no SSH. no Docker. same Hermes. same features. same tools. someone else handles the infrastructure. FOR TEAMS: this is where it gets interesting. spin up agents for everyone at your org. each team member gets their own Hermes instance. granular access controls per user. unified billing through Nous Portal. your team gets Hermes on day one. no DevOps needed. no VPS per person. one admin dashboard. one bill. WHAT'S INCLUDED: → 300+ models via Nous Portal (Claude, GPT, Gemini, DeepSeek, Grok, MiniMax, and more) → Tool Gateway (web search, image generation, TTS, browser automation) → all messaging platforms (Telegram, Discord, Slack, WhatsApp, Signal) → full feature set (profiles, cron, kanban, skills, memory, sub-agents, MoA, /goal, /learn, /journey) → automatic updates ONE PORTAL. FOUR TIERS: Free: $0/month. pay-as-you-go credits from $10. Plus: $20/month. $22 in monthly usage credit. Super: $100/month. $110 in monthly credit. Ultra: $200/month. $220 in monthly credit. highest rate limits. every paid tier includes Tool Gateway. one OAuth. one subscription. no extra API keys. SELF-HOSTED IS NOT GOING ANYWHERE: Hermes is MIT licensed. open source. free forever. you can still run it on your laptop, VPS, or GPU cluster. nothing changes for self-hosted users. the cloud version is for people who want the agent running without managing the machine. pick your path: → self-hosted: full control. you manage everything. → cloud: zero ops. Nous manages infrastructure. → hybrid: self-host your main agent, cloud for team members. HOW TO START: cloud: self-hosted: hermes setup --portal both connect to the same Nous Portal. same models. same tools. same billing. learn how to replace your entire team with 8 hermes agents 👇

YanXbt

47,447 views • 3 months ago

HERMES AGENT NOW HAS AUTOMATION TEMPLATES. COPY-PASTE RECIPES FOR CRON JOBS AND WEBHOOKS. ANY MODEL. ANY DELIVERY PLATFORM. three trigger types: SCHEDULE → runs on a cadence (hourly, nightly, weekly) GITHUB EVENT → fires on PR opens, pushes, issues, CI results API CALL → any external service POSTs JSON to your endpoint all three deliver to Telegram, Discord, Slack, SMS, email, GitHub comments, or local files.Nous Research what templates ship right now: DEVELOPMENT: → nightly backlog triage (label + prioritize new issues) → automatic PR code review (posts review on every PR) → docs drift detection (finds code changes without doc updates) → dependency security audit (daily CVE scan, CVSS >= 7.0) DEVOPS: → deploy verification (smoke tests after every deploy) → alert triage (correlates alerts with recent changes) → uptime monitor (check endpoints every 30 min, notify only when something is down) RESEARCH: → competitive repo scout (monitor competitor PRs daily) → weekly AI news digest (headlines, papers, repos, industry) → daily arXiv scan (saves summaries to your notes) the webhook system is the part most people miss: hermes webhook subscribe github-pr-review \ --events "pull_request" \ --prompt "Review this PR for security, performance, and code quality." \ --skills "github-code-review" \ --deliver github_comment one command. every future PR gets reviewed automatically. the review posts as a comment directly on the PR. two cost-saving details from the docs: 1. use [SILENT] in prompts. "if nothing changed, respond with [SILENT]" prevents notification noise on monitoring jobs. 2. use script-only cron jobs for data collection. a Python script handles HTTP requests and file reads. the agent only sees stdout and applies reasoning. cheaper and more reliable than having the agent fetch. every template is copy-paste ready. every template works with any model. docs: full Hermes agent SOUL MD guide in the article 👇

YanXbt

38,263 views • 4 months ago

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.

Himanshu Kumar

229,643 views • 5 months ago

HERMES AGENT HAS FEATURES THAT 90% OF USERS NEVER TOUCH. /BACKGROUND. /STEER. /GOAL. SUB-AGENTS. MODEL SWITCHING. CRON JOBS. 7 LEVELS OF HERMES. ALL EXPLAINED.👇 LEVEL 1 — ONE-SHOT PROMPTS you type a prompt. agent responds. done. this is using Hermes as a chatbot. it works but you leave 90% of the value untouched. LEVEL 2 — MEMORY + SOUL.MD the agent remembers you across sessions. you wrote a SOUL.md with identity, voice, restrictions. Hermes tailors every answer to your context. two people asking the same question get different answers because it knows them differently. LEVEL 3 — COMMANDS THAT MULTIPLY OUTPUT /background → fires a task in the background. your main session stays free. result appears as a panel when done. /steer → injects a message into the current run without interrupting the agent. redirects the work mid-execution. /queue → queues a follow-up for after the current task finishes. /model → switches models mid-session. start with Sonnet for planning. switch to DeepSeek for execution. switch to Opus for review. configure default behavior: display: busy_input_mode: steer # or queue, or interrupt LEVEL 4 — SKILLS + RIGHT MODEL PER SKILL every installed skill becomes a slash command: /competitive-research analyze my top 3 competitors /social-media-copy write 5 LinkedIn posts /code-review check this PR for security issues the unlock: assign a specific model per skill. research skill → GPT-5.5 (cheap, high volume). code review skill → Fable 5 (best at code). content skill → Sonnet (best at writing). you stop paying premium prices for tasks that don't need premium models. LEVEL 5 — MCPs (CONNECT YOUR WORLD) plug Hermes into the tools you already use: Gmail, Calendar, Notion, Slack, ClickUp, Granola. the agent reads your emails, checks your calendar, pulls from your project management tool, and answers questions using YOUR actual data. "what were the numbers this week?" Hermes checks ClickUp, cross-references with your goals in memory, gives a contextualized answer. caveat from the docs: keep MCPs minimal. every MCP adds tools to the context window. 15 MCPs with 10 tools each = 150 tool schemas the model reads every turn. install what you use. disable what you don't. LEVEL 6 — SUB-AGENTS + PARALLEL EXECUTION delegate_task spawns sub-agents with isolated context. batch mode runs children in parallel: delegate_task(tasks=[ {goal: "research best industries for websites", model: "deepseek-v4-flash"}, {goal: "critique the research and find gaps", model: "gpt-5.5"}, ]) max_concurrent_children: 3 (default). each child gets own terminal session and toolset. parent receives summaries when children finish. roles: → leaf (default): cannot re-delegate → orchestrator: can spawn its own workers (bounded by delegation.max_spawn_depth) LEVEL 7 — ASYNC OPERATIONS this is where the agent works without you. /goal — persistent objective across turns. judge model checks after every turn. runs until done or budget hit (default 20 turns). cron jobs — scheduled tasks on repeat. morning briefs, competitor scans, weekly reviews. wakeAgent gates for zero-token monitoring. /background — parallel tasks in current session. results delivered when ready. your main conversation never stops. the shift: from "I ask, it responds" to "it works, I review." WHERE ARE YOU? 1 → chatbot 2 → it knows you 3 → parallel commands 4 → right model per task 5 → connected to your tools 6 → sub-agents working together 7 → runs without you most people are at 2-3. the jump from 4 to 7 is where the real time savings compound. this is just the first 7. beyond this: multi-profile architecture, self-improving knowledge bases, voice mode, kanban orchestration, webhook automation, profile distributions, browser control, IDE integration, and more. comment LEVEL and I'll send you the advanced levels with setup for each. Full guide how to build 3-agent research department with Hermes 👇

YanXbt

31,551 views • 4 months ago