terraform-provider-libvirt
ingress-nginx
terraform-provider-libvirt | ingress-nginx | |
---|---|---|
13 | 203 | |
1,513 | 16,664 | |
- | 0.7% | |
6.8 | 9.6 | |
13 days ago | 6 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-provider-libvirt
- What do y'all use to provision KVM VM's?
-
libvirt-k8s-provisioner - Ansible and terraform to build a cluster from scratch in less than 10 minutes ok KVM - Updated for 1.26
libvirt-terraform-provider ( based on https://github.com/dmacvicar/terraform-provider-libvirt )
- NixOS 22.11 “Raccoon” Released
-
libvirt-ocp4-provisioner - Provision an OCP 4.x.y cluster in minutes with Ansible, now with Single Node OCP support! .
Hi guys!I wanted to allotment with you a tool to provision a fully working OCP 4.x.y cluster in minutes using Ansible for automation, libvirt as virtualization provider and terraform as VMs templating and creation tool. https://github.com/kubealex/libvirt-ocp4-provisioner It will take care of all the infrastructure provisioning and OCP machines provisioning, starting and completing the UPI installation of a cluster. (IPI work in progress ;) ) To give a quick overview, this project will allow you to provision a fully working OCP stable environment, consisting of: * Bastion machine provisioned with: * dnsmasq (with SELinux module, compiled and activated) * dhcp based on dnsmasq * nginx (for ignition files and rhcos pxe-boot) * pxeboot * Loadbalancer machine provisioned with: * haproxy * OCP Bootstrap machine * OCP Master(s) VM(s) * OCP Worker(s) VM(s) From latest release, it also supports installing SNO on a single host! It also takes care of preparing the host machine with needed packages, configuring: * dedicated libvirt network (fully customizable) * dedicated libvirt storage pool (fully customizable) * terraform * libvirt-terraform-provider ( compiled and initialized basedon https://github.com/dmacvicar/terraform-provider-libvirt) PXE is automatic, based on MAC binding to different OCP nodes role, so no need of choosing it from the menus, this means you can just run the playbook, take a beer and have your fully running OCP 4.9.latest stable up and running. It has been tested on Fedora 3x and CentOS 7/8. Playing around with it and contributions to make it work even on different OSes is more than welcome, hope you enjoy it! Alex
-
Need help on Terraform with KVM/Libvirt
I learned and got terraform to work with the KVM/Libvirt provider.
-
Automate creation of KVM VM and Installation of OS
I saw Terraform with the dmacvicar/terraform-provider-libvirt provider, but sadly didn't get really warm with it. When some can explain to me how I can set up new images for every VM I would be very happy also there are more question in the pipeline. Sadly, the “Documentation” is not really that good. Maybe Terraform is also the wrong Application for me. I'm a little lost because I thought Terraform would be the big Solution I want and need, until now, not yet.
-
Terraform Persistent Storage
It looks like there was an issue dealing with "attaching an existing disk" to a terraform created VM. That's here: https://github.com/dmacvicar/terraform-provider-libvirt/issues/688
-
Those of you running a home cluster that is NOT comprised of RasPis, what hardware are you using?
Nice. I’m straight KVM as it’s a mirror of work (my Lab) and I’m using the terraform-provider-libvirt provider. 20 minutes to fully build a site. Pretty cool.
-
Provision a full functional cluster in less than 10 minutes! libvirt-k8s-provisioner
libvirt-terraform-provider ( compiled and initialized based on https://github.com/dmacvicar/terraform-provider-libvirt)
- QEMU Version 6.0.0 Released
ingress-nginx
-
Automating EKS Deployment and NGINX Setup Using Helm with AWS CDK in Python
# Add NGINX ingress using Helm eks.HelmChart( self, "NginxIngress", cluster=cluster, chart="ingress-nginx", repository="https://kubernetes.github.io/ingress-nginx", namespace="ingress-nginx", values=helm_values )
-
deploying a minio service to kubernetes
ingress-nginx
-
Upgrading Hundreds of Kubernetes Clusters
The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.
-
[06/52] Accessible Kubernetes with Terraform and DigitalOcean
resource "helm_release" "icrelease" { name = "nginx-ingress" repository = "https://kubernetes.github.io/ingress-nginx" chart = "ingress-nginx" version = "4.9.1" namespace = kubernetes_namespace.icnamespace.metadata[0].name set { name = "controller.ingressClassResource.default" value = "true" } }
-
Deploy Ghost with MySQL DB replication using helm chart
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx --namespace ingress-nginx --create-namespace -f custom/ghost/nginx.yaml
-
Kubernetes Gateway API v1.0: Should You Switch?
For example, if you chose Nginx Ingress, you will use some of its dozens of annotations that are not portable if you decide to switch to another Ingress implementation like Apache APISIX.
- nginx ingress controller installation
-
IP-Whitlisting: Is adjusting nginx-ingress-controller service a solution?
The controller is installed with helm upgrade --install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ingress-nginx --namespace ingress-nginx --create-namespace
-
Deploy Rancher on AWS EKS using Terraform & Helm Charts
helm repo add jetstack https://charts.jetstack.io helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo add rancher-latest https://releases.rancher.com/server-charts/latest helm repo update helm repo list
-
☸️ Kubernetes NGINX Ingress Controller: 10+ Complementary Configurations for Web Applications
Everything in the YAML snippets below — except for ingress configuration — relates to configuring the NGINX ingress controller. This includes customizing the default configuration.
What are some alternatives?
UTM - Virtual machines for iOS and macOS
traefik - The Cloud Native Application Proxy
terraform-provider-proxmox - Terraform provider plugin for proxmox
emissary - open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
terraform-provider-rancher2 - Terraform Rancher2 provider
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
QEMU - Official QEMU mirror. Please see https://www.qemu.org/contribute/ for how to submit changes to QEMU. Pull Requests are ignored. Please only use release tarballs from the QEMU website.
cilium-cli - CLI to install, manage & troubleshoot Kubernetes clusters running Cilium
libvirt-k8s-provisioner - Automate your k8s installation
haproxy-ingress - HAProxy Ingress
xemu - Original Xbox Emulator for Windows, macOS, and Linux (Active Development)
application-gateway-kubernetes-ingress - This is an ingress controller that can be run on Azure Kubernetes Service (AKS) to allow an Azure Application Gateway to act as the ingress for an AKS cluster.