dcoliversun commented on pull request #35359: URL: https://github.com/apache/spark/pull/35359#issuecomment-1024826220
> Second reason, and also the current namespace set way break a special case like below(we shouldn't occupy any pontential data.key allowed by k8s in confFileMap): > > ```yaml > apiVersion: v1 > kind: ConfigMap > metadata: > name: configmap-test > # This is metadata.namespace, the namespace of configMap > namespace: non-default > data: > # This is user specified `namespace` file, fill up in configFileMap > namespace: > foo=bar > ``` @Yikun Thanks for your sharing. This example is exactly what I'm worried about. I think the namespace in sparkConf will prevail. All resources of spark application should keep the same namespace. The behavior of the user to arbitrarily specify the namespace should be regarded as an attack. What do you think about this？ -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
