Closed dicolasi closed 3 years ago
Whenever I got a promotion from dev to stage and production, the repository dev2 is added:
dev2
repositories: - name: dev url: https://chartmuseum.dev.property.xyz - name: dev2 url: http://jenkins-x-chartmuseum.jx.svc.cluster.local:8080 releases:
This would cause an error in stage and production environments since dev2 it is not reachable.
3 clusters (eks-vault):
Dev2 it is not added, but dev would be used as default chart.
Dev2 is added causing the following to happen:
- chart: dev2/data-outcode-stats-service version: 1.0.22 name: data-outcode-stats-service values: - jx-values.yaml
Which will result in a error in jx-boot (repo unreachable).
The output of jx version is:
jx version
version: 3.1.251
![Uploading Screenshot 2021-02-19 at 13.17.37.png…]()
we now use the ingress URL on remote clusters. the service URLs still work for environments inside the same cluster
Summary
Whenever I got a promotion from dev to stage and production, the repository
dev2
is added:This would cause an error in stage and production environments since dev2 it is not reachable.
Steps to reproduce the behavior
3 clusters (eks-vault):
Expected behavior
Dev2 it is not added, but dev would be used as default chart.
Actual behavior
Dev2 is added causing the following to happen:
Which will result in a error in jx-boot (repo unreachable).
Jx version
The output of
jx version
is: