-
Notifications
You must be signed in to change notification settings - Fork 27
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 security context, update the app version and image tag #93
Conversation
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 we should also add the env variable GEOSERVER_CONTEXT_ROOT
, it allows or controls the path at which geoserver can be accessed externally. See the Readme for further context
charts/geoserver/v0.3.4/README.md
Outdated
@@ -0,0 +1,72 @@ | |||
# GeoServer | |||
|
|||
This is Kartoza's GeoServer Rancher charts |
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.
Is it for rancher or kubernetes?
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.
Kubernetes
|
||
- Default TLS enabled | ||
- Generate new datadir at startup if volume empty | ||
- Some plugins are shipped |
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.
Default extensions are activated on startup
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.
Added that on readme.
I've added the environment variable. Could you please review to ensure everything looks correct? |
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.
LGTM , left some comments
{{- end }} | ||
env: | ||
{{- if .Values.enableJSONP }} | ||
- name: ENABLE_JSONP |
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'd like to know why only this env was chosen to be exposed. This defaults to true so we can skip it. We need to pass env that affects the image in some 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.
I copied the deployment configuration from the previous Helm chart, which included exposing ENABLE_JSONP. While it defaults to true, we can consider disabling it if it's not necessary.
{{- tpl . $ | nindent 10 }} | ||
{{- end }} | ||
{{- else }} | ||
startupProbe: |
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 know if this probe happens internally or using the externally exposed geoserver? If it's the latter then this can be affected by env GEOSERVER_CONTEXT_ROOT
No description provided.