Samuel

@bastelfreak I'd like to get your opinion on this

I had the same question when doing a security review of Rollouts. Would removing the ClusterRoleBinding from the install yaml, and instead craft one RoleBinding for each ns work in...

I was able to get the code with okta, but without the `--console` there is nowhere to input the verification code? What am I missing? For okta provider ``` step...

Following, hit this issue in github actions since the runner was being re-used and the cert already existed, a `step ca bootstrap` was requesting on stdin `overwrite (y/n)?` in a...

I get the error during the `apply`, and subsequent runs during the `plan` stage as well, effectively blocking our pipeline.

I get a similar behavior with this simple pipeline in GKE. Took the latest debug tag `debug-v0.19.0` and a dummy dockerfile from git. Removed any registry. ``` podTemplate(yaml: """ kind:...

Thank for trying these out and trying to help me. Base on the kubernetes docs https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.11/#securitycontext-v1-core it seems like the securityContext can be set at the container level or the...

Thanks for trying to help. I tried the above it didnt make a difference. Also even without it Icould see the process in the process space by going into the...

In case people wonder, `kaniko/executor` will hang forever if it cannot reach `metadata.google.internal` in GKE. kaniko code https://github.com/GoogleContainerTools/kaniko/blob/v0.19.0/vendor/k8s.io/kubernetes/pkg/credentialprovider/gcp/metadata.go#L194-L204 it would have saved a lot of headache if it had at...

Seems to happen if `metadata.google.internal` does not resolve. It'd be better to get something logged at the debug/info or warning level to say it couldn't be reached.