itsecforu

Highlighted in bold for what exactly changed values.yaml: ``` expose: # Set the way how to expose the service. Set the type as "ingress", # "clusterIP", "nodePort" or "loadBalancer" and...

Can somebody helps? :-(

I updated to 2.8

I can’t update this way, I need to install version 3 in parallel

the same **Readiness probe failed** with Helm 3.0.2 :-(

From my database pod: ``` CREATE TABLE waiting for server to shut down....LOG: received fast shutdown request LOG: aborting any active transactions LOG: autovacuum launcher shutting down LOG: shutting down...

I was triying install with: `version.BuildInfo{Version:"v3.0.2", GitCommit:"19e47ee3283ae98139d98460de796c1be1e3975f", GitTreeState:"clean", GoVersion:"go1.13.5"}` and: ``` helm version Client: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"} Server: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"} ``` I collected a minimal file of values: ```...

no ideas?

@reasonerjt now i fixed networking problems. in my registry log i see error: ``` time="2020-06-25T09:24:19.693410115Z" level=warning msg="httpSink{http://harbor-harbor-core/service/notifications} encountered too many errors, backing off" time="2020-06-25T09:24:23.694225242Z" level=error msg="retryingsink: error writing events: httpSink{http://harbor-harbor-core/service/notifications}:...

Fixed by Nginx pod proxy settings