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
The DevfileRegistry CRD allows telemetry properties to be specified (registry name, key) and these are mapped to environment variables in the deployment but if a user updates these properties, they do not take into effect (i.e. no live updates). Users would need to re-create the pods in order to see the updates.
To Reproduce:
Deploy a DevfileRegistry with Telemetry configuration specified
Update the deployment with modified properties (registryName and/or key)
The environment variables in the pod are not updated
Expected behavior
Changes should occur on existing pod
Additional context
Looks like it's just the telemetry properties that are affected but I'll review the other ones to make sure we have everything covered.
Any workaround?
Delete the deployment. New pods should have the changes
Suggestion on how to fix the bug
Need to update this method to handle the environment variables:
The text was updated successfully, but these errors were encountered:
/kind bug
Which area this bug is related to?
/area registry
Bug Summary
Describe the bug:
The DevfileRegistry CRD allows telemetry properties to be specified (registry name, key) and these are mapped to environment variables in the deployment but if a user updates these properties, they do not take into effect (i.e. no live updates). Users would need to re-create the pods in order to see the updates.
To Reproduce:
registryName
and/orkey
)Expected behavior
Changes should occur on existing pod
Additional context
Looks like it's just the telemetry properties that are affected but I'll review the other ones to make sure we have everything covered.
Any workaround?
Delete the deployment. New pods should have the changes
Suggestion on how to fix the bug
Need to update this method to handle the environment variables:
The text was updated successfully, but these errors were encountered: