-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add 'disable_tls' and 'dev_deployment' modifications #282
Conversation
cb67401
to
946ac46
Compare
environments.yaml.tmpl
Outdated
- ../etc/_mods/disable_tls.yaml | ||
{{ end }} | ||
{{ if .Values.dev_deployment }} | ||
- ../etc/_mods/disable_tls.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As the number of helmfile related configs have increased I suggest moving all of them to a different root directory, it will make things more clear and more easy to manage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I moved the files to a new directory mods in the root.
etc/_mods/local_development.yaml
Outdated
configurationOverrides: | ||
"offsets.topic.replication.factor": 1 | ||
cp_zookeeper: | ||
servers: 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we move the configs that make the apps run only one replica to the base.yaml? As we try to have a minimal working config in the default configuration I think it's good to have them there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rather not do that in this PR. I would need to very carefully inspect the consequences because we change default behavior. Would be good to create a new issue for this.
cert_manager: | ||
prometheus: | ||
servicemonitor: | ||
enabled: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be false?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess you are right.... Chnaged
sidecars: [] | ||
radar_grafana: | ||
_install: false | ||
radar_jdbc_connector: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't these part of RADAR-Base apps? Why are they being disabled?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes, I mistook it for graylog... updated.
environments.yaml.tmpl
Outdated
{{ end }} | ||
{{ if .Values.dev_deployment }} | ||
- ../etc/_mods/disable_tls.yaml | ||
- ../etc/_mods/disable_logging_and_monitoring.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there should be a separate flag for disabling logging and monitoring and it should be true since it doesn't need to be enabled for a simple default installation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disabled logging and monitoring in the default deployment. We need to be careful here, because this change is not backwards compatible. We should provide a migration note here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it's good to mention in release notes to manually enable these components during upgrade.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also created a separate flag to disable monitoring and logging.
Closes #12 |
77fa8c8
to
2f4c0c7
Compare
environments.yaml.tmpl
Outdated
- ../etc/secrets.yaml | ||
default: | ||
values: | ||
- ../etc/base.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think it would be good to move these files helmfile related files to a separate directory as well? Probably something like helmfile_configs
to put all of it's configuration related files in it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this would make sense yes. Should we do this now? We have to make sure all the scripts in the /bin folder play nice with this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be probably better in the long run make things more organized but we can do it later if it is easier.
- ../etc/production.yaml.gotmpl | ||
- ../etc/secrets.yaml | ||
{{ if not .Values.enable_tls }} | ||
- ../mods/disable_tls.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To reduce confusion I think these 2 lines should either be enable_tls
or disable_tls
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is a matter of API design, I guess. The config file disables tls and is, therefore, correctly named. What are the config options that we would like to present:
A:
# Enable logging and monitoring
enable_logging_monitoring: false
# Enable TLS redirection and retrieval of Let's Encrypt certificates.
# Can be disabled when TLS termination is handled upstream of the on-cluster Nginx reverse proxy.
enable_tls: true
B:
# Disable logging and monitoring
disable_logging_monitoring: true
# Disable TLS redirection and retrieval of Let's Encrypt certificates.
# Can be disabled when TLS termination is handled upstream of the on-cluster Nginx reverse proxy.
disable_tls: false
I am fine either way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there is a /mods/disable_tls.yaml
and I think the variable should also be disable_tls
2f4c0c7
to
7676cc2
Compare
fc9415e
to
b98490e
Compare
b98490e
to
5776a12
Compare
5776a12
to
1be83bc
Compare
For local development I introduce the following modifications to the default RADAR-base deployment: