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
{{ message }}
This repository has been archived by the owner on Jul 24, 2018. It is now read-only.
Is this a bug report or feature request? (choose one): Bug
Python Version (output of python --version): N/A
Development or Deployment Environment?: N/A
Release Tag or Master: Master
Expected Behavior: That releases do not have a prefix attached to the name.
What Actually Happened: Charts deployed have a prefix attached to the name.
How to Reproduce the Issue (as minimally as possible):
Any Additional Comments:
Rather than using a prefix attached to the release name of a chart - could we explore using alternatives to track Armada managed releases. Taking a leaf from Helm/Tiller's book may be appropriate here - and the releases could be simply managed via a config map in the same namespace as Tiller.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a bug report or feature request? (choose one): Bug
Python Version (output of
python --version
): N/ADevelopment or Deployment Environment?: N/A
Release Tag or Master: Master
Expected Behavior: That releases do not have a prefix attached to the name.
What Actually Happened: Charts deployed have a prefix attached to the name.
How to Reproduce the Issue (as minimally as possible):
Any Additional Comments:
Rather than using a prefix attached to the release name of a chart - could we explore using alternatives to track Armada managed releases. Taking a leaf from Helm/Tiller's book may be appropriate here - and the releases could be simply managed via a config map in the same namespace as Tiller.
The text was updated successfully, but these errors were encountered: