rollout-extension
rollout-extension copied to clipboard
argocd-extension-installer is deployed but "more" tab is missing in argoCD UI.
Argo rollouts version: 1.7.1 (Installed in argo-rollouts namespace). ArgoCD version: 2.11.5 (Installed in argocd namespace via helm chart)
extensions:
enabled: true
image:
repository: "quay.io/argoprojlabs/argocd-extension-installer"
tag: "v0.0.5"
imagePullPolicy: ""
extensionList:
- name: rollout-extension
env:
- name: EXTENSION_URL
value: https://github.com/argoproj-labs/rollout-extension/releases/download/v0.3.5/extension.tar
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.
did you manage to sort this ?
I had the same question in the beginning, but finally found that this extension is only for Rollout objects inside an Application. It adds a "Rollout" tab for Rollout objects to view the rollout status.
@rajgupta2720, do you have any solution for this?
I have the same issues.
Argo rollouts version: 1.7.2 (Installed in argo-rollouts namespace). ArgoCD version: v2.12.6+4dab5bd (Installed in good namespace via helm chart)
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
~~I have the same questions.
Argocd 2.9, 2.10
rollout-extension 0.1.0 - 0.3.6~~
upd. my mistake.I found a misconfiguration: readOnlyRootFilesystem was enabled, therefore the ArgoCD extensions installer couldn't create a temporary folder and exited without downloading the extension.