argoproj / argoproj/argo-cd

ArgoCD omites values.yaml file under subfolders

Open
#8,697 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
24.2k
Forks
7.9k
Avg merge
1d 6h
Merged PRs (30d)
239

Description

Looks like ArgoCD is omiting the values.yaml file under my subfolder:

![image](https://user-images.githubusercontent.com/65667266/157034838-4f0a82a7-4647-440b-a474-4a09fe3c1b73.png)

I am using app of apps approach so first I install ArgoCD through Terraform and later ArgoCD will install all the necessary app for the cluster.

This is my chart.yaml

![image](https://user-images.githubusercontent.com/65667266/157035013-cc413099-d792-4b26-b95c-039416e1cfe1.png)

and this is a piece of code of values.yaml file that overrides the default one.
```
external:
enabled: false

internal:
# -- Enables an additional internal load balancer (besides the external one).
enabled: true
# -- Annotations are mandatory for the load balancer to come up. Varies with the cloud service.
annotations:
service.beta.kubernetes.io/azure-load-balancer-internal: "true"

loadBalancerIP: "10.xx.xx.xx" #

# -- Restrict access For LoadBalancer service. Defaults to 0.0.0.0/0.
loadBalancerSourceRanges: []
```

I specified this code to get always the same private IP for my ingress svc LoadBalancer.

ingress-nginx is installed successfully but looks like omits the values.yaml file where I have specified an IP for the internal loadbalancer...

However if I install it manually using helm install ... -f values.yaml the ingress svc loadbalancer is picking up the IP that I specified in values.yaml file...

Any idea about this?

Thanks.

Contributor guide

Open the contributing guide

Research direction

Start by comparing the app-of-apps ArgoCD configuration with the chart.yaml and values.yaml shown, then reproduce the difference between ArgoCD deployment and the manual helm install. Done means the nested values.yaml is applied and the ingress service receives the specified internal load balancer IP.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes, terraform
Domain
ci-cd, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.