fix missing namespace environment variables for various services #2828
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Ensure all Namespace related environment variables are passed to the Fission Deployments.
As part of starting the services, CRDs are checked, which requires the correct
FISSION_DEFAULT_NAMESPACE
be set.Move all Namespace related environment variables to the 'fission-resource-namespace' macro to ensure all services know the relavant namespaces.
Which issue(s) this PR fixes:
Fixes #2732
Testing
Tested running in a cluster that doesn't use the
default
namespace; ie:Checklist: