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
Just putting this out there for discussion. The charts set the namespace to default, but the environment variables for the api fqdns all assume 'hackfest'. It's not an issue for people following the lab exactly because our helm commands set the namespace to hackfest, but it's a bit inconsistent, and anyone messing with the namespace will hit issues where the service tracker UI cant hit the backend services.
Does it make sense to just swap out the 'default' everywhere with hackfest, or parameterize the namespace to give people more flexibility to play with the namespace?
The text was updated successfully, but these errors were encountered:
Just putting this out there for discussion. The charts set the namespace to default, but the environment variables for the api fqdns all assume 'hackfest'. It's not an issue for people following the lab exactly because our helm commands set the namespace to hackfest, but it's a bit inconsistent, and anyone messing with the namespace will hit issues where the service tracker UI cant hit the backend services.
Does it make sense to just swap out the 'default' everywhere with hackfest, or parameterize the namespace to give people more flexibility to play with the namespace?
The text was updated successfully, but these errors were encountered: