Hi
I have followed the link https://medium.com/nerd-for-tech/terraforming-the-gitops-way-9417cf4abf58 for doing a setup of atlantis server on EKS. When a PR is created it does do a initial init, plan. But, when I comment atlantis plan/atlantis apply on the commit it does not do anything. Following is my repo config

repoConfig: |
  ---
  repos:
  - id: /.*/
    branch: /.*/
    apply_requirements: [approved, mergeable] 
    workflow: default
    allowed_overrides: []
    allow_custom_workflows: false
  workflows:
    default:
      plan:
        steps: [init, plan]
      apply:
        steps: [apply]

Would you be able to help me on this

running "/atlantis-data/bin/terraform0.15.5 init -input=false -upgrade" in "/atlantis-data/repos/abc/tf-deploy-aws-atlantis/1/default": exit status 1
In Terraform Init and Plan

Initializing the backend...
╷
│ Warning: Version constraints inside provider configuration blocks are deprecated
│
│ on provider_aws.tf line 3, in provider "aws":
│ 3: version = "~> 0.13"
│
╷
│ Terraform 0.13 and earlier allowed provider version constraints inside the
│ Error: error configuring S3 Backend: IAM Role (arn:aws:iam::0000000000:role/AssumeDevelopersRoleInDevelopment) cannot be assumed.
│
│ provider configuration block, but that is now deprecated and will be
│ removed in a future version of Terraform. To silence this warning, move the
│ There are a number of possible causes of this - the most common are:
│ * The credentials used in order to assume the role are invalid
│ provider version constraint into the required_providers block.
╵
│ * The credentials do not have appropriate permission to assume the role
│ * The role ARN is not valid

│
│ Error: NoCredentialProviders: no valid providers in chain. Deprecated.
│ For verbose messaging see aws.Config.CredentialsChainVerboseErrors
│
│
│
╵

kubectl get all -l app.kubernetes.io/part-of=rabbitmq
NAME READY STATUS RESTARTS AGE
pod/production-rabbitmqcluster-server-0 0/1 Pending 0 116s
pod/production-rabbitmqcluster-server-1 0/1 Pending 0 116s
pod/production-rabbitmqcluster-server-2 0/1 Pending 0 116s

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/production-rabbitmqcluster-nodes ClusterIP None 4369/TCP,25672/TCP 117s
service/production-rabbitmqcluster LoadBalancer 10.152.183.131 5672:31684/TCP,15672:32510/TCP,15692:30154/TCP 117s

NAME READY AGE
statefulset.apps/production-rabbitmqcluster-server 0/3 116s

Warning FailedScheduling 3m2s default-scheduler 0/2 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling..
Warning FailedScheduling 3m default-scheduler 0/2 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling..

is there anything i missed?

Hi @pavan-kumar-99 ,

I was following your tutorial for setting up Thanos with Sidecar. After I deploy thanos ingress on external k8s clusters with tls/port 443 and try to configure thanos stores on thanos cluster, it fails to connect.

I keep getting connection errors as such

level=warn ts=2022-01-05T20:40:33.268164041Z caller=endpointset.go:500 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from thanos-1:443: rpc error: code = Internal desc = stream terminated by RST_STREAM with error code: FRAME_SIZE_ERROR" address=thanos-1:443
level=warn ts=2022-01-05T20:40:38.029698764Z caller=endpointset.go:500 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from thanos-2:443: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=thanos-2:443

Have you experienced something similar?

Thanks in advance!