Superset used to start by running init_superset.sh which was
configurable. This commit adds that possibility back together with the
option to pass additional arguments to that script for configuring
start up.
Signed-off-by: Daniel Johansson <daniel.sjohansson@niradynamics.se>
Co-authored-by: Daniel Johansson <Daniel.SJohansson@niradynamics.se>
* updating maintainers list due to significant improvement in how app is started and big jump in version. Ongoing improvements to follow.
Signed-off-by: marcussorealheis <marcuseagan@gmail.com>
* add CI directory and security manager custom test values.
Signed-off-by: marcussorealheis <marcuseagan@gmail.com>
* update maintainer.
Signed-off-by: marcussorealheis <marcuseagan@gmail.com>
* add an owners file.
Signed-off-by: marcussorealheis <marcuseagan@gmail.com>
* adding bumped superset version in better branch name and clean PR.
Signed-off-by: marcussorealheis <marcuseagan@gmail.com>
* update to latest stable version and modify start commands for changes in project.
Signed-off-by: marcussorealheis <marcuseagan@gmail.com>
* remove typo missed in terminal diff.
Signed-off-by: marcussorealheis <marcuseagan@gmail.com>
* fixed name of char for linter.
Signed-off-by: marcussorealheis <marcuseagan@gmail.com>
* Start Superset with appropriate webserver and host:port binding
Signed-off-by: marcussorealheis <marcuseagan@gmail.com>
- I would like to add deployment level annotations. I am currently using
this patch along side kube2iam to apply aws instance credentials to the
pods.
Signed-off-by: Hiroshi Fukada <hiroshi@fukada.us>
* [stable/superset] Use the target port number instead of a name
Older (but still actual) versions of some Network Policy providers don't support named ports as
a value of `targetPort` field in the Service spec.
Changing it to the number shouldn't break the UX for existing installations.
Signed-off-by: Mikhail Zholobov <legal90@gmail.com>
* [stable/superset] Bump version
Signed-off-by: Mikhail Zholobov <legal90@gmail.com>
The default container (amancevice/superset) creates
a user 'superset' with uid 1000, expecting to run as that.
There is no need to run 'privileged'.
Signed-off-by: Don Bowman <db@donbowman.ca>
* Add imagePullSecrets for stable/superset chart
Signed-off-by: Don Bowman <db@donbowman.ca>
* Inadvertently added this file, removed.
Signed-off-by: Don Bowman <db@donbowman.ca>
* - support service annotations and in general more settings on the service
- there is an actual health check endpoint in superset /health so let's use that one
Signed-off-by: Justin Heesemann <justin.heesemann@holidu.com>
* increment chart version
Signed-off-by: Justin Heesemann <justin.heesemann@holidu.com>
* change version bump to be 1.0.0 since its in stable.
Signed-off-by: Paul Czarkowski <username.taken@gmail.com>
* added Apache superset charts
* removed apiVersion
* use apiVersion: apps/v1
* added docu for missing values, change to amancevice/superset image
* use amancevice/superset image
* don't make containerPort configurable
* fixed docu for image values
* Added release label to selector
* use current image version
* default pullPolicy to "IfNotPresent"
* moved to stable repo
* prettify Readme
* Kubernetes 1.9+
* fix default value for image.tag