-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to create an app from private repository #1411
Comments
Ok, I got the problem. I have to update known_hosts in each argoCD deployment, not only in argocd-server. |
Hi i have same problem how do you update them? |
Working on documenting the steps to support private repository with self-signed certificates. |
@andreyvelich Thanks for you answer. Your solution didn't work for me so i updated know host and it worked. Documentation would really help in this case. ---
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app.kubernetes.io/component: server
app.kubernetes.io/name: argocd-server
app.kubernetes.io/part-of: argocd
name: argocd-server
spec:
selector:
matchLabels:
app.kubernetes.io/name: argocd-server
template:
metadata:
annotations:
prometheus.io/scrape: "true"
prometheus.io/path: "/metrics"
prometheus.io/port: "8083"
labels:
app.kubernetes.io/name: argocd-server
spec:
containers:
- command:
- argocd-server
- --insecure
- --staticassets
- /shared/app
image: argoproj/argocd:v0.12.1
imagePullPolicy: Always
name: argocd-server
ports:
- containerPort: 8080
- containerPort: 8083
readinessProbe:
httpGet:
path: /healthz
port: 8080
initialDelaySeconds: 3
periodSeconds: 30
volumeMounts:
- mountPath: /shared
name: static-files
- name: known-hosts
mountPath: /etc/ssh/ssh_known_hosts
subPath: known_hosts
initContainers:
- command:
- cp
- -r
- /app
- /shared
image: argoproj/argocd-ui:v0.12.1
imagePullPolicy: Always
name: ui
volumeMounts:
- mountPath: /shared
name: static-files
serviceAccountName: argocd-server
volumes:
- emptyDir: {}
name: static-files
- name: known-hosts
configMap:
name: argo-known-hosts
---
apiVersion: v1
kind: ConfigMap
metadata:
name: argo-known-hosts
data:
known_hosts: |-
gitlab.mine.infra,172.168.10.0 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlyaHAyNTYAAAAIbmlzdHAyNTYAAABBBGRMHcvQ4qX8lkn4g/mEpXDUTL2LzKlvV5sEYAEu1Ztpu6volX19zpkquXxpa59XCmoeuuBR97t3Q/qK6Wvymec= |
Has any new documentation made it up covering this yet? Still not sure exactly how to get a private repo to work from these scattered comments.. |
Sorry for the delay. This one is next on the list. Will test, prepare docs today evening, latest tomorrow morning |
@alexmt Ok, thank you! |
@alexmt Needing this too. Any help is appreciated. |
Configured gitlab with self-signed cert and tested various scenarios. Tried to document my findings in this PR: #1515 :
Please let me know if it helps. |
Related #1322 |
test |
Describe the bug
I am not available to create an app from connected GitHub repository.
To Reproduce
I tried to create an app in ArgoCD from our private GitHub repository. I followed this approach #827 and successfully connected our private repository to ArgoCD.
After that, I tried this command:
I got this error:
Expected behavior
App should be created, when my repository successfully connected to ArgoCD, isn't it?
The text was updated successfully, but these errors were encountered: