Azure Developer Community

Hi Friends I am going to publish Kubernetes Components in simple form for better understanding . At Master Node: >Kube-api : It maintain communication into Cluster >Kube-etcd : It contain complete Cluster Information ; It save information into yaml format or we can say contain complete Backup information of Cluster . >Kube-C0ntroller : It give instruction to Worker node (Kubelet) if any request initiated by Master to worker node, Same has been acknowledge by Worker node components (Kubelet) . 4>Kube-Scheduler: It determines best fit worker node or host node to run application pod . Worker Node Components: 1>Docker: Works as Container engine 2>Kubelet : Its work as agent of Master node means which receive instruction from Master node (Controller) and provide acknowledgment to Master (Controller) . 3>Kube-Proxy: Works as Load balancer running on each Worker node (Host Node) . It distribute the traffic across all Container application which is running inside the Host .

111

5 Comments

Any one Looking for Interview preparation On Dot Net Technology #DM me. Real time interview Questions on .Net Core 1. What are the advantages of migrating an application from .NET Framework to .NET Core? 2. Discuss the process of deploying a .NET Core application to a Linux server. 3. Explain the role of dependency injection in ASP.NET Core. 4. Explain the differences between Razor Pages and MVC in ASP.NET Core. 5. How would you handle asynchronous programming in .NET Core? 6. Explain the process of deploying a .NET Core application to Microsoft Azure. 7. Your team is tasked with migrating a large-scale web application from .NET Framework to .NET Core. What factors would you consider during the planning phase of this migration? 8. Your are building a new application using a microservices architecture with .NET Core. How would you design the service boundaries and communication between microservices to ensure scalability, resilience, and maintainability? 9. Your have to deploy a .NET Core application to multiple environments, including Windows, Linux, and Docker containers. How would you ensure that the application behaves consistently across different platforms? 10. Your are following a CI/CD process for delivering changes to production regularly. How would you set up automated build and deployment pipelines for a .NET Core application using tools like Azure DevOps or Jenkins? #.netcore #dotnet #csharp #asp #mvc #wpf #wcf #restapi #api #usa #canada #UK #Interview #hiring #immediate

6

10 Comments

✨ Making Strong Profile - 1 #newskilladded ⚡ CI CD pipeline using Jenkins and Ansible 🖊 What I learned: 1. Continuous Integration and Continuous Delivery (CI/CD) 2. Continuous Integration with Jenkins 3. Jenkins CLI (Command Line Interface) 4. Deployment 5. Jenkins X 6. Jenkins with Docker 7. Jenkins with Ansible 8. Managing and Monitoring Jenkins #devops #agile #skills #plm

24

1 Comment

#Day6/ #365: Learning Ansible Automation(WSL, Ubuntu) , Network Security ,DSA, and Gita Reflections Today, I focused on WSL (Windows Subsystem for linux), Ubuntu Commands, Few playbooks of Ansible. Note - If we want to run ansible playbooks in Windows its only possible in linux and mac OS devices so one solution is Create an environment of Linux in your local computer using WSL and then use ubuntu to run you ansible playbook with Inventory. Steps Important for interview if anyone preparing - 💡 Install WSL and Ubuntu (as outlined in previous lines). Install Ansible within your WSL Ubuntu. Create an inventory file and playbooks in the WSL environment. Run your playbooks directly from the WSL terminal. I’ve put together some important commands and my handwritten notes on GitHub—check them out here: https://lnkd.in/d6R-puGw. Ansible, which is a great tool for IT automation. It helps you manage repetitive tasks. For example, if you need to configure an application on over 200,000 devices without involving employees (for security reasons), Ansible can really simplify that process. It’s maintained by Red Hat and built with Python. Network Security - Routing(How the traffic travels, Switching) etc. ✍ In my DSA practice, I tackled the problem: ☺️ 567. Permutation in String. Gita 🙂 Today, I also read more from the Bhagavad Gita. When Arjuna hesitates to fight his family, Krishna tells him that those who are on the side of Adharma are as good as dead already. He encourages Arjuna to do what’s right, reminding him that he’s not alone in this fight. This journey is getting more interesting every day—can’t wait to see where it goes! #Ansible #networksecurity #Leetcode #WSL #Ubuntu #Automation #DSA #BhagavadGita #Day6 #Consistency #Coder #pepsicoproud

35

"Keycloak" is an open-source identity and access management solution for modern applications and services. It provides features such as single sign-on (SSO), identity brokering, user federation, and social login. Steps to Deploy Keycloak on Azure AKS:- 1. Set Up Azure Kubernetes Service (AKS) Login to Azure Create a Resource Group Create an AKS Cluster Get AKS Cluster Credentials 2. Deploy Keycloak on Kubernetes Create a Persistent Volume (PV) and Persistent Volume Claim (PVC) Create a YAML file for PV and PVC Apply the PV and PVC Deploy Keycloak with a StatefulSet Create a YAML file for StatefulSet Apply the StatefulSet Expose Keycloak with a Service Create a YAML file for Service Apply the Service 3. Access Keycloak Get the External IP Access Keycloak using the External IP Troubleshooting Keycloak Deployment Check Pod Status and Logs Check Events Verify Persistent Volume and Claims Verify Service and External IP. As for the manifest files and commands,,, I m too lazy... but I hope that you know why keycloak is deployed as a statefulset, and why you need PV and PVC, right?! If no, find out..... Like why monitoring components are deployed as daemonsets....!!!

4

Hi Folks, Here is today's Byte 💡: Azure Kubernetes Service (AKS) - Integration with Azure Firewall 📥 : 🔹Provides advanced threat protection and secure network boundaries. 🔹 Users can create and enforce custom firewall rules tailored to their specific security requirements. 🔹Integration with Azure Monitor allows for detailed logging and monitoring of network traffic. 🔹The solution scales with the needs of the AKS cluster, ensuring consistent security across various deployment sizes. Area of Implementation 👨‍💻 : ➡ A retail company running a large-scale e-commerce platform on AKS can utilize Azure Firewall integration to secure their application and customer data. ➡ By implementing custom firewall rules and leveraging Azure Monitor, they can protect against cyber threats and ensure compliance with security standards. Hope you find this Byte useful, do share your suggestions for any specific topic/concept 👍 Stay tuned for the next Byte... 🤓 #AzureBytes #azure #azurecloud #microsoft #microsoftazure #microsoftbuild #microsoftinspire #microsoftlearn #aks #kubernetes #firewall #security #network #containermanagement #loadbalancing Azure Developer Community OpsTree Solutions

12

Learn Kubernetes Administration at Maharashtra Institute of Technology Aurangabad, MIT CIDCO Auranagabad NetworkPolicy is a resource (like Pod). It's designed with YAML manifest file. You can refer the template from Kuberenetes documentation. Three things are important: a) Which Pod you want to apply policy. b) Type of traffic you want to restrict : Ingress or Egress c) Which Port and Protocol You can choose destination using: PodSelector, NamespaceSelector, and IP address(CIDR) block. Here, labels are important. The labels can be for Pod or for namespace. Through label, you can choose the desired object from the k8s cluster. To know labels of Pod and namespace: kubectl get po --show-labels kubectl get ns --show-labels After knowing the labels, those can be written into Network Policy YAML manifest file.

33

Database Startup Sequence  ******************************* # Nomount Stage : ---------------- 1) The parameter file is read under $ORACLE_HOME/dbs location.                                               2) Allocate SGA as per the parameter file, and start Oracle background processes, which means starting the instance. (INSTANCE=SGA+Bcakground process)       3) open the alert log & trace log file to write all startup details.                                            4) only the instance is started, no DB is associated with an instance.                                             5) You can an issue Create a database statement You can create a P-file from a Sp-file & vice-versa.                                   # Mount Stage : ---------------- 1) For mounting the database oracle looks for the Control file, which contains the metadata of the database means data about data,                the location of the control file is mentioned in the p-file.                                             2) Oracle read control file for Data file & Redolog file location Database won't be available for normal operations only SYS user can access the db.  3) We can perform different operations in the mount stage as enabling archive log mode, creating db, database recovery, and different RMAN operations.                                                                                # Open Stage : ----------------                                                                    1) In this stage oracle opens the Header of Data file & Redolog file and reads the SCN number, and compares it with the Control file SCN number,       if it matches, it opens the database or throws an error.                                         2) Oracle open all data files and all tablespace are online in the open stage, Oracle opens the redo log files, the Default mode is a read-write mode,         if the data file or redo log file is absent, media recovery may be required.                                   3) Any Valid user can connect to the database. #database #DBA

194

10 Comments

🚀 Day4: Conquer Azure Devops Series: Let's begin with creating the infrastructure through Terraform in Azure. Here is the code that creates the basic infra in Azure through Tf. 📌 Features: Linux VM created data block for RG , VNet and Subnet Custom Data for script installation You can explore the code here: https://lnkd.in/giTMdeCc I'll be adding more features to it... stay tuned. One step at a time. 😁 #learninpublic #AzureDevops #terraform #infra #trainwithshubham

8

2 Comments

Are you struggling to find Kubernetes (K8s) resources in Hindi? Look no further! Saiyam Pathak and his Kubesimplify Hindi channel have completed an amazing 12-part K8s Bootcamp series entirely in Hindi. This comprehensive playlist is perfect for anyone interested in learning K8s, from beginners to seasoned professionals. Whether you're new to the concept or want to deepen your K8s knowledge, this boot camp covers it all: Part 12: Dive into GitOps, CI/CD with GitHub Actions, and ArgoCD. Parts 11-10: Learn about project deployment with HTTPS and explore Kubernetes Volumes. Part 9: Demystify Authentication, Authorization, and Admission Control (AAA) in Kubernetes. Parts 8-6: Gain insights into StatefulSets, Services, Ingress, ConfigMaps, Secrets, ReplicaSets, Deployments, and Probes. Parts 5-1: Explore Kubernetes Scheduling, and Pods, understand the difference between Imperative vs Declarative approaches, and learn about YAML and Pod Lifecycle. With over 15 hours of content, this Hindi K8s Bootcamp is a treasure trove of knowledge! Don't miss out! Watch the playlist here: https://lnkd.in/dSRMybFC #Kubernetes #DevOps #CloudNative #TechLearning #Hindi #K8sBootcamp

26

2 Comments

Lest see, If Azure app service Host the Frontend, compare with Azure Blob Storage Hosting for same! 📣 **Azure App Service** can also be used to host your frontend, and it offers additional features compared to Azure Blob Storage. Here's how it can work for hosting a frontend: ### **Azure App Service for Frontend Hosting:** #### 1. **Static Content Hosting**   - **Flexible Hosting**: Azure App Service allows you to host static websites and also dynamic content if needed, making it versatile for various types of applications.   - **Custom Domains and SSL**: Easily configure custom domains and SSL certificates for your frontend.   - **Built-in CI/CD**: Integrates seamlessly with GitHub, Azure DevOps, and other CI/CD tools for automated deployments.   - **Scaling Options**: Automatic scaling options to handle varying traffic loads. #### 2. **Advanced Features**   - **Custom Routing**: App Service allows more complex routing scenarios compared to Blob Storage, which can be useful for single-page applications (SPAs).   - **Authentication**: Built-in support for adding authentication to your frontend if required.   - **API Integration**: If your frontend needs to interact with backend services, Azure App Service can host your APIs and frontend together, simplifying the architecture. ### **When to Use Azure App Service:** - **Dynamic Content**: If your frontend requires server-side logic or dynamic content generation. - **Advanced Features**: If you need features like integrated authentication, custom routing, or API hosting. - **Complex Deployments**: For applications that require more than just static file hosting, including SPAs or applications needing continuous integration and delivery pipelines. ### **How to Set Up:** 1. **Create an App Service**: Create a new App Service in the Azure Portal. 2. **Deploy Your Frontend**: Deploy your static files (HTML, CSS, JavaScript) using FTP, Git, or other deployment methods supported by Azure App Service. 3. **Configure Custom Domain and SSL**: Set up your custom domain and SSL certificates. 4. **Enable CI/CD (Optional)**: Integrate with your CI/CD pipeline for automated deployments. ### **Summary:** - **Azure Blob Storage + CDN**: Ideal for simple, static websites that need global distribution. - **Azure App Service**: Best for more complex scenarios where you might need dynamic content, API integration, or advanced features like authentication and routing. Both services can effectively host your frontend, so the choice depends on your specific requirements.

7

#Challenge - Day 2 🌐 Understanding Cloud Storage Bucket Types and Limitations 🌐 In today's data-driven landscape, choosing the right storage solution is crucial. Let's explore the types and limitations of cloud storage buckets: Types of Cloud Storage Buckets: 🔹 Standard Storage: Ideal for frequently accessed data with low latency requirements. 🔹 Nearline Storage: Cost-effective for data accessed less frequently, with slightly longer access times. 🔹 Coldline Storage: Designed for data accessed infrequently, offering the lowest storage costs. 🔹 Archive Storage: Lowest-cost storage for long-term retention and compliance needs. Key Limitations to Consider: 🔸 Access Times: Storage classes vary in access latency, so choose based on your data retrieval needs. 🔸 Data Retrieval Costs: Costs associated with accessing data vary among storage classes. 🔸 Storage Costs: Each storage class has different pricing structures, influencing budget considerations. 🔸 Lifecycle Management: Policies for moving data between storage classes may impact management complexity. Choosing the Right Bucket: Align your storage strategy with business requirements, balancing performance needs, cost efficiency, and data access patterns. Leverage features like versioning and lifecycle management for optimal control. Ready to optimize your data storage strategy? Let’s connect and explore how cloud storage buckets can elevate your organization's efficiency and scalability! #CloudStorage #DataManagement #TechInsights #DigitalTransformation #BusinessStrategy #CloudComputing

1

Assignement and practice on Azure Load Balancer : 1. Deploy 2 VMs with Ubuntu and Apache2 installed  2. Change index.html to include the following text  a. “This is VM1” on VM1  b. “This is VM2” on VM2  3. Create a load balancer which will balance the traffic between these two VMs Azure Load Balancer is a networking service provided by Microsoft Azure that distributes incoming network traffic across multiple virtual machines (VMs) to ensure high availability and reliability of applications. It operates at the Transport Layer (Layer 4) of the OSI model and can distribute traffic based on various factors such as: 1.Load Balancing Rules: Azure Load Balancer uses load balancing rules to distribute incoming traffic to backend VMs based on criteria like round-robin, source IP affinity, or session affinity. 2.Health Probes: Load Balancer regularly checks the health of VM instances using health probes. If a VM becomes unhealthy, the Load Balancer stops sending traffic to that instance until it becomes healthy again. 3.Frontend IP Configurations: Load Balancer can have one or more frontend IP configurations, including public IP addresses for internet-facing applications or private IP addresses for internal applications. 4.Backend Address Pools: Load Balancer routes incoming traffic to backend address pools, which consist of the IP addresses of the VMs or virtual machine scale sets (VMSS) that receive the traffic. 5.Availability Zones: Load Balancer can be configured to distribute traffic across multiple availability zones to improve fault tolerance and resiliency. 6.Inbound NAT Rules: In addition to load balancing, Load Balancer can also provide inbound network address translation (NAT) to allow VMs in a private subnet to communicate with the internet or other services. Azure Load Balancer is commonly used for applications requiring high availability, scalability, and fault tolerance, such as web servers, microservices, and backend APIs. It plays a crucial role in ensuring that applications hosted on Azure remain accessible and performant even during peak traffic loads or VM failures. Load Balancer Types: 1>Azure Standard Load Balancer: This is a fully featured load balancer suitable for most common scenarios. It operates at Layer 4 (TCP/UDP) of the OSI model and can distribute traffic to backend VMs or instances based on configurable load balancing rules. 2>Azure Basic Load Balancer: Basic Load Balancer provides simple load balancing based on round-robin distribution of traffic across backend VMs. 3>Azure Application Gateway: It's ideal for scaling and securing web applications. 4>Azure Front Door: Front Door is a global HTTP/HTTPS load balancer and application accelerator service that provides intelligent routing and global failover across multiple regions. 5>Azure Traffic Manager: Traffic Manager is a DNS-based traffic routing service that enables global load balancing and high availability across multiple. #azure #load #balancer #round

3

Working with terraform ?? Save The below list of commands to have much more insights on TF !! . terraform init: - Initializes a working directory containing Terraform configuration files. 2. terraform plan: - Generates an execution plan, outlining actions Terraform will take. 3. terraform apply: - Applies the changes described in the Terraform configuration. 4. terraform destroy: - Destroys all resources described in the Terraform configuration. 5. terraform validate: - Checks the syntax and validity of Terraform configuration files. 6. terraform refresh: - Updates the state file against real resources in the provider. 7. terraform output: - Displays the output values from the Terraform state. 8. terraform state list: - Lists resources within the Terraform state. 9. terraform show: - Displays a human -readable output of the current state or a specific resource’s state. 10. terraform import: - Imports existing infrastructure into Terraform state. 11. terraform fmt: - Rewrites Terraform configuration files to a canonical format. 12. terraform graph: - Generates a visual representation of the Terraform dependency graph. 13. terraform providers: - Prints a tree of the providers used in the configuration. 14. terraform workspace list: - Lists available workspaces. 15. terraform workspace select: - Switches to another existing workspace. 16. terraform workspace new: - Creates a new workspace. 17. terraform workspace delete: - Deletes an existing workspace. 18. terraform output: - Retrieves output values from a module. 19. terraform state mv: - Moves an item in the state. 20. terraform state pull: - Pulls the state from a remote backend. 21. terraform state push: - Pushes the state to a remote backend. 22. terraform state rm: - Removes items from the state. 23. terraform taint: - Manually marks a resource for recreation. 24. terraform untaint: - Removes the ‘tainted’ state from a resource. 25. terraform login: - Saves credentials for Terraform Cloud. 26. terraform logout: - Removes credentials for Terraform Cloud. 27. terraform force -unlock: - Releases a locked state. 28. terraform import: - Imports existing infrastructure into your Terraform state. 29. terraform plan -out: - Saves the generated plan to a file. 30. terraform apply -auto -approve: - Automatically applies changes without requiring approval. 31. terraform apply -target=resource: - Applies changes only to a specific resource. 32. terraform destroy -target=resource: - Destroys a specific resource. 33. terraform apply -var=”key=value”: - Sets a variable’s value directly in the command line. 34. terraform apply -var -file=filename.tfvars: - Specifies a file containing variable definitions. 35. terraform apply -var -file=filename.auto.tfvars: - Automatically loads variables from a file Follow Adulla Kiran Reddy for more insights into cloud and devops technology Follow High Teaching for learning cloud technology #Linux #Devops #AWS #CloudComputing

53

Hi Folks, Here is today's Byte 💡: Breaking Changes in Azure API Management Workspaces 💥 : 🔹Workspaces will no longer be supported in the Standard and Developer tiers. They will be exclusively available in the Premium tier. 🔹Assignments of workspace APIs and products to service-level entities, such as products and tags, will no longer be supported. Instead, workspace-level entities must be used. 🔹Certain context objects previously used in workspace policies are deprecated. For example, context.Api.Workspace and context.Product.Workspace will be replaced by context.Workspace. 🔹 Users must update their configurations to comply with these changes, which may involve exporting and modifying Resource Manager templates or migrating to higher service tiers. Area of Implementation 👨‍💻 : ➡ A large enterprise using Azure API Management for their multi-team development environments in the Standard tier will need to migrate to the Premium tier to continue leveraging workspaces. ➡ This ensures that they can maintain isolated environments for development, staging, and production, facilitating better collaboration and governance. Hope you find this Byte useful, do share your suggestions for any specific topic/concept 👍 Stay tuned for the next Byte... 🤓 #AzureBytes #azure #azurecloud #microsoft #microsoftazure #microsoftbuild #microsoftinspire #microsoftlearn #apimanagement #api #gateway #apim Azure Developer Community OpsTree Solutions

12