-
Notifications
You must be signed in to change notification settings - Fork 3
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
stigatron nats images #151
Comments
we have not pushed the nats images to carbide as we weren't sure it would be necessary |
hey @dweomer, is there an update on this issue? it has been a few months since nats was added to carbide. |
hey @dweomer / @amartin120, any update on this? |
We had a customer hitting this as well (RGS ZD Ticket #4909). |
hey @dweomer, is there any progress on this? a customer mentioned this last week |
hey @dweomer, any updates on this? still have this issue |
something to revisit @CamrynCarter... |
In one of the recents updates/releases of
stigatron
, support fornats
was added. When reviewing the upstream and publicnats
helm chart, there is the ability to add a private registry for thenats
images. When adding thenats
private registry value to the helm chart, it fails to pull the images from the carbide registry.Are the
nats
images supposed to be available and a part of the carbide images registry/pipeline? If not, are we able to add the images and update default values forstigatron
?https://github.com/zackbradys/rgs-carbide/blob/b7d2e5016d719ed697304bdb82316dacc0a2ee92/fleet/carbide/stigatron/stigatron-values.yaml:
The text was updated successfully, but these errors were encountered: