-
Notifications
You must be signed in to change notification settings - Fork 46
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
argocd-extension-installer is deployed but "more" tab is missing in argoCD UI. #80
Comments
rajgupta2720
changed the title
argocd-extension-installer is deployed but "more" tab is missing.
argocd-extension-installer is deployed but "more" tab is missing in argoCD UI.
Jul 23, 2024
did you manage to sort this ? |
@rajgupta2720, do you have any solution for this? I have the same issues. Argo rollouts version: 1.7.2 (Installed in argo-rollouts namespace). When I tried to view the created pod manifest, I got this. initContainers:
- env:
- name: EXTENSION_URL
value: https://github.com/argoproj-labs/rollout-extension/releases/download/v0.3.4/extension.tar
image: quay.io/argoprojlabs/argocd-extension-installer:v0.0.5
imagePullPolicy: IfNotPresent
name: rollout-extension
resources: {}
securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
readOnlyRootFilesystem: true
runAsNonRoot: true
runAsUser: 1000
seccompProfile:
type: RuntimeDefault
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
- mountPath: /tmp/extensions/
name: extensions
- mountPath: /tmp
name: tmp
- mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: kube-api-access-7cv7r
readOnly: true
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Argo rollouts version: 1.7.1 (Installed in argo-rollouts namespace).
ArgoCD version: 2.11.5 (Installed in argocd namespace via helm chart)
I could see init-container is completed successfully. However, I can't see extension or "more" tab in ArgoCD UI or is there any other way to verify? Not sure what am I missing.
The text was updated successfully, but these errors were encountered: