rickchengx commented on pull request #4170: URL: https://github.com/apache/zeppelin/pull/4170#issuecomment-878747422
> Same as in #4171 > > > I don't think we need to include all the configuration options in our example 100-interpreter-spec.yaml. This file should be configured by the user. > > Maybe we should write more documentation on how to change the file to suit use cases. Hi, @Reamer Thanks for your comment. In order to support more k8s features, the `100-interpreter-spec.yaml` file may indeed become more complicated. But if users are required to modify `100-interpreter-spec.yaml`, it may lead to a poor user experience. Especially when the user directly runs the zeppelin server in the k8s cluster, every time the `100-interpreter-spec.yaml` file is modified, the docker image needs to be rebuilt and deployed. Therefore, I think that common features should be placed in the `100-interpreter-spec.yaml` file as much as possible so that users can directly configure their desired properties in the interpreter settings. When users need to configure some more customized properties, they can modify the `100-interpreter-spec.yaml` file. Users may often need to pull the image from a private repository, so I think this property is relatively important. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
