Shubham BansalandGitHub
6d117ad43a
Currently, we create Fission resources in the default namespace, function-related resources are created in the fission-function namespace, whereas builder resources are created in the fission-builder namespace. This causes confusion for a lot of users. In this fix, we allow the user to set the function and builder namespace empty so that function and builder resources are created in the same namespace as the function resource always. If the user desires older behaviour they can functionNamespace and builderNamespace the same previous before the upgrade. * use default namespace for fission function and builder * support for existing fission namespaces * Replace builder and function namespace with template * Fix namespace creation template Signed-off-by: Sanket Sudake <sanketsudake@gmail.com>
27 lines
900 B
YAML
27 lines
900 B
YAML
{{/*
|
|
Passing namespace as an argument to the "fissionFunction.rolebindings" template.
|
|
Need to use merge function to pass in the current scope so that ".Release" values
|
|
can be used
|
|
*/}}
|
|
{{ include "fissionFunction.rolebindings" (merge (dict "namespace" .Values.defaultNamespace) .) }}
|
|
---
|
|
apiVersion: rbac.authorization.k8s.io/v1
|
|
kind: RoleBinding
|
|
metadata:
|
|
name: {{ .Release.Name }}-fission-fetcher-pod-reader
|
|
namespace: {{ template "fission-function-ns" . }}
|
|
roleRef:
|
|
apiGroup: rbac.authorization.k8s.io
|
|
kind: Role
|
|
name: {{ .Release.Name }}-event-fetcher
|
|
subjects:
|
|
- kind: ServiceAccount
|
|
name: fission-fetcher
|
|
namespace: {{ template "fission-function-ns" . }}
|
|
|
|
{{- if not .Values.singleDefaultNamespace }}
|
|
{{- range $namespace := $.Values.additionalFissionNamespaces }}
|
|
{{ include "fissionFunction.rolebindings" (merge (dict "namespace" $namespace) $) }}
|
|
{{- end }}
|
|
{{- end }}
|