Bitnami by VMware Tanzu logo
  • Applications
  • Products
    • Bitnami Premium

      Add secure software supply chain features and support for all application versions maintained by upstream projects

    • Tanzu Application Catalog

      Used by many of the most security-conscious organizations in the world to curate and customize Open Source software artifacts

    • Support

      If you are a customer and need help, we will get you to the right place

  • Developers
    • Documentation

      Dive into detailed documentation for all aspects of Bitnami

    • Kubernetes Tutorials

      Move Your Containers to Production

    • Kubeacademy

      Unlock your full potential with Kubernetes courses designed by experts

    • VMware Tanzu Education

      Invest in your future and build your cloud native skills

    • Containers
    • Helm Charts
    • Sealed Secrets
    • See all projects
  • Company
    • Resources

    • Blog

    • Careers

    • VMware Newsroom

    • Do you want to talk? Contact Us
Bitnami Documentation > Microsoft Azure > Bitnami Stacks for Microsoft Azure > GitLab Enterprise (CORE) for Microsoft Azure > Administration > Configure virtual network peering

GitLab Enterprise (CORE) for Microsoft Azure

Getting started

  • Obtain application and server credentials
  • Access the administration panel
  • Understand the default port configuration
  • Run rake commands
  • Push changes to GitLab
  • License information

Configuration

  • Configure SMTP for outbound emails
  • Modify the GitLab host name

Administration

  • Start or stop services
  • Use a PEM file to pull or push
  • Update the IP address or hostname
  • Reset the GitLab Enterprise (CORE) administrator password
  • Upgrade GitLab Enterprise (CORE)
  • Create and restore application backups
  • Create an SSL certificate
  • Enable HTTPS support with NGINX
  • Generate and configure a Let's Encrypt certificate
  • Upload files using SFTP
  • Configure virtual network peering
  • gonit
  • Configure and use Gonit

Troubleshooting

  • Debug GitLab Enterprise (CORE) errors

Configure virtual network peering

To connect two instances internally you can enable a Virtual Network (VNet) peering from the Azure Portal. Depending if the instances were launched in the same or in different resource groups, there are two methods for performing a internal connection: sharing a virtual network or enabling a virtual network peering.

  • Learn how to share a virtual network to join instances from the same resource group.
  • Learn how to enable virtual network peering to join instances from different resource groups.

In this article

Last modification May 20, 2025

Bitnami by VMware Tanzu Logo

See Bitnami's Twitter profile. Twitter icon See Bitnami's Github profile. Github icon See Bitnami's Youtube profile. Youtube icon See Bitnami's LinkedIn profile. LinkedIn icon

Copyright © 2005-2025 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

    Products

  • Application Catalog
  • VMware Tanzu App Catalog

    Solutions

  • Kubernetes

    Company

  • Careers
  • Resources
  • Blog
  • Contact

    Legal

  • Terms of Use
  • Trademark
  • Privacy
  • Your California Privacy Rights

    Support

  • Docs
  • Bitnami Images
  • Helm Charts
  • Containers