Change Details

Related to T4046 Unfortunately, it's not possible to assign an static ip address to the private endpoint without using a load balancer ~Remaining tasks~: - [x] Test the public ip allocation The public ip is allocated when the ingress controllers are created by the gitlab operator - [x] try to deploy the gitlab operator with terraform It doesn't seem to suit our needs. The kubernetes provider [1] is oriented to deploy components explicitly configured by terraform and not through a yaml file. It also has the problem of the local cluster configuration as the cluster fqdn must be declared in the local /etc/hosts to be able to interact with it (due to the certificate verification). - [x] move the aks configuration outside the gitlab module The gitlab module now relies on a kubernetes modules that can be used independently to instantiate an aks cluster not related to gitlab [1] https://registry.terraform.io/providers/hashicorp/kubernetes/1.11.0/docs

Related to T4046 Unfortunately, it's not possible to assign an static ip address to the private endpoint without using a load balancer ~~Remaining tasks~~: - [x] Test the public ip allocation The public ip is allocated when the ingress controllers are created by the gitlab operator - [x] try to deploy the gitlab operator with terraform It doesn't seem to suit our needs. The kubernetes provider [1] is oriented to deploy components explicitly configured by terraform and not through a yaml file. It also has the problem of the local cluster configuration as the cluster fqdn must be declared in the local /etc/hosts to be able to interact with it (due to the certificate verification). - [x] move the aks configuration outside the gitlab module The gitlab module now relies on a kubernetes modules that can be used independently to instantiate an aks cluster not related to gitlab [1] https://registry.terraform.io/providers/hashicorp/kubernetes/1.11.0/docs

Related to T4046 Unfortunately, it's not possible to assign an static ip address to the private endpoint without using a load balancer ~~~Remaining tasks~:~~: - [x] Test the public ip allocation The public ip is allocated when the ingress controllers are created by the gitlab operator - [x] try to deploy the gitlab operator with terraform It doesn't seem to suit our needs. The kubernetes provider [1] is oriented to deploy components explicitly configured by terraform and not through a yaml file. It also has the problem of the local cluster configuration as the cluster fqdn must be declared in the local /etc/hosts to be able to interact with it (due to the certificate verification). - [x] move the aks configuration outside the gitlab module The gitlab module now relies on a kubernetes modules that can be used independently to instantiate an aks cluster not related to gitlab [1] https://registry.terraform.io/providers/hashicorp/kubernetes/1.11.0/docs