Skip to main content

Azure Insights: Kibana access; Container Registry; Container Instance

by MSCN Reporter
Staff Writer, MSDynamicsWorld.com

Microsoft Azure pros discuss how to setup Application Gateway for Kibana access, deploying from Container Registry, and tracking Container Instance.

Setting up Application Gateway for Kibana access

Danny McDermott, writing on the Azure Field Notes Blog, looked at how to configure Azure Application Gateway so that a protected instance of Kibana works properly. In a recent project, McDermott was working on a private OpenShift cluster set up on Azure. After the cluster was deployed through Application Gateway, a 500 error popped up when trying to access Kibana. He was able to localize the problem to Application Gateway after successfully connecting through a VNet.

After a bit of investigating, he decided he needed to rewrite the request header. McDermott determined that the X-Forwarded-For header needed changes. With a rewritten rule in place, Kibana opened normally.

Deploying from Container Registry with a CI/CD Pipeline and Terraform

Thomas Thornton explored how to deploy Container Instance using DevOps Pipeline and Terraform. The method also allows users to build a new image and enable CI/CD when pushing to the repository. Thornton explained that the Pipeline has four stages: terraform_base, build and push, and terraform_aci—lastly terraform_destroy destroys the terraform stages.

FREE Membership Required to View Full Content:

Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here

About MSCN Reporter
More about MSCN Reporter