You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The corresponding attribute reposerver.max.combined.directory.manifests.size is set to 20M and annotated with the necessary labels.
Neither the reposerver pod deployment (command) nor the environment variables show the corresponsing value. The config map after being created is not referenced anywhere or mounted.
The base manifest of the downstream reposerver references the argocd-cmd-params-cm with envFrom. It seems to be missing in the operator deployment.
OCP: v4.14.
Operator Version: 1.14.0
Expected behavior
The params cm should be mounted as volume for envFrom to the corresponding argocd component and used in the cli command.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
The corresponding attribute reposerver.max.combined.directory.manifests.size is set to 20M and annotated with the necessary labels.
Neither the reposerver pod deployment (command) nor the environment variables show the corresponsing value. The config map after being created is not referenced anywhere or mounted.
The base manifest of the downstream reposerver references the argocd-cmd-params-cm with envFrom. It seems to be missing in the operator deployment.
OCP: v4.14.
Operator Version: 1.14.0
Expected behavior
The params cm should be mounted as volume for envFrom to the corresponding argocd component and used in the cli command.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: