You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2022. It is now read-only.
What happened:
If a securityContext is set the process is not able to create directory
kubectl logs -n catalog catalog-catalog-controller-manager-6c8cfdbcc7-5jxxz
W0609 12:50:10.066023 1 feature_gate.go:235] Setting GA feature gate OriginatingIdentity=true. It will be removed in a future release.
I0609 12:50:10.066131 1 feature_gate.go:243] feature gates: &{map[OriginatingIdentity:true]}
I0609 12:50:10.066236 1 feature_gate.go:243] feature gates: &{map[OriginatingIdentity:true ServicePlanDefaults:false]}
I0609 12:50:10.066305 1 hyperkube.go:192] Service Catalog version v0.3.0-dirty (built 2020-05-25T13:37:02Z)
I0609 12:50:10.140154 1 controller_manager.go:100] Building k8s kubeconfig
I0609 12:50:10.145096 1 controller_manager.go:128] Building service-catalog kubeconfig for url:
I0609 12:50:10.145130 1 controller_manager.go:135] Using inClusterConfig to talk to service catalog API server -- make sure your API server is registered with the aggregator
Error: failed to establish SecureServingOptions mkdir /var/run/kubernetes-service-catalog: permission denied
What you expected to happen:
Not crash How to reproduce it (as minimally and precisely as possible):
Set a securityContext inside chart
Anything else we need to know?:
Environment:
Kubernetes version (use kubectl version): 1.18
service-catalog version: 0.3.0
The text was updated successfully, but these errors were encountered:
Bug Report
What happened:
If a securityContext is set the process is not able to create directory
What you expected to happen:
Not crash
How to reproduce it (as minimally and precisely as possible):
Set a securityContext inside chart
Anything else we need to know?:
Environment:
kubectl version
): 1.18The text was updated successfully, but these errors were encountered: