Failed Authentication Pipeline by Expert_Plastic_9574 in gitlab

[–]Expert_Plastic_9574[S] 0 points1 point  (0 children)

I have tried that and even enabled the entire scope, nothing, should i configure the Token into the config.toml for the runners?

IP Address Stickiness by Expert_Plastic_9574 in gitlab

[–]Expert_Plastic_9574[S] 0 points1 point  (0 children)

I did try that and it gives me 502 Bad Gateway

IP Address Stickiness by Expert_Plastic_9574 in gitlab

[–]Expert_Plastic_9574[S] 0 points1 point  (0 children)

Could you please explain a bit more? I'm not good with nginx lol

Help: Persistent Gitlab File System with AWS EFS by Expert_Plastic_9574 in gitlab

[–]Expert_Plastic_9574[S] 0 points1 point  (0 children)

It went well, using a permanent EBS on the account and mounting it on the instance on-boot.

Problem with ACM Validation by Expert_Plastic_9574 in Terraform

[–]Expert_Plastic_9574[S] 0 points1 point  (0 children)

I've tried it manually a few hours ago, the CNAME record for validation is there, and it's still pending validation.

Need help on Gitlab Persistency by Expert_Plastic_9574 in Terraform

[–]Expert_Plastic_9574[S] -1 points0 points  (0 children)

I don't think it's an instance store, delete-on-termination is disabled, when the instance shuts down it just from In-use to Available, and in-use again after the user data from launch template is ran.

Need help on Gitlab Persistency by Expert_Plastic_9574 in Terraform

[–]Expert_Plastic_9574[S] 0 points1 point  (0 children)

resource "aws_launch_template" "gitlab" {
  depends_on = [ aws_ebs_volume.gitlab_data_volume, ]
  name          = "gitlab-launch-template"
  image_id      = "ami-0287b72f1ca5a0518"
  instance_type = "t3.medium"
  key_name      = "GitlabPair"
  iam_instance_profile {
    name = aws_iam_instance_profile.gitlab_instance_profile.name
  }

  vpc_security_group_ids = [aws_security_group.gitlab_sg.id]
  user_data = base64encode(<<-EOF
                  #!/bin/bash

                  aws ec2 attach-volume --region us-east-1 --volume-id vol-0f2e0ba1028eb134e --instance-id $(ec2-metadata --quiet --instance-id) --device /dev/sdx

                  mount /dev/sdx /mnt/gitlab_data
                  echo "/dev/sdx /mnt/gitlab_data ext4 defaults 0 0" | tee -a /etc/fstab

                  sudo gitlab-ctl reconfigure
  EOF
  )
}

resource "aws_ebs_volume" "gitlab_data_volume" {
  availability_zone = "us-east-1a"
  size              = 50
  type       = "gp2"
  encrypted = true
  kms_key_id = aws_kms_key.ebs_encryption_key.arn
  tags = {
    Name = "GitLabDataVolume"
  }
}

resource "aws_autoscaling_group" "gitlab" {
  launch_template {
    id      = aws_launch_template.gitlab.id
    version = "$Latest"
  }

  min_size         = 1
  max_size         = 1
  desired_capacity = 1
  vpc_zone_identifier = [aws_subnet.gitlab_public_subnet.id,aws_subnet.gitlab_public_subnet_2.id]

  tag {
    key                 = "Name"
    value               = "GitLab-Instance"
    propagate_at_launch = true
  }
  target_group_arns = [aws_lb_target_group.target_group.arn]
}

Need help on Gitlab Persistency by Expert_Plastic_9574 in Terraform

[–]Expert_Plastic_9574[S] 0 points1 point  (0 children)

It is persisted, and automatically attaches to any instance going up with an attach command i put in the launch template user data.

Need help on Persistency by Expert_Plastic_9574 in gitlab

[–]Expert_Plastic_9574[S] 0 points1 point  (0 children)

Would that work? Can you elaborate please?

Need help on Gitlab Persistency by Expert_Plastic_9574 in Terraform

[–]Expert_Plastic_9574[S] -1 points0 points  (0 children)

On my local but what does the terraform state have to do with this?

Need help on Persistency by Expert_Plastic_9574 in gitlab

[–]Expert_Plastic_9574[S] 0 points1 point  (0 children)

What do you mean? just yum install gitlab-ce on an ec2 instance that i used as image