Skip to content
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

Fallback to Helm .Release.Namespace when .namespace not defined #101

Merged
merged 2 commits into from
Jun 11, 2020

Conversation

enriched
Copy link
Contributor

@enriched enriched commented Jun 8, 2020

This defaults the pulsar namespace to helms default .Release.Namespace if namespace is not defined. This is implemented in the new "pulsar.namespace" template.

The .namespace is set to "pulsar" in the default values.yaml, in order to unset it --set namespace=null can be passed to the helm install command.

closes #100

This defaults the pulsar namespace to helms default .Release.Namespace if namespace is not defined.
@sijie sijie added this to the 1.2.0 milestone Jun 11, 2020
@sijie
Copy link
Member

sijie commented Jun 11, 2020

@enriched great contribution!

@sijie sijie merged commit b0dc5e6 into streamnative:master Jun 11, 2020
@austince
Copy link

austince commented Jun 19, 2020

Hey, thanks for this contribution! Please correct me if I'm wrong, but I think it might have missed a few instances in some of the .tpl files:

{{- define "pulsar.zookeeper.hostname" -}}
${HOSTNAME}.{{ template "pulsar.zookeeper.service" . }}.{{ .Values.namespace }}.svc.cluster.local
{{- end -}}

I've found reference to the direct .namespace value in the following directory's _{dir}.tpl

  • autorecovery
  • bookkeeper
  • broker
  • pulsar_manager
  • toolset
  • zookeeper

Should I open up a new issue for this?

@enriched
Copy link
Contributor Author

@austince I think you're right, thanks for catching that! If you could open a new issue that would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Provide a way to use the --namespace from helm
3 participants