set service.exposeAdmin=true -set ingress.enabled=true -set autoscaling.enabled=true -set autoscaling.minReplicas=3 -set autoscaling.MaxReplicas=7 And will we need to enable the ingress controller? I even tried the following parameters but the ingress service fails to set up I did look in to the ingress rules before posting this as an issue, I did not understand does this mean we need to deploy Kong in GKE with the default service.type which is ClusterIP? Because I do want to keep Kong HA, just trying to get a better understanding of how we can get ingress rules to control access as I am still quite new to all this.
#1 and 1 bitnami mean ssl upgrade
Can this later be expanded as well if I run Helm upgrade with that parameter? and we can set the storageclass as well using a parameter? and the deployment only creates 1 container of postgres, which I think we have to manually scale as the stateful does not have the option to auto scale is that correct? Will try out the parameter you mentioned for the size of disk. "client_secret" : os.Hello Thanks for your reply. # This will make sure the redirect_uri is properly computed, even with SSL offloadingįrom flask_ import AUTH_OAUTH Once you've identified the appropriate URL you can log in with:ĭefault security settings and passwords are included but you SHOULD override those with your own, in particular: Run kubectl port-forward superset-xxxx-yyyy :8088 to directly tunnel one pod's port into your localhostĭepending how you configured external access, the URL will vary.Set up an Ingress for it - the chart includes a definition, but will need to be tuned to your needs (hostname, tls, annotations etc.).Configure the Service as a LoadBalancer or NodePort.
To access it externally you will have to either: The chart will publish appropriate services to expose the Superset UI internally within your k8s cluster. 1 superset-celerybeat-xxxx-yyyy pod if you have supersetCeleryBeat.enabled = true in your values overrides.1 superset-redis-master-0 depending on your redis settings.1 superset-postgresql-0 depending on your postgres settings.N superset-xxxx-yyyy and superset-worker-xxxx-yyyy pods (depending on your supersetNode.replicaCount and supersetWorker.replicaCount values).The exact list will depend on some of your specific configuration overrides but you should generally expect: Superset-worker-75b48bbcc-qrq49 1/1 Running 0 4m12s Superset-worker-75b48bbcc-jmmjr 1/1 Running 0 4m8s Superset-redis-master-0 1/1 Running 0 6d20h Superset-postgresql-0 1/1 Running 0 6d20h Superset-init-db-zlm9z 0/1 Completed 0 111s Superset-celerybeat-7cdcc9575f-k6xmc 1/1 Running 0 119s
0 kommentar(er)
