-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Support Azure Storage account as default artifact repo #9595
Comments
You need to use the latest version, at least 3.4. |
Ah, then the doc's have not been updated yet as of v3.4.0-rc4. Do you maybe also know in which PR/commit this was introduced? |
It's added in #9026 by @brianloss. @brianloss Would you like to help update the documentation? |
It's already documented on that page in the table at the top and with a detailed section |
… Azure Blob Storage. Fixes #9595 (#9597) docs: update default artifact repository docs for Azure Signed-off-by: Brian Loss <[email protected]> Signed-off-by: Brian Loss <[email protected]>
… Azure Blob Storage. Fixes argoproj#9595 (argoproj#9597) docs: update default artifact repository docs for Azure Signed-off-by: Brian Loss <[email protected]> Signed-off-by: Brian Loss <[email protected]> Signed-off-by: juchao <[email protected]>
This is a new issue based on my comment in #1540
Azure File storage support is now available for artifacts, but it can not be used as defaultArtifactRepo yep.
Now that minio gateway is being deprecated, this seems like an important thing to add to support deployments on Azure.
Same, when I try to use azure as defaultArtifactRepo, the configmap is empty except this exception:
Originally posted by @Transmitt0r in #1540 (comment)
The text was updated successfully, but these errors were encountered: